nerdexam
Amazon

SOA-C03 · Question #87

A company uses Amazon Route 53 with latency-based routing across multiple AWS Regions to provide resiliency. The company uses Route 53 with latency-based routing to direct traffic to the nearest…

The correct answer is A. Add a Route 53 health check for each of the weighted records that received traffic during the. In Route 53 latency-based routing, traffic is routed to the Region with the lowest latency, and within each Region, weighted records can distribute traffic across multiple endpoints. However, if the weighted records lack individual health checks, Route 53 cannot detect endpoint…

Submitted by parkjh· Mar 5, 2026Reliability and business continuity

Question

A company uses Amazon Route 53 with latency-based routing across multiple AWS Regions to provide resiliency. The company uses Route 53 with latency-based routing to direct traffic to the nearest Region. Within each Region, weighted A records distribute traffic across multiple Availability Zones. During a recent update, some Availability Zone endpoints became unhealthy. Route 53 continued to route traffic to the unhealthy endpoints. The company must prevent this issue from occurring in the future. Which solution will meet this requirement?

Options

  • AAdd a Route 53 health check for each of the weighted records that received traffic during the
  • BIncrease the weight of Route 53 records in the Region where traffic must go during updates.
  • CReconfigure all records to use latency-based routing across all Regions uniformly.
  • DReduce the TTL value for latency-based routing to detect changes more quickly.

How the community answered

(63 responses)
  • A
    81% (51)
  • B
    3% (2)
  • C
    6% (4)
  • D
    10% (6)

Explanation

In Route 53 latency-based routing, traffic is routed to the Region with the lowest latency, and within each Region, weighted records can distribute traffic across multiple endpoints. However, if the weighted records lack individual health checks, Route 53 cannot detect endpoint failures and continues routing traffic to unhealthy targets. Attaching a Route 53 health check to each weighted record ensures that only healthy endpoints receive traffic, preventing recurrence of the issue.

Topics

#Route 53 health checks#latency-based routing#weighted records#failover

Community Discussion

No community discussion yet for this question.

Full SOA-C03 Practice