SOA-C02 Reliability and Business Continuity Practice Question
A company runs a critical web application on Amazon EC2 instances that are part of an Auto Scaling group. The application receives unpredictable traffic spikes. The SysOps administrator needs to ensure that when a scale-out event occurs, new instances are ready to serve traffic quickly to minimize latency spikes. Currently, the instance launch and configuration process (including software installs and cache warming) takes about 5 minutes. The administrator wants to reduce the time it takes for new instances to start serving traffic. Which combination of Auto Scaling features should be used?
⚠ Common exam trap
Watch out — candidates often confuse warm pools with lifecycle hooks or pre-warmed AMIs, assuming that reducing software install time alone is sufficient, when the real bottleneck is the entire instance initialization process that warm pools bypass.
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
✓
Implement an Auto Scaling warm pool with a minimum number of pre-initialized instances in a 'Stopped' state. Configure the scaling policy to move instances from the warm pool to the Auto Scaling group when needed.
An Auto Scaling warm pool maintains a pool of pre-initialized instances in a 'Stopped' state that are fully configured (software installed, cache warmed) and ready to serve traffic. When a scale-out event occurs, instances from the warm pool are moved to the Auto Scaling group and transitioned to 'Running' state, bypassing the 5-minute launch and configuration delay, thereby minimizing latency spikes.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a launch template that includes a pre-warmed Amazon Machine Image (AMI) with all software pre-installed, and configure the Auto Scaling group to use a larger instance type to reduce initialization time.
Why it's wrong here
A pre-warmed AMI can reduce installation time, but it does not eliminate the need for instance launch and initialization (e.g., booting, cache warming). Increasing instance type may not significantly reduce boot time and increases cost.
- ✓
Implement an Auto Scaling warm pool with a minimum number of pre-initialized instances in a 'Stopped' state. Configure the scaling policy to move instances from the warm pool to the Auto Scaling group when needed.
Why this is correct
A warm pool maintains instances that have been fully launched and configured but are stopped or in a standby state. When scale-out occurs, instances from the warm pool are started or moved into service quickly, drastically reducing the time to handle traffic.
- ✗
Use scheduled scaling to predictively launch instances before the traffic spikes based on historical patterns.
Why it's wrong here
Scheduled scaling relies on pre-defined time-based adjustments using cron-like schedules, so it can only handle traffic patterns that repeat at known times. In a scenario with unpredictable spikes, scheduled scaling cannot react to real-time demand; it will either over-provision (wasting cost) or under-provision (causing performance issues) because it has no awareness of current load. It also does not reduce instance initialization time, so even if the timing is right, new instances still take minutes to become ready.
- ✗
Configure lifecycle hooks to add a wait time during instance launch so that the instance is fully configured before it is placed behind the load balancer.
Why it's wrong here
Lifecycle hooks are designed to pause an instance during launch or termination so you can run custom actions (e.g., configuration scripts or health checks) before it becomes available. Adding a wait time with a lifecycle hook actually increases the time required for an instance to reach the InService state, making cold starts even slower. This mechanism does nothing to pre-initialize instances or reduce boot time; it only introduces additional delays and is orthogonal to improving scale-out latency.
Go deeper
Related to this question
About these practice questions
One of 247 original SOA-C02 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SOA-C02 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 SOA-C02 exam.