AWS - Architecture Best Practices
A user configures an Auto Scaling policy but notices no new instances launch during high traffic. What is the most likely cause?
A user configures an Auto Scaling policy but notices no new instances launch during high traffic. What is the most likely cause?
medium📝 Debug Q6 of 15
Step-by-Step Solution
Solution:
Step 1: Analyze scaling policy thresholds
If thresholds are too high, scaling triggers won't activate during traffic spikes.Step 2: Check other options
Minimum size affects initial instances but not scaling triggers; stopped instances don't auto scale; CloudFront caching unrelated.Final Answer:
The scaling policy threshold is set too high -> Option DQuick Check:
High threshold blocks scaling = The scaling policy threshold is set too high [OK]
Quick Trick: Check scaling thresholds if no instances launch [OK]
Common Mistakes:
- Ignoring threshold settings
- Confusing minimum size with scaling triggers
- Blaming unrelated services
Master "Architecture Best Practices" in AWS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore AWS Quizzes