A serverless checkout API uses AWS Lambda behind API Gateway. Every weekday at 09:00 UTC, marketing triggers a predictable surge. The first few minutes after each surge show cold-start latency, but traffic volume is forecastable and the business wants stable p95 latency. Which two changes should the team implement? Select two.

Increase the Lambda timeout so the function has more time to initialize during the spike.

A longer timeout does not remove cold starts or pre-initialize execution environments. It only changes how long a function may run before timing out. The user-facing latency issue would remain, so this does not solve the core problem.

Double the memory size during the spike without changing the concurrency model.

More memory can improve CPU allocation and sometimes reduce execution duration, but it does not guarantee that the environment is already warm. Without provisioned concurrency, the first requests can still incur cold-start penalties. The scenario specifically calls for stable p95 latency.

Move the function into more Availability Zones so the platform can spread cold starts across regions.

Lambda already runs as a managed regional service and does not need the customer to place individual functions across AZs. Spreading across AZs does not eliminate cold starts. The issue is initialization time, not geographic distribution.

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: Publish a Lambda version and attach provisioned concurrency to an alias that points to that version. — The correct solution is to use provisioned concurrency and schedule it ahead of the known burst. Provisioned concurrency keeps Lambda environments warm, which removes most cold-start delays, and scheduled scaling ensures enough capacity exists before traffic arrives at 09:00 UTC. This combination matches the predictable workload pattern and gives the team stable latency without keeping excess concurrency running all day. Timeout changes, memory increases, and AZ-related ideas do not remove cold starts. They may affect how long or how fast a function runs once it is executing, but they do not pre-initialize the runtime. The scenario explicitly says the surge is predictable, which makes scheduled provisioned concurrency the right operational fit.

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.