Soru

Zorluk: OrtaAmazon Route 53 DNS Configuration and Routing Policies

A SysOps Administrator is managing a web application that uses Amazon Route 53 for DNS resolution. The administrator configures Geolocation routing for `app.example.com` to route users in Europe to an Application Load Balancer (ALB) in `eu-west-1` and users in Asia to an ALB in `ap-southeast-1`. Shortly after deployment, users in North America report that they receive DNS resolution errors when trying to access the application. Which configuration change should the administrator implement to resolve the DNS resolution errors for North American users?

  1. A
    Modify the Application Load Balancer's target group health check settings to send health check requests to port 5353 of the target instances.
  2. B
    Create a CNAME record for the apex domain `example.com` that points directly to the DNS name of the default Application Load Balancer.
  3. Create a third geolocation routing record for `app.example.com` with the location set to 'Default' and point it to one of the active ALBs.Cevap
  4. D
    Change the routing policy for `app.example.com` to Failover routing, setting the European ALB as the primary endpoint and the Asian ALB as the secondary endpoint without configuring Route 53 health checks.

Cevap

Create a third geolocation routing record for the subdomain with the location set to 'Default' pointing to one of the active Application Load Balancers.
The correct answer is to create a third geolocation routing record with the location set to 'Default' and point it to an active ALB. In Amazon Route 53, if geolocation routing is configured but a query originates from a region not explicitly mapped in any of the records, Route 53 returns a 'no answer' response (NXDOMAIN). Configuring a default record handles queries from all locations that are not explicitly mapped.

Adım Adım Çözüm

1
Analyze the DNS routing configuration and the failure scenario.
Identify that the current Geolocation routing policy only covers Europe and Asia, leaving other regions (like North America) without a matching route rule.
When Route 53 receives a DNS query from a location that does not match any existing geolocation record, it will return a DNS resolution error if no default fallback is configured.
2
Determine the appropriate Route 53 configuration to handle unmapped locations.
A geolocation record with the location set to 'Default' must be added to route unmatched queries.
The 'Default' location record matches all queries from locations that are not explicitly covered by another geolocation record in the set.
3
Map the 'Default' record to an active application endpoint.
Create the record pointing to one of the existing Application Load Balancers to serve traffic for users in North America and other unmapped regions.
This ensures high availability and continuous DNS resolution globally.

Anahtar Kavram

Route 53 Geolocation Routing Default Fallback Configuration
Tahmini Süre:1m 30s
Bu soruyu puanla