DOP-C02 Question 309
Select 3Your company uses AWS Auto Scaling to manage a fleet of EC2 instances that support a highly available web application. Recently, you noticed frequent scaling events due to sudden spikes in incoming traffic, which sometimes result in increased response times. To address this, you need to implement configuration changes to better handle these events and ensure seamless scaling. Which action(s) should you take to optimize the Auto Scaling behavior?
- A
Modify the cooldown period for the Auto Scaling group to prevent overlapping scaling events.
- B
Implement a step scaling policy to add instances incrementally based on the magnitude of the traffic spike.
- C
Switch from a target tracking scaling policy to a scheduled scaling policy for better predictability.
- D
Enable instance warm-up time in the Auto Scaling group to account for booting and application initialization.
- E
Reduce the instance size in the Auto Scaling group to handle more instances per scaling step.
Show answer and explanation
Correct answers: A, B, D
Explanation
To optimize Auto Scaling behavior in response to sudden traffic spikes, it is important to implement configuration changes that stabilize scaling events and improve responsiveness. Adjusting the cooldown period prevents overlapping scaling actions, while step scaling policies allow for finer-grained scaling based on traffic intensity. Enabling instance warm-up time ensures that metrics reflect actual capacity, avoiding premature scaling decisions. These actions together help accommodate unpredictable workloads effectively.
- A. Correct.
Modifying the cooldown period prevents Auto Scaling from launching or terminating instances too quickly, which can help stabilize the environment during traffic spikes.
- B. Correct.
A step scaling policy allows you to scale incrementally based on the intensity of the metric breaches, offering finer control during sudden traffic surges.
- C. Incorrect.
Switching to a scheduled scaling policy does not address unpredictable traffic spikes and is not suitable for highly variable workloads.
- D. Correct.
Enabling instance warm-up time ensures that new instances are not immediately included in metric calculations, giving them time to initialize properly and reducing premature scaling events.
- E. Incorrect.
Reducing the instance size may introduce additional overhead and is not directly related to optimizing the scaling behavior during traffic spikes.