Examkin

Soru

Zorluk: ZorRoute 53 DNS Failover

A company hosts a critical web application on Amazon EC2 instances behind an Application Load Balancer (ALB) in the eu-central-1 (Frankfurt) region. The company wants to implement an active-passive disaster recovery strategy using Amazon Route 53. If the application's response latency exceeds 5 seconds, traffic must fail over to a static maintenance page hosted on an Amazon S3 bucket configured for website hosting in the eu-west-1 (Ireland) region. The latency metric is monitored via a custom CloudWatch metric. Which two configuration steps must the SysOps Administrator perform to set up this Route 53 DNS failover configuration? (Select TWO.)

  1. Create the CloudWatch alarm for the latency metric in the us-east-1 (N. Virginia) Region, and associate the Route 53 health check with this alarm.Cevap
  2. B
    Create the CloudWatch alarm for the latency metric in the eu-central-1 Region, and link the Route 53 health check directly to this local alarm.
  3. Create a primary Route 53 Failover record pointing to the ALB with the custom health check associated, and a secondary Route 53 Failover record pointing to the S3 bucket website endpoint.Cevap
  4. D
    Configure the secondary Failover record to point to an Amazon RDS Read Replica endpoint in eu-west-1 to handle database write availability during a failover event.
  5. E
    Enable Detailed Monitoring on the Application Load Balancer to retrieve sub-minute metrics, allowing the Route 53 health check to query the load balancer latency directly without an associated alarm.

Cevap

Creating the CloudWatch alarm for the latency metric in the us-east-1 Region to link with the Route 53 health check, and creating a primary Route 53 Failover record pointing to the ALB alongside a secondary Route 53 Failover record pointing to the S3 website endpoint.
To set up Route 53 active-passive failover based on custom metrics like latency, the SysOps Administrator must use a CloudWatch alarm. Route 53 can only integrate with CloudWatch alarms residing in the us-east-1 region, meaning the alarm must be created there even if the metric data originates elsewhere. Additionally, the DNS configuration requires defining a primary Failover record associated with the health check and a secondary Failover record pointing to the passive destination (the S3 bucket website hosting endpoint).

Adım Adım Çözüm

1
Configure metric publishing to the us-east-1 region, or configure a cross-region CloudWatch alarm in us-east-1 that evaluates the custom metric data coming from the eu-central-1 region.
A CloudWatch alarm monitoring the response latency is created in the us-east-1 Region.
Amazon Route 53 health checks are global and only integrate with CloudWatch alarms created in the us-east-1 region.
2
Create a Route 53 health check that monitors the state of the newly created CloudWatch alarm in us-east-1.
A Route 53 health check is established that reports unhealthy status when the CloudWatch alarm transitions to the ALARM state.
This links the application-layer latency metric directly to the DNS failover logic.
3
Create a primary routing record (e.g., an Alias A record for the zone apex or a standard CNAME) pointing to the ALB in eu-central-1, configure it with the Failover routing policy, and associate it with the created Route 53 health check.
The primary record will route traffic to the ALB as long as the health check reports healthy.
Associating the health check ensures that Route 53 will detect latency spikes and stop resolving queries to the primary ALB.
4
Create a secondary routing record with the same name, configure it with the Failover routing policy, and point it to the S3 bucket website endpoint in eu-west-1.
The secondary record will serve traffic to the maintenance page when the primary endpoint is unhealthy.
Completes the active-passive failover configuration.

Anahtar Kavram

Amazon Route 53 DNS Active-Passive Failover with CloudWatch Alarms
Tahmini Süre:2m 30s
Bu soruyu puanla

Konular

Route 53 DNS Failover

Bu konudan daha fazla soru