Explanation:
Option D is the correct answer.
An EC2 Auto Scaling warm pool allows you to decrease latency for applications that have exceptionally long boot times. By keeping instances in a stopped or running state, pre-initialized and ready to go, the Auto Scaling group can quickly place them in service during scale-out events without waiting for long-running boot scripts to finish. This solves the boot delay without permanently overprovisioning the application, saving costs compared to simply raising the minimum capacity (Option B).
Changing the instance size (Option A) won't necessarily bypass the time required for long boot scripts. Predictive scaling (Option C) scales ahead of traffic but doesn't reduce the actual boot time, which could still lead to issues if sudden traffic spikes occur.
Ultimate access to all questions.
A company runs an application on Amazon EC2 instances that are in an Amazon EC2 Auto Scaling group. Scale-out actions take a long time to become complete because of long-running boot scripts. A SysOps administrator must implement a solution to reduce the required time for scale-out actions without overprovisioning the Auto Scaling group. Which solution will meet these requirements?
A
Change the launch configuration to use a larger instance size.
B
Increase the minimum number of instances in the Auto Scaling group.
C
Add a predictive scaling policy to the Auto Scaling group.
D
Add a warm pool to the Auto Scaling group.
No comments yet.