You configured an Auto Scaling group with minimum 2 instances across two AZs, but during a failure, only one instance is running. What is the likely issue?

medium📝 Debug Q14 of 15

AWS - Architecture Best Practices

AAuto Scaling group is not set to replace unhealthy instances

BLoad balancer is misconfigured to route traffic

CInstances are launched in the same AZ only

DSecurity groups block instance communication

Step-by-Step Solution

Solution:

Step 1: Check Auto Scaling group settings
Auto Scaling must replace unhealthy instances to maintain minimum capacity.
Step 2: Understand failure impact
If replacement is disabled, failed instance won't be replaced, causing fewer running instances.
Final Answer:
Auto Scaling group is not set to replace unhealthy instances -> Option A
Quick Check:
Auto Scaling replaces unhealthy = maintain capacity [OK]

Quick Trick: Auto Scaling must replace failed instances to keep count [OK]

Common Mistakes:

Blaming load balancer for instance count
Assuming instances launched only in one AZ
Thinking security groups affect instance count

Master "Architecture Best Practices" 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 configured an Auto Scaling group with minimum 2 instances across two AZs, but during a failure, only one instance is running. What is the likely issue?

Step 1: Check Auto Scaling group settings

Step 2: Understand failure impact

Final Answer:

Quick Check:

Want More Practice?