Reduce scale-out latency with warm pools and lifecycle hooks on a mixed-instances group
A company runs a web application on a single Amazon EC2 instance. End users experience slow application performance during times of peak usage, when CPU utilization is consistently more than 95%. A user data script installs required custom packages on the EC2 instance. The process of launching the instance takes several minutes. The company is creating an Auto Scaling group that has mixed instance groups, varied CPUs, and a maximum capacity limit. The Auto Scaling group will use a launch template for various configuration options. The company needs to decrease application latency when new instances are launched during auto scaling. Which solution will meet these requirements?
Community Votes
78% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Warm pools let the group pre-launch instances into a stopped state and complete their initialization in advance, so scale-out only has to start and resume them, while lifecycle hooks are the supported way to run configuration work during that transition.
A single-instance web application becomes slow at high CPU, and new instances take several minutes to launch because a user data script installs custom packages. The Auto Scaling group uses mixed instance groups, varied CPUs, a maximum capacity limit, and a launch template.
Setting the default instance warmup time to 0 seconds. That only affects how the group evaluates instance health during its default warmup, it does not pre-initialize instances, and it makes the group act on health data sooner, which is the opposite of what a slow-booting fleet needs.
Community Discussion (10 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Warm pools keep pre-initialized instances in a stopped state, and when scale-out occurs the group starts an instance that has already had its user data work applied, which removes the several-minute launch delay from the request path. Dynamic scaling is the appropriate policy because the requirement is to react to observed load rather than to a forecast, and no peak pattern is given that would justify predictive scaling. Lifecycle hooks provide the documented mechanism for running the configuration script during instance initialization.Why the Other Options Are Wrong
A and B: Both set the default instance warmup time to 0 seconds, which shortens the period the group waits before evaluating instance health but does nothing to pre-launch or pre-configure instances, so the scale-out latency is unchanged. A additionally uses predictive scaling, which is inappropriate with no forecast pattern to base it on. C: Instance maintenance policies apply to Auto Scaling groups with an instance refresh workflow rather than to a warm pool transition, and warm pools are unsupported for groups using a mixed instances policy, so this option is not viable as written.Community Comment Notes
The community voted 70 to 20 for D. One commenter raised a valid technical caveat that warm pools cannot be used with a mixed instances policy, which makes the question poorly written, and another confirmed that no peak pattern is given so predictive scaling has nothing to forecast from. A third commenter noted the B variant is the only one left viable if warm pools are excluded, which is why the exam key is D.Official Reference
Related Analysis
Practice All SAP-C02 Questions
Access 85 questions with complete answers and detailed explanations.
View Full SAP-C02 Practice Test →