1 / 1010%
Question 1 of 10

Your Auto Scaling group is configured to launch one new Amazon EC2 instance if the overall CPU load exceeds 65% over a five minutes interval. Occasionally, the Auto Scaling group launches a second Amazon EC2 instance before the first is operational. The second instance is not required and introduces needless compute costs. How can you prevent the Auto Scaling group from launching the second instance?

AConfigure a lifecycle hook for your Auto Scaling group
BAdd a scaling-specific cooldown period to the scaling policy
CAdjust the CPU threshold that triggers a scaling action
DAttach a new launch configuration to the Auto Scaling group