ExamGecko
Question list
Search
Search

List of questions

Search

Related questions











Question 451 - SAP-C02 discussion

Report
Export

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 issue1? (Select TWO)

A.
The weight for the Region where the web servers were stopped is higher than the weight for the other Region.
Answers
A.
The weight for the Region where the web servers were stopped is higher than the weight for the other Region.
B.
One of the web servers in the secondary Region did not pass its HTTP health check
Answers
B.
One of the web servers in the secondary Region did not pass its HTTP health check
C.
Latency resource record sets cannot be used in combination with weighted resource record sets
Answers
C.
Latency resource record sets cannot be used in combination with weighted resource record sets
D.
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.
Answers
D.
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.
E.
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
Answers
E.
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
Suggested answer: D, E

Explanation:

Evaluate Target Health Setting:

Ensure that the 'Evaluate Target Health' setting is enabled for the latency alias resource record sets in Route 53. This setting helps Route 53 determine the health of the resources associated with the alias record and redirect traffic appropriately.

HTTP Health Checks:

Configure HTTP health checks for all weighted resource record sets. Health checks monitor the availability and performance of the web servers, allowing Route 53 to reroute traffic to healthy servers in case of a failure.

Verify that the health checks are correctly set up and associated with the resource record sets. This ensures that Route 53 can detect server failures and redirect traffic to the servers in the other Region.

By enabling the 'Evaluate Target Health' setting and configuring HTTP health checks, Route 53 can effectively manage traffic during failover scenarios, ensuring high availability and reliability.

Reference

AWS Route 53 Documentation on Latency-Based Routing50.

AWS Architecture Blog on Cross-Account and Cross-Region Setup49.

asked 16/09/2024
Sebrena Adkins
42 questions
User
Your answer:
0 comments
Sorted by

Leave a comment first