mediummultiple choiceObjective-mapped

Exhibit

Current deployment:
  Application Load Balancer subnets: subnet-a1 (AZ-a), subnet-a2 (AZ-a)
  Auto Scaling group subnets: subnet-a1 (AZ-a) only
  Desired capacity: 4 instances
  Minimum capacity: 4 instances

Incident report:
  2026-04-18T09:21Z AZ-a experienced a power issue
  2026-04-18T09:22Z all targets became unhealthy
  2026-04-18T09:25Z service returned HTTP 503 to users

Based on the exhibit, the application should continue serving requests if one Availability Zone fails. Which change best improves resilience with the least operational complexity?

Question 1mediummultiple choice
Full question →

Based on the exhibit, the application should continue serving requests if one Availability Zone fails. Which change best improves resilience with the least operational complexity?

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

Increase the desired capacity in AZ-a so more instances can absorb the failure of that same Availability Zone.

Adding more instances in the same Availability Zone does not protect against an AZ-wide outage because all of those instances fail together.

B

Best answer

Add at least one subnet from a second Availability Zone to both the ALB and the Auto Scaling group.

A resilient design needs the load balancer and the Auto Scaling group to span multiple Availability Zones. If one AZ fails, the ALB can still route to healthy targets in the remaining AZs and the Auto Scaling group can replenish capacity there. This is the simplest and most common way to achieve AZ-level fault tolerance.

C

Distractor review

Disable health checks so the ALB stops removing targets during brief infrastructure issues.

Disabling health checks hides failures instead of recovering from them. The load balancer would continue sending traffic to unhealthy targets, which makes the outage worse rather than better.

D

Distractor review

Move the application to a single larger instance type so the fleet has fewer moving parts.

A single larger instance increases concentration risk and does not remove the Availability Zone single point of failure. It reduces the number of instances, but it also reduces redundancy.

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 at least one subnet from a second Availability Zone to both the ALB and the Auto Scaling group. — The issue is that both the ALB and the Auto Scaling group are pinned to one Availability Zone. To survive an AZ loss, they need subnets in at least two AZs so traffic and capacity can shift to healthy infrastructure automatically. This is the standard high-availability pattern for EC2 applications behind an ALB, and it adds resilience without major operational complexity. Scaling up inside the same AZ does not help when the entire AZ fails. Disabling health checks prevents the system from removing bad targets and delays recovery. Using one larger instance makes the design less resilient, not more, because it creates a larger single point of failure with no redundancy.

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.