Examkin

Soru

Zorluk: ZorAmazon Route 53 DNS Configuration and Routing Policies

An organization hosts a web application behind Application Load Balancers (ALBs) deployed in two AWS Regions: `us-west-2` and `eu-central-1`. A SysOps administrator must configure Amazon Route 53 to route traffic for the apex domain (`example.com`) to satisfy these requirements:

* All users located in Europe must be routed to the ALB in `eu-central-1` to comply with regional data privacy laws.
* Users outside of Europe must be routed to the ALB that provides the lowest network latency.
* The solution must support routing at the zone apex and minimize client-side DNS lookup overhead.

Which configuration should the SysOps administrator implement to meet these requirements?

  1. A
    Create an active-passive Failover routing policy for `example.com` with the primary record pointing to the `eu-central-1` ALB and the secondary record pointing to the `us-west-2` ALB. Associate a Geolocation-based health check with the primary record to trigger a failover when non-European users request access.
  2. B
    Create a Geolocation routing policy for `example.com`. Configure a rule for the Europe continent that points to the `eu-central-1` ALB using an Alias record. Configure the Default geolocation rule to point to `latency.example.com` using a CNAME record. In the same hosted zone, create Latency routing records for `latency.example.com` that point to the ALBs in both regions using Alias records.
  3. Create a Geolocation routing policy for `example.com`. Configure a rule for the Europe continent that points to the `eu-central-1` ALB using an Alias record. Configure the Default geolocation rule to point to `latency.example.com` using an Alias record. In the same hosted zone, create Latency routing records for `latency.example.com` that point to the ALBs in both regions using Alias records.Cevap
  4. D
    Create Latency routing records for `example.com` pointing to the ALBs in both regions. For the `eu-central-1` Latency record, apply a Geoproximity routing policy as a nested configuration to restrict European users, and use a CNAME record at the apex to fall back for other users.

Cevap

Create a Geolocation routing policy for `example.com` with a rule for Europe pointing to the `eu-central-1` ALB and a Default rule pointing to `latency.example.com` using an Alias record, and then create Latency records for `latency.example.com` pointing to both ALBs using Alias records.
The correct configuration utilizes a Geolocation routing policy for the apex domain (`example.com`). A rule matching Europe continent traffic points directly to the `eu-central-1` ALB using an Alias record. The Default geolocation rule points to a subdomain (`latency.example.com`) using a nested Alias record. Within `latency.example.com`, Latency-based routing records point to both regional ALBs using Alias records. Because Route 53 resolves Alias records internally in a single step, the client browser receives the final IP address directly without any additional DNS queries or round-trips. This configuration fully supports the zone apex and respects the compliance and performance constraints.

Adım Adım Çözüm

1
Identify the primary routing constraint based on location.
European users must always go to `eu-central-1`. This requires a Geolocation routing policy as the entry point at the zone apex (`example.com`).
To comply with regional data privacy laws, geography-based routing must take precedence over latency.
2
Design the routing mechanism for non-European users.
Create Latency-based routing records under a subdomain (e.g., `latency.example.com`) pointing to both ALBs.
Users outside of Europe must be routed dynamically based on the lowest network latency.
3
Connect the primary Geolocation policy to the Latency policy while meeting the zone apex and performance requirements.
Configure the Default geolocation rule at `example.com` as an Alias record pointing to `latency.example.com`.
Using an Alias record instead of a CNAME satisfies the DNS zone apex requirement and allows Route 53 to resolve the nested query internally, avoiding extra client-side round-trips.

Anahtar Kavram

Using nested Alias records in Amazon Route 53 allows the integration of different routing policies (such as Geolocation and Latency) while adhering to zone apex limitations and optimizing DNS resolution speed.
Bu soruyu puanla

Konular

Amazon Route 53 DNS Configuration and Routing Policies

Bu konudan daha fazla soru