Auto Scaling Group Multi-AZ Configuration and Health Checks
A company runs a critical web application on EC2 instances behind an Application Load Balancer (ALB) across multiple Availability Zones. During a recent failure of one AZ, the application experienced downtime because the Auto Scaling group did not launch new instances quickly enough. What should a DevOps engineer do to improve resilience?
Quick Answer
The correct answer is to configure the Auto Scaling group to span multiple Availability Zones and enable health checks to replace unhealthy instances. This approach ensures high availability by distributing instances across AZs, so when one AZ fails, the Auto Scaling group can launch new instances in the remaining healthy zones, while health checks automatically detect and replace failed instances to maintain capacity. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this concept tests your understanding of resilient architecture patterns, often appearing in questions that contrast horizontal scaling with vertical scaling or single-AZ pitfalls. A common trap is choosing to increase instance size or use a larger AMI, which does not address AZ-level failure. Memory tip: think “spread and replace”—spread instances across AZs and replace them via health checks to survive zone outages.
⚠ Common exam trap
The trap here is that candidates often focus on instance-level improvements (like larger AMIs or instance sizes) instead of architectural resilience across Availability Zones, which is the core requirement for AZ failure scenarios.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure the Auto Scaling group to span multiple AZs and enable health checks to replace unhealthy instances.
Configuring the Auto Scaling group to span multiple Availability Zones (AZs) and enabling health checks ensures that if an entire AZ fails, the Auto Scaling group can launch replacement instances in the remaining healthy AZs. The ALB health checks detect unhealthy instances and trigger the Auto Scaling group to replace them, reducing downtime. This approach leverages the fault isolation of multiple AZs and the automatic scaling capabilities of AWS Auto Scaling.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Configure the Auto Scaling group to span multiple AZs and enable health checks to replace unhealthy instances.
Why this is correct
Multiple AZs provide high availability and health checks ensure quick replacement.
- ✗
Use a larger AMI to reduce boot times.
Why it's wrong here
Boot time reduction does not solve the AZ failure issue.
- ✗
Increase the instance size of the EC2 instances to handle more traffic.
Why it's wrong here
Instance size impacts performance, not resilience to AZ failure.
- ✗
Configure the Auto Scaling group to launch instances in a single AZ with a larger instance count.
Why it's wrong here
A single AZ is a single point of failure.
Go deeper
Related to this question
About these practice questions
One of 251 original DOP-C02 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
3 more ways this is tested on DOP-C02
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company runs a critical web application on EC2 instances behind an Application Load Balancer. To improve resilience, they want to automatically replace unhealthy instances. Which AWS feature should they use?
easy- ✓ A.Auto Scaling group with ELB health checks
- B.CloudWatch alarm that terminates the instance
- ✓ C.AWS Lambda function that checks health and launches new instances
- D.Elastic Load Balancer health checks
Why A: Auto Scaling groups with ELB health checks automatically replace unhealthy instances by terminating and launching new ones. AWS Lambda functions can also be used to check health and launch new instances, providing a custom automation solution. Option A is the native recommended approach, while option C is a valid custom implementation. Option B is wrong because CloudWatch alarms can terminate instances but do not automatically launch replacements; Auto Scaling is needed. Option D is wrong because ELB health checks only mark instances unhealthy; they do not perform any replacement action.
Variation 2. A company runs a critical web application on EC2 instances behind an Application Load Balancer. To improve resilience, they want to automatically replace failed instances. Which AWS service should they use?
medium- A.EC2 Instance Recovery
- B.AWS Systems Manager Automation
- C.CloudFormation Stack update
- ✓ D.Auto Scaling group with health checks
Why D: Auto Scaling groups with health checks automatically replace unhealthy instances based on ELB health check integration. Option D is correct. Option A (EC2 Instance Recovery) recovers instances on the same host but does not replace them if the host fails. Option B (Systems Manager Automation) requires manual or scheduled automation, not automatic health-based replacement. Option C (CloudFormation Stack update) does not provide auto-replacement; it manages infrastructure updates.
Variation 3. A company runs a stateless web application on EC2 instances behind an Application Load Balancer. To improve resilience, which configuration should be used for the EC2 instances?
easy- A.Use one EC2 instance with a larger instance type
- B.Use a single, large EC2 instance in one Availability Zone
- C.Use multiple EC2 instances in one Availability Zone with health checks disabled
- ✓ D.Use multiple EC2 instances across two or more Availability Zones
Why D: D is correct because deploying multiple EC2 instances across two or more Availability Zones (AZs) ensures high availability and fault tolerance. If one AZ fails, the Application Load Balancer (ALB) automatically routes traffic to healthy instances in other AZs, maintaining service continuity. This aligns with the AWS Well-Architected Framework's resilience best practices for stateless applications.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DOP-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DOP-C02 exam.