easymultiple choiceObjective-mapped

Your company hosts an internal API in two AWS Regions. You want Amazon Route 53 to automatically send traffic to the secondary Region if the primary Region’s endpoint becomes unhealthy. Which Route 53 configuration best meets this requirement?

Question 1easymultiple choice
Full question →

Your company hosts an internal API in two AWS Regions. You want Amazon Route 53 to automatically send traffic to the secondary Region if the primary Region’s endpoint becomes unhealthy. Which Route 53 configuration best meets this requirement?

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

Latency-based routing with health checks for both Regions.

Latency-based routing chooses the Region primarily based on measured latency. Health checks can remove an endpoint from routing if unhealthy, but it does not guarantee that all traffic switches to a specific secondary Region as a deliberate primary/backup failover policy.

B

Best answer

Failover routing with a primary record associated with a health check, and a secondary (failover) record associated with its own health check settings.

Route 53 failover routing is explicitly designed for primary/secondary behavior. When the primary record’s health check fails, Route 53 automatically routes to the secondary (failover) record, matching the stated requirement.

C

Distractor review

Weighted routing to distribute traffic evenly across both Regions.

Weighted routing sends a configured percentage of traffic to each Region under normal conditions. Even if one endpoint becomes unhealthy, weighted routing by itself does not implement a strict “switch all traffic to the secondary when primary fails” pattern without additional failover-specific configuration.

D

Distractor review

Geolocation routing based on the client’s country to choose a Region.

Geolocation routing selects endpoints based on where the user is located, not based on the health of the primary Region’s endpoint. It does not provide health-based regional failover.

Common exam trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

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?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Failover routing with a primary record associated with a health check, and a secondary (failover) record associated with its own health check settings. — Route 53 failover routing is built for scenarios with a designated primary Region and a designated secondary Region. Route 53 uses health checks to determine whether the primary record is healthy; when it becomes unhealthy, Route 53 automatically responds to DNS queries using the secondary (failover) record. Latency, weighted, and geolocation routing can influence normal selection, but they are not the mechanism that provides deterministic health-based failover to a specific secondary Region. Option A may stop routing to an unhealthy endpoint, but it still does not provide the explicit primary/secondary failover intent. Option C continues to distribute traffic according to weights rather than switching all traffic to a designated backup when the primary fails. Option D ignores endpoint health and cannot react to regional outages.

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.