Explanation:
Amazon Route 53 health checks are essential for identifying unhealthy endpoints. When health checks are associated with resource record sets (like weighted A records), Route 53 monitors the health of the targets. If a target is found to be unhealthy, Route 53 stops including it in DNS query responses and fails over to other healthy records. Without these health checks, Route 53 will continue to route traffic based on the routing policy (latency or weight) even if the underlying instance or resource is down. Reducing TTL (Option D) helps DNS propagation speed but does not enable health detection itself.
Ultimate access to all questions.
Question #12 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?
A
Add a Route 53 health check for each of the weighted records that received traffic during the recent update.
B
Increase the weight of Route 53 records in the Region where traffic must go during updates.
C
Reconfigure all records to use latency-based routing across all Regions uniformly.
D
Reduce the TTL value for latency-based routing to detect changes more quickly.
E
null
F
null
No comments yet.