Route 53 Health Checks for Weighted Records

SOA-C03 By islever Editorial Last updated

Implement highly available and resilient environments.

Short answer

A Add a Route 53 health check for each of the weighted records to ensure Route 53 stops routing traffic to unhealthy endpoints.

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?
  1. Add a Route 53 health check for each of the weighted records that received traffic during the recent update. Correct Answer
  2. Increase the weight of Route 53 records in the Region where traffic must go during updates.
  3. Reconfigure all records to use latency-based routing across all Regions uniformly.
  4. Reduce the TTL value for latency-based routing to detect changes more quickly.

Key Takeaways

Tests the critical requirement that Route 53 does not automatically detect endpoint health for standard records; you must explicitly associate health checks with DNS records to remove unhealthy targets.

Learn why Route 53 continues routing traffic to unhealthy endpoints when health checks are missing and how to implement them for weighted records to ensure resiliency.

Common mistake: Candidates often choose reducing TTL or changing weights, failing to realize these only affect caching or distribution ratios but do not prevent traffic from being sent to failed endpoints.

Expert Analysis

Why the Answer Is Correct

Route 53 does not automatically evaluate the health of non-alias DNS records. To prevent traffic from being routed to unhealthy Availability Zone endpoints, you must create a Route 53 health check for each endpoint and associate it with the corresponding weighted record. When the health check fails, Route 53 automatically stops including that record in DNS responses, effectively removing the unhealthy endpoint.

Why the Other Options Are Wrong

Option B (increasing weight) merely changes the proportion of traffic directed to healthy zones but does not stop traffic from going to unhealthy ones if they are still registered. Option C (reconfiguring to latency-based) ignores the immediate need for health monitoring and doesn't solve the underlying lack of health detection. Option D (reducing TTL) speeds up DNS cache expiration but does not trigger Route 53 to stop sending traffic to a known bad endpoint during an active failure.

Community Comment Notes

Community consensus strongly supports Option A, with users noting that 'Route 53 does not automatically determine the health of ordinary non-alias records' and emphasizing that associating health checks is the standard solution for this scenario.

Exam Strategy

Always look for explicit health check associations when Route 53 routing issues involve unhealthy endpoints. Remember that Alias records can have 'Evaluate Target Health' enabled, but standard records require manual health check association.

Frequently Asked Questions

Why doesn't Route 53 auto-detect unhealthy endpoints?

Route 53 only evaluates health automatically for Alias records with 'Evaluate Target Health' set to Yes. Standard records require explicit health check association.

Can I use TTL reduction to fix unhealthy endpoint routing?

No. Reducing TTL only affects how quickly clients refresh cached DNS records. It does not make Route 53 aware of endpoint failures or exclude them from responses.

More SOA-C03 FAQ →

Discussion 3 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 3

  1. BAL007RAJ 👍 1 Answered A
    Exam memory tip Route 53 sends traffic to unhealthy records → configure health checks. Alias record → Evaluate Target Health = Yes. Route 53 does not automatically determine the health of ordinary non-alias records. Associate a health check with each weighted record so Route 53 removes an unhealthy Availability Zone endpoint from DNS responses. Why the others are incorrect B: Changing weights affects traffic distribution, not endpoint-health detection. C: Latency routing selects between Regions; it does not automatically detect unhealthy endpoints within each Region. D: Lowering DNS TTL causes clients to refresh records sooner but does not make Route 53 recognize an unhealthy endpoint.
  2. Derel1ct 👍 1 Answered A
    B. Manual and human driven, this is not going to prevent the traffic from being routed to unhealthy endpoints. C. More or less defeats the purpose of using latency-based routing, also doesn't implement a health check so traffic will still be routed to unhealthy instances. D. TTL value changes is just going to affect cache time of the DNS response, again does nothing for finding and avoiding unhealthy endpoints.
  3. JSTech 👍 1 Answered A
    Route 53 will not automatically know an endpoint is unhealthy unless you configure health checks and associate them with the DNS records

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Resolving Private IPv4 Exhaustion in AWS VPCs

S-grade

How Do You Ramp ALB Traffic Gradually During EC2 Cache Warm-Up?

S-grade

Avoiding Permanent Credentials with AWS STS

S-grade

Automate EC2 Reboot with Systems Manager Maintenance Windows

S-grade

Practice All SOA-C03 Questions

Access 100 questions with complete answers and detailed explanations.

View Full SOA-C03 Practice Test →

← Back to SOA-C03 Study Guide