SAA-C03 Design High-Performing Architectures Practice Question
A team runs a stateless web app on Amazon EC2 behind an Application Load Balancer. During traffic spikes, new EC2 instances take several minutes to finish bootstrapping before they can receive traffic. Which Auto Scaling configuration most directly reduces the time until additional capacity is available?
⚠ Common exam trap
A common mix-up: candidates confuse the deregistration delay (which handles graceful connection draining) with a mechanism to speed up instance readiness, or they may incorrectly assume that reducing the minimum size or switching to a Network Load Balancer will improve scaling speed, when neither addresses the root cause of slow bootstrapping.
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 pre-initialized instances are ready to enter service.
An Auto Scaling warm pool allows you to maintain a pool of pre-initialized instances that are ready to quickly enter the target group and start serving traffic. Instead of waiting for new instances to boot and configure during a scale-out event, the warm pool provides instances that have already completed bootstrapping, drastically reducing the time to additional capacity.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the ALB target group deregistration delay.
Why it's wrong here
Deregistration delay governs how long the load balancer waits before removing a draining target; it affects scale-in, not the bootstrapping of new instances. Raising it is correct when long-lived connections must finish gracefully during instance termination.
When this WOULD be correct
This option would be correct in a scenario where the question asks how to prevent in-flight requests from being dropped during a scale-in event, such as when instances are being terminated and you need to ensure graceful connection draining.
- ✓
Use an Auto Scaling warm pool so pre-initialized instances are ready to enter service.
Why this is correct
A warm pool keeps pre-initialised instances in a stopped or running state, so scaling out moves already-bootstrapped capacity into service instead of waiting several minutes for bootstrap, directly cutting the delay before new instances receive traffic.
- ✗
Reduce the Auto Scaling group minimum size to one instance.
Why it's wrong here
Lowering the minimum size reduces the baseline fleet, so scale-out must launch more instances from scratch during a spike, worsening time-to-capacity. A low minimum suits cost reduction for predictable low traffic, not faster response to sudden demand.
When this WOULD be correct
If the question were about minimizing costs for a predictable, low-traffic application where over-provisioning is unnecessary, reducing the minimum size to one instance would be correct.
- ✗
Replace the Application Load Balancer with a Network Load Balancer.
Why it's wrong here
A Network Load Balancer operates at layer 4 and changes nothing about instance bootstrapping time; capacity still arrives only after user data scripts complete. NLB is chosen for extreme throughput, static IPs or TCP/UDP traffic, not for shortening scale-out latency.
When this WOULD be correct
In a scenario where the application requires ultra-low latency and high throughput for TCP/UDP traffic, and the bootstrapping delay is not a concern, replacing an ALB with an NLB would be correct to reduce latency and handle millions of requests per second.
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.
✓Use an Auto Scaling warm pool so pre-initialized instances are ready to enter service.Correct answer▾
Why this is correct
A warm pool keeps pre-initialised instances in a stopped or running state, so scaling out moves already-bootstrapped capacity into service instead of waiting several minutes for bootstrap, directly cutting the delay before new instances receive traffic.
✗Increase the ALB target group deregistration delay.Wrong answer — click to see why▾
Why this is wrong here
Increasing the deregistration delay only keeps existing connections alive longer; it does not speed up the bootstrapping of new instances, so it does not reduce the time until additional capacity is available.
★ When this WOULD be the correct answer
This option would be correct in a scenario where the question asks how to prevent in-flight requests from being dropped during a scale-in event, such as when instances are being terminated and you need to ensure graceful connection draining.
Why candidates choose this
Candidates may confuse the deregistration delay with a mechanism that helps new instances become ready faster, or they might think it gives more time for bootstrapping to complete before traffic is sent.
✗Reduce the Auto Scaling group minimum size to one instance.Wrong answer — click to see why▾
Why this is wrong here
Reducing the minimum size to one instance does not address the bootstrapping delay; it only lowers the baseline capacity, potentially worsening performance during traffic spikes.
★ When this WOULD be the correct answer
If the question were about minimizing costs for a predictable, low-traffic application where over-provisioning is unnecessary, reducing the minimum size to one instance would be correct.
Why candidates choose this
Candidates may think that a smaller minimum size forces faster scaling, but it actually reduces the buffer of running instances, increasing the impact of bootstrapping delays.
✗Replace the Application Load Balancer with a Network Load Balancer.Wrong answer — click to see why▾
Why this is wrong here
Replacing the ALB with a Network Load Balancer does not address the bootstrapping delay of EC2 instances; NLB operates at layer 4 and does not affect instance initialization time.
★ When this WOULD be the correct answer
In a scenario where the application requires ultra-low latency and high throughput for TCP/UDP traffic, and the bootstrapping delay is not a concern, replacing an ALB with an NLB would be correct to reduce latency and handle millions of requests per second.
Why candidates choose this
Candidates may think that a faster load balancer (NLB) will reduce the time until new instances can receive traffic, overlooking that the bottleneck is instance bootstrapping, not load balancer performance.
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
About these practice questions
This SAA-C03 question is part of Courseiva's 935-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.