A company runs a web application with endpoints in the `us-east-1` Region, the `us-west-2` Region, and an on-premises data center in Chicago. A SysOps administrator must configure Amazon Route 53 to route client traffic to the closest physical endpoint. During scheduled maintenance of the Chicago data center, the administrator needs to redirect a portion of the traffic that would normally route to Chicago to the `us-east-1` Region instead, without altering the DNS endpoint IP addresses or physical locations.
Which Route 53 configuration should the SysOps administrator use to meet these requirements?
- Configure a Geoproximity routing policy using Route 53 Traffic Flow. Define the endpoints for the AWS Regions and specify the latitude and longitude coordinates for the Chicago data center. To shift traffic away from Chicago to the `us-east-1` Region, apply a negative bias to the Chicago endpoint and a positive bias to the `us-east-1` endpoint.Answer
- BConfigure a Latency-based routing policy with resource record sets for the three endpoints. For the Chicago data center, create a CNAME record at the zone apex pointing to the on-premises IP address. Lower the TTL on the Chicago record to force client DNS resolvers to query Route 53 more frequently during the maintenance window.
- CConfigure a Geolocation routing policy with records mapping specific US states to either the AWS Regions or the Chicago on-premises IP address. When the maintenance starts, manually delete the state mappings for Chicago and recreate them pointing to the `us-east-1` Region.
- DConfigure a Geoproximity routing policy by creating standard alias records at the zone apex in the Route 53 console. Specify the IP address of the Chicago data center as a CNAME record and set a positive routing bias directly on that CNAME record to shift traffic to the other endpoints.
Answer
Configure a Geoproximity routing policy using Route 53 Traffic Flow. Define the endpoints for the AWS Regions and specify the latitude and longitude coordinates for the Chicago data center. To shift traffic away from Chicago to the `us-east-1` Region, apply a negative bias to the Chicago endpoint and a positive bias to the `us-east-1` endpoint.
The correct option outlines configuring a Geoproximity routing policy using Route 53 Traffic Flow, mapping the on-premises coordinates, and applying a negative bias to the Chicago endpoint alongside a positive bias to the `us-east-1` endpoint. Geoproximity routing requires Route 53 Traffic Flow and supports specifying coordinates for non-AWS resources. Applying a negative bias shrinks the routing footprint of the Chicago endpoint, while a positive bias expands the routing footprint of the `us-east-1` endpoint, successfully shifting traffic.
Step-by-Step Solution
Key Concept
Amazon Route 53 Geoproximity routing policy using Traffic Flow and bias adjustments for hybrid endpoints.
Estimated Time:2m 0s