easymultiple choiceObjective-mapped

Exhibit

Auto Scaling group configuration:
- Desired capacity: 4
- VPC subnets: subnet-0a11 (us-east-1a) only
- Health check type: ELB

Application Load Balancer configuration:
- Enabled subnets: subnet-0a11 (us-east-1a), subnet-0b22 (us-east-1b)

Incident note:
- A planned test stopped all instances in us-east-1a and the application became unavailable.

Based on the exhibit, a web application must stay available if one Availability Zone fails. What is the best change to improve resilience?

Question 1easymultiple choice
Full question →

Based on the exhibit, a web application must stay available if one Availability Zone fails. What is the best 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

Increase the desired capacity to 8 instances in the same subnet.

More instances in one Availability Zone do not protect against the Zone itself failing. Capacity increases, but resilience does not.

B

Best answer

Add a subnet in another Availability Zone to the Auto Scaling group and keep the ALB spanning both AZs.

This places application instances across multiple Availability Zones, which protects the stateless tier from a single-AZ failure. The ALB already spans two AZs, so the missing piece is the Auto Scaling group using subnets in more than one AZ. That allows AWS to replace unhealthy instances and continue serving traffic from the surviving Zone.

C

Distractor review

Replace the Application Load Balancer with a Network Load Balancer.

A different load balancer type does not fix the single-AZ compute placement problem. The application still has no surviving instances in another Zone.

D

Distractor review

Move the instances to a larger instance type with more CPU and memory.

Bigger instances can improve performance, but they do not add Availability Zone redundancy. A larger instance in one AZ is still a single point of failure.

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 subnet in another Availability Zone to the Auto Scaling group and keep the ALB spanning both AZs. — For high availability, the application tier must be spread across at least two Availability Zones. The exhibit shows the ALB already spans us-east-1a and us-east-1b, but the Auto Scaling group launches instances only in us-east-1a. If that Zone fails, no instances remain to serve traffic. Adding a second subnet from another AZ lets the ASG place and replace instances across Zones, which is the standard multi-AZ pattern for resilient stateless applications. Why others are wrong: Increasing instance count, changing load balancer type, or using larger instances may help capacity or performance, but none of them eliminate the single-AZ dependency. The problem is placement, not size or load balancer selection. The application needs instances in more than one Availability Zone to survive an AZ outage.

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.