- A
Configure a larger ALB deregistration delay so that old targets remain longer before termination.
Why wrong: ALB deregistration delay affects how long existing targets are kept during scale-in events and connection draining behavior. It does not reduce the initialization/warm-up time of newly launched instances. If new instances cannot become healthy until warm-up completes, customers can still see 5xx responses during the initial minutes after scale-out.
- B
Use an Auto Scaling warm pool so instances are pre-initialized and ready to register quickly when the ASG scales out.
With a warm pool, Auto Scaling can launch and keep a set of instances in a pre-initialized state (for example, instances are already booted and have completed parts of startup/initialization as supported by warm pool behavior). When scaling triggers, these instances can transition to service faster and begin registering with the ALB. Because your bottleneck is that instances take ~4 minutes to become truly ready, warming them ahead of time most directly reduces the gap between scale-out and customer-ready capacity (and therefore reduces 5xx occurrences while waiting for targets to pass ALB health checks).
- C
Increase the number of desired instances immediately without using scaling policies, and then rely on manual reconfiguration.
Why wrong: Manually changing desired capacity can work in an operational sense, but it is not a direct improvement to application warm-up time, and it is not responsive/automated for demand variability. It also doesn’t solve the core issue: newly created instances still require the same warm-up duration before they pass ALB health checks.
- D
Switch from ALB to NLB so instances become reachable sooner without waiting for health checks.
Why wrong: NLB does not inherently remove the application’s initialization requirement. While health check behavior differs by load balancer type (e.g., NLB often uses TCP-level checks), the application still needs time to become ready to handle requests successfully. Switching to NLB may change routing and health-check characteristics, but it does not directly address the ~4-minute warm-up bottleneck.
Quick Answer
The answer is to use an Auto Scaling warm pool, which directly addresses the need to reduce warm-up time on EC2 scale-out by pre-initializing instances before they are needed. This is correct because a warm pool launches and prepares instances—loading caches, running initialization scripts, and completing dependency setup—so they are fully warmed and ready to register with the ALB as healthy the moment the Auto Scaling group scales out, eliminating the ~4-minute delay that causes 5xx errors. On the SAA-C03 exam, this scenario tests your understanding of lifecycle hooks and state management within Auto Scaling; a common trap is to confuse warm pools with simple increased minimum instances or scheduled scaling, which still suffer from cold-start latency. Remember the memory tip: “Warm pool = pre-heated, not pre-launched”—the instances are fully initialized but held in a stopped or pending state, ready to serve traffic instantly when demand spikes.
SAA-C03 Design High-Performing Architectures Practice Question
This SAA-C03 practice question tests your understanding of design high-performing architectures. Examine the command output carefully: the correct answer depends on what the output actually shows, not on general recall alone. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You run a web application on an EC2 Auto Scaling group behind an Application Load Balancer (ALB). During scheduled traffic spikes, new instances launch but customers occasionally see 5xx errors for the first few minutes after scale-out. Operational logs show instances need ~4 minutes to warm up (load caches and initialize dependencies). ALB target health becomes healthy only after this warm-up. Which change most directly improves performance during spikes by reducing the time to serve traffic after scaling?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"first"Why it matters: Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
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
Use an Auto Scaling warm pool so instances are pre-initialized and ready to register quickly when the ASG scales out.
B is correct because a warm pool pre-initializes instances (e.g., loading caches and dependencies) before they are added to the Auto Scaling group. When the ASG scales out, these pre-warmed instances can be quickly moved into service, bypassing the ~4-minute warm-up delay and reducing the window for 5xx errors.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configure a larger ALB deregistration delay so that old targets remain longer before termination.
Why it's wrong here
ALB deregistration delay affects how long existing targets are kept during scale-in events and connection draining behavior. It does not reduce the initialization/warm-up time of newly launched instances. If new instances cannot become healthy until warm-up completes, customers can still see 5xx responses during the initial minutes after scale-out.
- ✓
Use an Auto Scaling warm pool so instances are pre-initialized and ready to register quickly when the ASG scales out.
Why this is correct
With a warm pool, Auto Scaling can launch and keep a set of instances in a pre-initialized state (for example, instances are already booted and have completed parts of startup/initialization as supported by warm pool behavior). When scaling triggers, these instances can transition to service faster and begin registering with the ALB. Because your bottleneck is that instances take ~4 minutes to become truly ready, warming them ahead of time most directly reduces the gap between scale-out and customer-ready capacity (and therefore reduces 5xx occurrences while waiting for targets to pass ALB health checks).
Clue confirmation
The clue word "first" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Increase the number of desired instances immediately without using scaling policies, and then rely on manual reconfiguration.
Why it's wrong here
Manually changing desired capacity can work in an operational sense, but it is not a direct improvement to application warm-up time, and it is not responsive/automated for demand variability. It also doesn’t solve the core issue: newly created instances still require the same warm-up duration before they pass ALB health checks.
- ✗
Switch from ALB to NLB so instances become reachable sooner without waiting for health checks.
Why it's wrong here
NLB does not inherently remove the application’s initialization requirement. While health check behavior differs by load balancer type (e.g., NLB often uses TCP-level checks), the application still needs time to become ready to handle requests successfully. Switching to NLB may change routing and health-check characteristics, but it does not directly address the ~4-minute warm-up bottleneck.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may think NLB bypasses health checks entirely, but in reality NLB still requires health checks to mark targets as healthy, and the application warm-up delay remains the bottleneck.
Detailed technical explanation
How to think about this question
A warm pool uses a separate Auto Scaling group with a 'Warmed' state; instances in this state run but are not yet registered with the ALB. When scaling out, the ASG moves instances from the warm pool to the 'InService' state, where they immediately begin health checks, but the warm-up (cache loading) has already occurred, so they pass health checks faster. This is especially useful for applications with long initialization times, such as those loading large ML models or connecting to external caches like Redis.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Design High-Performing Architectures — study guide chapter
Learn the concepts, then practise the questions
- →
Design High-Performing Architectures practice questions
Targeted practice on this topic area only
- →
All SAA-C03 questions
1,040 questions across all exam domains
- →
SAA-C03 study guide
Full concept coverage aligned to exam objectives
- →
SAA-C03 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SAA-C03 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Design Secure Architectures practice questions
Practise SAA-C03 questions linked to Design Secure Architectures.
Design Resilient Architectures practice questions
Practise SAA-C03 questions linked to Design Resilient Architectures.
Design High-Performing Architectures practice questions
Practise SAA-C03 questions linked to Design High-Performing Architectures.
Design Cost-Optimized Architectures practice questions
Practise SAA-C03 questions linked to Design Cost-Optimized Architectures.
SAA-C03 VPC practice questions
Practise SAA-C03 questions linked to SAA-C03 VPC.
SAA-C03 S3 lifecycle policy questions
Practise SAA-C03 questions linked to SAA-C03 S3 lifecycle policy questions.
SAA-C03 RDS Multi-AZ questions
Practise SAA-C03 questions linked to SAA-C03 RDS Multi-AZ questions.
SAA-C03 IAM policy practice questions
Practise SAA-C03 questions linked to SAA-C03 IAM policy.
SAA-C03 Route 53 failover questions
Practise SAA-C03 questions linked to SAA-C03 Route 53 failover questions.
SAA-C03 CloudFront practice questions
Practise SAA-C03 questions linked to SAA-C03 CloudFront.
SAA-C03 NAT gateway questions
Practise SAA-C03 questions linked to SAA-C03 NAT gateway questions.
SAA-C03 VPC endpoint questions
Practise SAA-C03 questions linked to SAA-C03 VPC endpoint questions.
Practice this exam
Start a free SAA-C03 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SAA-C03 question test?
Design High-Performing Architectures — This question tests Design High-Performing Architectures — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use an Auto Scaling warm pool so instances are pre-initialized and ready to register quickly when the ASG scales out. — B is correct because a warm pool pre-initializes instances (e.g., loading caches and dependencies) before they are added to the Auto Scaling group. When the ASG scales out, these pre-warmed instances can be quickly moved into service, bypassing the ~4-minute warm-up delay and reducing the window for 5xx errors.
What should I do if I get this SAA-C03 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "first". Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.