You have an application with a startup time of 5 minutes and a shutdown time of 2 minutes. What is the best cooldown period setting for your AWS Auto Scaling group to avoid rapid scaling actions?

hard📝 Best Practice Q15 of 15

AWS - Auto Scaling

ASet cooldown to 300 seconds (5 minutes) to cover startup time

BSet cooldown to 120 seconds (2 minutes) to cover shutdown time

CSet cooldown to 60 seconds to speed up scaling

DSet cooldown to 600 seconds (10 minutes) to cover both startup and shutdown

Step-by-Step Solution

Solution:

Step 1: Identify relevant cooldown duration
Cooldown should cover the longest time the system needs to stabilize after scaling.
Step 2: Compare startup and shutdown times
Startup is 5 minutes, shutdown is 2 minutes, so total 7 minutes to be safe.
Step 3: Choose cooldown that covers both safely
Setting cooldown to 10 minutes (600 seconds) covers both startup and shutdown comfortably.
Final Answer:
Set cooldown to 600 seconds (10 minutes) to cover both startup and shutdown -> Option D
Quick Check:
Cooldown ≥ startup + shutdown time [OK]

Quick Trick: Cooldown ≥ startup + shutdown time for safety [OK]

Common Mistakes:

Setting cooldown too short for startup time
Ignoring shutdown time in cooldown
Choosing cooldown shorter than app needs

Master "Auto Scaling" in AWS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More AWS Quizzes

You have an application with a startup time of 5 minutes and a shutdown time of 2 minutes. What is the best cooldown period setting for your AWS Auto Scaling group to avoid rapid scaling actions?

Step 1: Identify relevant cooldown duration

Step 2: Compare startup and shutdown times

Step 3: Choose cooldown that covers both safely

Final Answer:

Quick Check:

Want More Practice?