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.)
The weight for the Region where the web servers were stopped is higher than the weight for the other Region.
One of the web servers in the secondary Region did not pass its HTTP health check.
Latency resource record sets cannot be used in combination with weighted resource record sets.
The setting to evaluate target health is not turned on for the latency alias resource record set that is associated with the domain in the Region where the web servers were stopped.
An HTTP health check has not been set up for one or more of the weighted resource record sets associated with the stopped web servers.
I strategize that the answer is:
The setting to evaluate target health is not turned on for the latency alias resource record set that is associated with the domain in the Region where the web servers were stopped.