An order-quote Lambda function is invoked directly by API Gateway. Traffic is predictable during the business day, and the first request after scaling from zero causes unacceptable latency. The team wants to keep the current architecture and reduce cold-start impact. Which configuration should they use?

Increase the function timeout so the first invocation has more time to finish.

A longer timeout can prevent premature failures, but it does nothing to remove cold-start latency. The user still waits for the execution environment to initialize before work begins. The problem here is startup delay, not insufficient execution time, so timeout tuning is not the right fix.

Set reserved concurrency to a fixed number and leave the rest unchanged.

Reserved concurrency limits how much a function can scale and protects downstream systems, but it does not pre-initialize execution environments. A function can still cold start even when reserved concurrency is set. That means the latency issue remains, even though the total number of concurrent executions is controlled.

Increase the memory size only to eliminate cold starts.

More memory can improve CPU allocation and execution speed, but it does not guarantee that cold starts disappear. Some workloads do benefit from memory tuning, yet the specific problem here is the delay when new environments are created. Provisioned concurrency addresses that directly, while memory tuning mainly affects execution performance after the runtime is already warm.

What does this SAA-C03 question test?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Enable provisioned concurrency for the Lambda function. — Provisioned concurrency is the best choice because it keeps Lambda execution environments warm and ready before traffic arrives. For a predictable daytime workload behind API Gateway, this is the most direct way to remove first-request delays caused by cold starts. It preserves the serverless design while delivering more consistent latency. Reserved concurrency controls scaling, and memory tuning affects runtime speed, but neither one pre-warms functions the way provisioned concurrency does. Why others are wrong: Timeout only changes how long a request may run, not how quickly it starts. Reserved concurrency controls concurrency limits and protection, but it does not eliminate cold starts. Increasing memory may improve CPU and reduce runtime duration, yet the cold-start problem still exists when a new environment must initialize. The requirement is predictable low-latency startup, which is why provisioned concurrency is the correct answer.

What should I do if I get this SAA-C03 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.