SAA-C03 Design Resilient Architectures Practice Question
This SAA-C03 practice question tests your understanding of design resilient architectures. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. A key principle to apply: auto Scaling groups can span multiple Availability Zones.. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A trading dashboard runs on EC2 instances behind an Application Load Balancer. The design must tolerate the failure of one Availability Zone. What should the Auto Scaling group configuration include? The design must avoid adding custom operational scripts.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Subnets in at least two Availability Zones with health checks enabled
Option B is correct because distributing EC2 instances across at least two Availability Zones (AZs) ensures that the Auto Scaling group can maintain capacity even if one AZ fails. Enabling health checks on the Application Load Balancer (ALB) allows the group to automatically replace unhealthy instances without custom scripts, meeting the fault-tolerance requirement.
Key principle: Auto Scaling groups can span multiple Availability Zones.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
A single EC2 instance with detailed monitoring
Why it's wrong here
Monitoring does not provide redundancy.
✓
Subnets in at least two Availability Zones with health checks enabled
Why this is correct
An Auto Scaling group spanning multiple AZs can replace unhealthy instances and maintain capacity during an AZ failure.
Related concept
Auto Scaling groups can span multiple Availability Zones.
✗
All instances in one larger subnet
Why it's wrong here
One AZ remains a single point of failure.
✗
A Network Load Balancer in one subnet
Why it's wrong here
A load balancer in one AZ does not make the application resilient to AZ failure.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse using a load balancer (like an NLB) with achieving AZ redundancy, but without multi-AZ subnets in the Auto Scaling group, the architecture remains single-AZ and vulnerable to failure.
Detailed technical explanation
How to think about this question
Auto Scaling groups distribute instances evenly across the specified subnets (one per AZ) by default, and the ALB health check (HTTP/HTTPS) triggers instance replacement when the target fails. Under the hood, the group uses Amazon EC2 Auto Scaling lifecycle hooks and the ELB health check integration to mark instances as unhealthy, avoiding reliance on custom scripts or manual intervention.
KKey Concepts to Remember
Auto Scaling groups can span multiple Availability Zones.
Health checks are used by Auto Scaling groups to identify and replace unhealthy instances.
Multi-AZ deployment protects against single Availability Zone failures.
Auto Scaling groups automatically maintain desired capacity without manual intervention.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Auto Scaling groups can span multiple Availability Zones.
Real-world example
How this comes up in practice
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
What to study next
Got this wrong? Here's your next step.
Review auto Scaling groups can span multiple Availability Zones., then practise related SAA-C03 questions on the same topic to reinforce the concept.
Design Resilient Architectures — This question tests Design Resilient Architectures — Auto Scaling groups can span multiple Availability Zones..
What is the correct answer to this question?
The correct answer is: Subnets in at least two Availability Zones with health checks enabled — Option B is correct because distributing EC2 instances across at least two Availability Zones (AZs) ensures that the Auto Scaling group can maintain capacity even if one AZ fails. Enabling health checks on the Application Load Balancer (ALB) allows the group to automatically replace unhealthy instances without custom scripts, meeting the fault-tolerance requirement.
What should I do if I get this SAA-C03 question wrong?
Review auto Scaling groups can span multiple Availability Zones., then practise related SAA-C03 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Auto Scaling groups can span multiple Availability Zones.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This SAA-C03 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 SAA-C03 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.