SAA-C03 Design High-Performing Architectures Practice Question
Exhibit
CloudWatch metrics for Lambda function 'image-resize': - Average Duration: 220 ms - P95 Init Duration after idle: 1,400 ms - ConcurrentExecutions: 15 average, 60 during campaign launches - Throttles: 0 - User complaint: first upload after inactivity feels slow
Based on the exhibit, what change best reduces Lambda cold-start impact for a predictable user-upload workflow?
⚠ Common exam trap
Candidates often confuse reserved concurrency (which limits concurrency to prevent throttling) with provisioned concurrency (which pre-warms instances to eliminate cold starts), leading candidates to choose a throttling protection mechanism instead of a cold-start mitigation solution.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable provisioned concurrency for the function.
Provisioned concurrency initializes a specified number of execution environments in advance, so when a user upload triggers the Lambda function, there is no cold-start delay. This directly addresses the predictable, user-upload workflow by ensuring warm containers are ready to handle requests immediately.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Set a reserved concurrency limit for the function to protect it from throttling.
Why it's wrong here
Reserved concurrency protects capacity, but it does not directly remove cold-start latency for the first invocation after idle time.
When this WOULD be correct
A question where multiple functions share an account concurrency limit and a critical function must always have capacity available, even during traffic spikes from other functions. The correct answer would be to set a reserved concurrency to guarantee that function's execution slots.
- ✓
Enable provisioned concurrency for the function.
Why this is correct
Provisioned concurrency keeps a pre-initialized pool of Lambda execution environments ready to respond immediately. The exhibit shows long init duration after inactivity, which is the classic symptom of cold starts affecting user experience. Because the traffic pattern is predictable during launches, provisioned concurrency is the most direct way to reduce startup latency and smooth response times.
- ✗
Increase the function timeout to give more time for initialization.
Why it's wrong here
A longer timeout does not improve startup speed. It only allows slower executions to continue running longer before failing.
- ✗
Move the function to a larger memory setting only to eliminate all initialization time.
Why it's wrong here
More memory can improve execution speed, but it does not eliminate cold starts or guarantee a warm execution environment.
When this WOULD be correct
Option D would be correct if the question asked: 'Which change minimizes function initialization time for a latency-sensitive workload?' In that context, larger memory allocations (up to 10,240 MB) proportionally increase CPU and reduce startup time, making it the best choice.
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.
✓Enable provisioned concurrency for the function.Correct answer▾
Why this is correct
Provisioned concurrency keeps a pre-initialized pool of Lambda execution environments ready to respond immediately. The exhibit shows long init duration after inactivity, which is the classic symptom of cold starts affecting user experience. Because the traffic pattern is predictable during launches, provisioned concurrency is the most direct way to reduce startup latency and smooth response times.
✗Set a reserved concurrency limit for the function to protect it from throttling.Wrong answer — click to see why▾
Why this is wrong here
Reserved concurrency limits protect a function from throttling by other functions, but they do not reduce cold-start latency. Cold starts occur when a new execution environment is initialized, and reserved concurrency does not pre-warm instances.
★ When this WOULD be the correct answer
A question where multiple functions share an account concurrency limit and a critical function must always have capacity available, even during traffic spikes from other functions. The correct answer would be to set a reserved concurrency to guarantee that function's execution slots.
Why candidates choose this
Candidates may confuse 'reserved concurrency' with 'provisioned concurrency' due to similar names, or think that reserving capacity inherently pre-warms environments, which it does not.
✗Move the function to a larger memory setting only to eliminate all initialization time.Wrong answer — click to see why▾
Why this is wrong here
Increasing memory reduces initialization time but does not eliminate it; cold starts still occur. The question asks to 'best reduce' cold-start impact, and provisioned concurrency (option B) keeps functions initialized and ready, which is more effective than merely speeding up initialization.
★ When this WOULD be the correct answer
Option D would be correct if the question asked: 'Which change minimizes function initialization time for a latency-sensitive workload?' In that context, larger memory allocations (up to 10,240 MB) proportionally increase CPU and reduce startup time, making it the best choice.
Why candidates choose this
Candidates know that larger memory allocations reduce initialization time, so they mistakenly believe this eliminates cold starts entirely, overlooking that provisioned concurrency pre-warms instances to avoid cold starts altogether.
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?”
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
Go deeper
Related to this question
About these practice questions
This SAA-C03 question is part of Courseiva's 302-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAA-C03 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAA-C03 exam.