SAA-C03 Design High-Performing Architectures Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Enable Lambda provisioned concurrency on a published function alias and set the minimum provisioned instances to the baseline expected during spikes.

  Why this is correct

  Provisioned concurrency pre-creates and initializes Lambda execution environments for a specific published alias or version, so requests are served immediately without a cold start. Setting the provisioned minimum to your baseline expected during spikes ensures that the required capacity is already warm and ready, maintaining consistent low latency under load. This is the correct, managed mechanism designed by AWS for this exact problem.

• ✗

  Increase the function memory size to the maximum and rely on the larger memory to eliminate cold starts.

  Why it's wrong here

  Allocating more memory to a Lambda function increases the CPU and network throughput, which can shorten execution time but does not address the initialization phase of a cold start. New execution environments are still created from scratch, including loading the code and initializing the runtime, which the memory setting does not preempt. Additionally, maxing out memory increases your cost significantly, making this a costly and ineffective strategy for latency guarantees.

  When this WOULD be correct

  In a scenario where the goal is to reduce Lambda execution duration for CPU-bound tasks without changing concurrency, and the question asks for a simple configuration change that improves performance without addressing cold starts specifically.

• ✗

  Configure an ALB with target group health checks to keep Lambda warm by sending periodic requests.

  Why it's wrong here

  Sending heartbeat requests through an ALB health check can keep one Lambda instance warm, but Lambda functions typically scale out to many concurrent instances, and health checks target only a single instance at a time. When a burst of traffic arrives, the other instances will still face cold starts, so consistency is not achieved. Furthermore, Lambda freezes and times out instances after several minutes of inactivity regardless of health checks, so this workaround is neither reliable nor scalable.

  When this WOULD be correct

  A question where the goal is to ensure a Lambda function remains warm for periodic requests from an ALB, and the traffic pattern is consistent (e.g., steady low traffic with occasional small spikes). In that case, ALB health checks can keep a single instance warm, reducing cold starts for the first request after idle periods.

• ✗

  Turn on AWS CloudTrail data events to monitor cold start frequency and tune the runtime accordingly.

  Why it's wrong here

  CloudTrail data events record API calls and management actions, not internal Lambda performance metrics such as cold start duration. Monitoring cold starts with CloudTrail provides visibility after the fact, but it does nothing to eliminate the latency itself. Tuning the runtime based on historical logs is a reactive process and cannot guarantee consistent low latency for every incoming request.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The SAA-C03 exam frequently reuses these exact scenarios with slightly different constraints.

Analysis generated from the official SAA-C03blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Go deeper

Related to this question