easymultiple choiceObjective-mapped

An organization hosts the same public API in two AWS Regions. Normal traffic should go to the primary Region. If the primary endpoint becomes unhealthy, Route 53 should automatically route users to the secondary Region. What is the best Route 53 configuration approach?

Question 1easymultiple choice
Full question →

An organization hosts the same public API in two AWS Regions. Normal traffic should go to the primary Region. If the primary endpoint becomes unhealthy, Route 53 should automatically route users to the secondary Region. What is the best Route 53 configuration approach?

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

Use simple routing with one record that contains both regions as weighted targets.

Simple routing returns a single set of resource record values and does not implement health-check-driven failover logic. There is no automatic switch based on endpoint health.

B

Distractor review

Use weighted routing and set the secondary Region weight to 0 until needed.

Weighted routing distributes traffic based on the configured weights. Changing weights is typically a manual process, and routing is not automatically switched solely because a health check marks the primary as unhealthy.

C

Best answer

Use Route 53 failover routing with health checks that mark the primary as unhealthy and fail over to the secondary.

Failover routing is designed for active/passive disaster recovery. You configure a primary record and a secondary record, each associated with health checks. When the primary fails its health checks, Route 53 automatically resolves the name to the secondary target.

D

Distractor review

Use latency-based routing so requests go to the region with the lowest latency, regardless of health.

Latency-based routing optimizes toward the lowest observed latency. Even if an endpoint is unhealthy, latency-based decisions are not a health-check failover mechanism by default.

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: Use Route 53 failover routing with health checks that mark the primary as unhealthy and fail over to the secondary. — Use Route 53 failover routing. This pattern is intended for disaster recovery where one region is active and the other is standby. You create two records for the same name: one configured as the primary and the other as the secondary. Route 53 continuously evaluates health checks for the primary endpoint. If the primary is marked unhealthy, Route 53 automatically starts responding with the secondary region’s target, allowing clients to recover without manual DNS changes. Simple routing does not switch based on health. Weighted routing changes traffic allocation based on weights, not on health-check state. Latency-based routing may change destinations based on performance but is not the same as a strict health-based failover strategy for region 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.