easymultiple choiceObjective-mapped

Your web tier runs on an EC2 Auto Scaling group behind an Application Load Balancer (ALB). You currently deploy both the ALB and the Auto Scaling group in only two Availability Zones (AZs). One AZ fails. What is the best configuration change to improve resilience?

Question 1easymultiple choice
Full question →

Your web tier runs on an EC2 Auto Scaling group behind an Application Load Balancer (ALB). You currently deploy both the ALB and the Auto Scaling group in only two Availability Zones (AZs). One AZ fails. What is the best configuration change to improve resilience?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Reduce health check timeouts so instances are replaced sooner in the failed AZ.

Health check tuning can change how quickly instances are marked unhealthy and replaced, but it does not increase usable capacity in the remaining AZ. If the remaining AZ cannot sustain load, outages can still occur.

B

Best answer

Add a third Availability Zone so the ALB and Auto Scaling group span at least three AZs.

An AZ failure typically reduces available capacity to the other AZs. Spreading the ALB subnets and ASG instances across at least three AZs reduces the impact of losing any single AZ and helps ensure the remaining AZs can continue serving traffic.

C

Distractor review

Enable instance scale-in protection to stop the ASG from terminating unhealthy instances.

Scale-in protection primarily affects scale-in actions (for example, terminating instances due to decreasing desired capacity). It does not solve the capacity-loss problem during an AZ failure, and it can interfere with replacing instances based on unhealthy status and replacement policies.

D

Distractor review

Switch the ALB to an internal Network Load Balancer (NLB) to avoid cross-AZ traffic.

Changing from ALB to NLB does not provide additional AZ fault tolerance for the compute capacity placement. Cross-AZ traffic considerations are separate from handling an AZ outage.

Common exam trap

Common exam trap: usable hosts are not the same as total addresses

Subnetting questions often tempt you into counting all addresses. In normal IPv4 subnets, the network and broadcast addresses are not usable host addresses.

Technical deep dive

How to think about this question

Subnetting questions test whether you can identify the network, broadcast address, usable range, mask and correct subnet. Slow down enough to calculate the block size correctly.

KKey Concepts to Remember

  • CIDR notation defines the prefix length.
  • Block size helps identify subnet boundaries.
  • Network and broadcast addresses are not usable hosts in normal IPv4 subnets.
  • The required host count determines the smallest suitable subnet.

TExam Day Tips

  • Write the block size before choosing the subnet.
  • Check whether the question asks for hosts, subnets or a specific address range.
  • Do not confuse /24, /25, /26 and /27 host counts.

Related practice questions

Related SAA-C03 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

CIDR notation defines the prefix length.

What is the correct answer to this question?

The correct answer is: Add a third Availability Zone so the ALB and Auto Scaling group span at least three AZs. — The most important resilience lever for an ALB + Auto Scaling group is to distribute both the load balancer and compute capacity across multiple AZs. With only two AZs, losing one AZ can leave you with reduced capacity (potentially not enough to serve requests). Adding a third AZ—by configuring the ALB with subnets in three AZs and configuring the ASG with subnets in three AZs—ensures that if one AZ fails, the remaining AZs can continue to serve traffic and maintain availability. A focuses on detection/replacement timing within the failed AZ, but the core issue is insufficient capacity across AZs after one fails. C can hinder proper replacement and does not create additional capacity in other AZs. D addresses traffic flow characteristics, not AZ-level fault tolerance of the deployed resources.

What should I do if I get this SAA-C03 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.