SOA-C02 · Question #727
A company configures an Amazon Route 53 public hosted zone. The company wants traffic to fail over to a backup web server whenever the primary web server becomes unreachable. The company configures…
The correct answer is A. Associate the Route 53 health check with the primary server's DNS record. Failover routing works only when the primary record is associated with a health check. Without that association, Route 53 can’t mark the primary as unhealthy and switch queries to the backup
Question
A company configures an Amazon Route 53 public hosted zone. The company wants traffic to fail over to a backup web server whenever the primary web server becomes unreachable. The company configures a Route 53 health check for the primary web server. A connectivity issue causes the primary server to be unreachable. However, traffic does not fail over to the backup server. A SysOps administrator must resolve the failover issue. Which solution will meet this requirement?
Options
- AAssociate the Route 53 health check with the primary server's DNS record.
- BConfigure a Route 53 health check for the backup web server.
- CSeta TTL of zero for the primary server's DNS record.
- DEnsure that the backup web server is in the same AWS Region as the primary web server.
How the community answered
(24 responses)- A75% (18)
- B13% (3)
- C8% (2)
- D4% (1)
Explanation
Failover routing works only when the primary record is associated with a health check. Without that association, Route 53 can’t mark the primary as unhealthy and switch queries to the backup
Topics
Community Discussion
No community discussion yet for this question.