SAP-C02 · Question #226
A solutions architect has deployed a web application that serves users across two AWS Regions under a custom domain. The application uses Amazon Route 53 latency-based routing. The solutions…
The correct answer is A. The weight for the Region where the web servers were stopped is higher than the weight for the E. An http health check has not been set up for one or more of the weighted resource record sets. When Route 53 latency-based routing fails to redirect users after web servers in one region stop, it is likely due to the absence of health checks and potentially a higher weight assigned to the failed region.
Question
A solutions architect has deployed a web application that serves users across two AWS Regions under a custom domain. The application uses Amazon Route 53 latency-based routing. The solutions architect has associated weighted record sets with a pair of web servers in separate Availability Zones for each Region. The solutions architect runs a disaster recovery scenario. When all the web servers in one Region are stopped Route 53 does not automatically redirect users to the other Region. Which of the following are possible root causes of this issue? (Choose two.)
Options
- AThe weight for the Region where the web servers were stopped is higher than the weight for the
- BOne of the web servers in the secondary Region did not pass its http health check
- CLatency resource record sets cannot be used in combination with weighted resource record sets
- DThe setting to evaluate target health is not turned on for the latency alias resource record set that
- EAn http health check has not been set up for one or more of the weighted resource record sets
How the community answered
(21 responses)- A62% (13)
- B19% (4)
- C5% (1)
- D14% (3)
Why each option
When Route 53 latency-based routing fails to redirect users after web servers in one region stop, it is likely due to the absence of health checks and potentially a higher weight assigned to the failed region.
If HTTP health checks are not set up, and the weight for the stopped region was higher, Route 53 would continue to direct a larger proportion of traffic to the unavailable servers, preventing effective redirection to the healthy region.
The failure of only one web server in the secondary region would not prevent redirection from a primary region where all web servers are stopped, assuming health checks are functioning correctly.
Latency-based routing and weighted routing policies can be used in combination within Amazon Route 53 configurations.
While 'Evaluate target health' is critical for alias records pointing to load balancers or other AWS resources, the core issue described by E is the absence of health checks on the weighted record sets themselves.
If HTTP health checks are not configured for the weighted resource record sets, Amazon Route 53 cannot determine the health status of the web servers and will continue to send traffic to the stopped instances based on existing routing policies.
Concept tested: Route 53 Latency-based and Weighted Routing with Health Checks
Source: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/AboutHealthChecks.html
Community Discussion
No community discussion yet for this question.