Examkin

Question

Difficulty: MediumAmazon Route 53 DNS Configuration and Routing Policies

An organization serves its backend API at api.service.com using Application Load Balancers (ALBs) deployed in the us-east-1 and eu-west-1 AWS regions. A SysOps Administrator must configure Amazon Route 53 to route client traffic to the nearest regional ALB based on the client's geographic location. If a regional ALB becomes unhealthy, traffic from that region must fail over to a default backup endpoint. Which combination of configuration steps will satisfy these requirements? (Select TWO.)

  1. Create Geolocation Alias A records for api.service.com mapped to the ALBs in their respective regions, and set Evaluate Target Health to Yes.Answer
  2. Create a Geolocation Alias A record for api.service.com with the location set to Default, mapped to the backup endpoint.Answer
  3. C
    Create CNAME records for api.service.com targeting the ALB DNS names, and configure a Latency routing policy with standard DNS health checks.
  4. D
    Create a Failover routing policy for api.service.com with the primary endpoint set to the us-east-1 ALB and the secondary set to the eu-west-1 ALB.
  5. E
    Configure a Geoproximity routing policy for both regional ALBs and apply a positive bias to the backup endpoint to handle traffic spikes.

Answer

The correct configuration requires creating Geolocation Alias A records for the specific regions with Evaluate Target Health enabled, alongside a Default Geolocation Alias A record mapped to the backup endpoint.
To route users based on their geographic location, Geolocation routing records must be created for the respective regions. By using Alias A records pointing to the Application Load Balancers (ALBs) and enabling 'Evaluate Target Health', Amazon Route 53 automatically monitors the health of the ALBs. Creating a 'Default' geolocation record ensures that if an ALB in a specific region is unhealthy, or if a user accesses the API from an unmapped location, Route 53 will fail over and route the traffic to the specified default backup endpoint.

Step-by-Step Solution

1
Configure regional Geolocation records.
Create Geolocation Alias A records for api.service.com pointing to the respective ALBs in us-east-1 and eu-west-1, enabling Evaluate Target Health.
This routes users from those geographic regions to the nearest ALB and allows Route 53 to monitor the health of each ALB automatically.
2
Configure the default fallback record.
Create a Geolocation Alias A record for api.service.com with the location set to Default, pointing to the backup endpoint.
This serves as the destination for users from locations not explicitly mapped, and functions as the failover target if the regional ALBs are unhealthy.

Key Concept

Amazon Route 53 Geolocation routing with health checks and default fallback behavior.
Estimated Time:1m 30s
Rate this question

Topics

Amazon Route 53 DNS Configuration and Routing Policies

More questions from this topic