QuestionQ23

VerifiedDesign Solutions for Organizational Complexity

A solutions architect has deployed a web application serving users in two AWS Regions under a custom domain. The application uses Amazon Route 53 latency-based routing. For each Region, the solutions architect has associated weighted record sets with two web servers in separate Availability Zones.

The solutions architect performs a disaster-recovery scenario. After all web servers in one Region are stopped, Route 53 does not automatically redirect users to the other Region.

Which of the following could be root causes of this issue?

Choose two
Explanation

For a latency alias record that points to weighted records in the same hosted zone, Evaluate target health must be enabled for Route 53 to use the health of that target group. The referenced weighted records also need health checks; a record without an associated health check is considered healthy, even when its web server has been stopped. Consequently, Route 53 can continue returning the failed Region unless the latency alias evaluates target health and the weighted records are health-checked.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!