You have deployed a web application targeting a global audience across multiple AWS Regions under the
domain name.example.com. You decide to use Route53 Latency-Based Routing to serve web requests to users
from the region closest to the user. To provide business continuity in the event of server downtime you
configure weighted record sets associated with two web servers in separate Availability Zones per region.
Dunning a DR test you notice that when you disable all web servers in one of the regions Route53 does not
automatically direct all users to the other region. What could be happening? (Choose 2 answers)
A.
Latency resource record sets cannot be used in combination with weighted resource record sets.
B.
You did not setup an http health check tor one or more of the weighted resource record sets associated
with me disabled web servers.
C.
The value of the weight associated with the latency alias resource record set in the region with the disabled
servers is higher than the weight for the other region.
D.
One of the two working web servers in the other region did not pass its HTTP health check.
E.
You did not set “Evaluate Target Health” to “Yes” on the latency alias resource record set associated with
example com in the region where you disabled the servers.
Hi,
I think the correct answers are B and E
Any thoughts on this are welcome.
Thanks,
Frank
See also: http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-complex-configs.html
For both latency alias resource record sets, you set the value of “Evaluate Target Health” to Yes. You use the Evaluate Target Health setting for each latency alias resource record set to make Amazon Route 53 evaluate the health of the alias targets—the weighted resource record sets—and respond accordingly.
1
0
Agree on B and E
0
0
I will go with B and D. See properly in the option E they have mentioned that about the disabled servers not the working servers. It doesn’t make any sense even if you have selected yes or no flag when you have disabled the servers because no health check will happen due to unavailability of the instances.
But if you have not selected the Evaluate Target Health to “Yes” on the failover instance then you can go with option E.
0
0
D is wrong, because if one server fail, the other server still work.
0
0
BE is the answer franks explanation is correct
0
0
B&E
0
0
Answer should be A & E.
Latency record can not be combined with weighted record set.
0
0
B & E is correct.
A is wrong because: ..you might use latency alias resource record sets to select a region close to a user and use weighted resource record sets for two or more resources within each region to protect against the failure of a single endpoint or an Availability Zone…
From this link: http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-complex-configs.html#dns-failover-complex-configs-eth-no
E is right because: http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-complex-configs.html#dns-failover-complex-configs-eth-no
0
0
B & E
0
0
B and E
0
0
I think B & E correct
0
0
“B. You did not setup an HTTP health check to one or more of the weighted resource record sets
associated with me disabled web servers.
E. You did not set “”Evaluate Target Health”” to “”Yes”” on the latency alias resource record set associated
with example com in the region where you disabled the servers.”
0
0