AWS - Architecture Best Practices
An Auto Scaling group fails to launch instances in a second AZ after initial deployment. What is a common cause?
An Auto Scaling group fails to launch instances in a second AZ after initial deployment. What is a common cause?
medium📝 Debug Q7 of 15
Step-by-Step Solution
Solution:
Step 1: Verify subnet configuration
Auto Scaling requires subnets in each AZ to launch instances there.Step 2: Check subnet capacity and specification
If subnet is missing or full, instances cannot launch in that AZ.Final Answer:
The subnet in the second AZ is not specified or lacks capacity -> Option BQuick Check:
Subnets must be configured per AZ for Auto Scaling [OK]
Quick Trick: Configure subnets in all AZs for Auto Scaling groups [OK]
Common Mistakes:
- Thinking Auto Scaling supports only one AZ
- Believing instances can't launch in multiple AZs
- Ignoring subnet and capacity issues
Master "Architecture Best Practices" in AWS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore AWS Quizzes