Bird
0
0

You want to optimize costs by scaling down servers during low traffic but avoid frequent scaling actions. Which approach is best?

hard📝 Best Practice Q15 of 15
AWS - Auto Scaling
You want to optimize costs by scaling down servers during low traffic but avoid frequent scaling actions. Which approach is best?
ASet aggressive scale-in thresholds with short cooldown periods.
BUse moderate scale-in thresholds with longer cooldown periods.
CDisable scale-in to keep servers always running.
DManually add and remove servers daily.
Step-by-Step Solution
Solution:
  1. Step 1: Understand cost optimization and stability

    To save costs, scale down servers when traffic is low but avoid too frequent scaling to prevent instability.
  2. Step 2: Evaluate options

    Aggressive thresholds and short cooldown cause frequent scaling (not good). Disabling scale-in wastes money. Manual scaling is inefficient. Moderate thresholds with longer cooldown balance cost and stability.
  3. Final Answer:

    Use moderate scale-in thresholds with longer cooldown periods. -> Option B
  4. Quick Check:

    Moderate thresholds + longer cooldown = cost and stability [OK]
Quick Trick: Balance thresholds and cooldown for cost and stability [OK]
Common Mistakes:
  • Setting too aggressive scale-in causing flapping
  • Disabling scale-in wastes money
  • Relying on manual scaling

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes