Examkin

Question

Difficulty: HardRoute 53 Routing Policies and DNS Failover Strategies

An enterprise company hosts its customer portal under the domain name portal.finance.example.com. The primary infrastructure consists of an Application Load Balancer (ALB) and EC2 instances in the us-east-1 region. The company wants to set up an active-passive disaster recovery strategy. If the primary region goes offline or if the primary database loses connectivity, traffic must automatically redirect to an Amazon S3 bucket in the us-west-2 region hosting a static maintenance page. A custom health-check script on the EC2 instances monitors the database connection status. Which two configurations should the solutions architect implement to achieve this goal? (Select TWO.)

  1. Configure a Route 53 Failover record for portal.finance.example.com as an Alias record pointing to the us-east-1 ALB, set the routing category to Primary, enable Evaluate Target Health, and configure the ALB's target group health checks to monitor the custom health-check path.Answer
  2. Configure a Route 53 Failover record for portal.finance.example.com as an Alias record pointing to the Amazon S3 static website endpoint in us-west-2, set the routing category to Secondary, and configure the S3 bucket name to exactly match portal.finance.example.com.Answer
  3. C
    Configure a Route 53 Latency routing record for portal.finance.example.com pointing to the primary ALB, and set up a secondary CNAME record pointing to the S3 bucket to ensure lower latency failover.
  4. D
    Configure the primary Route 53 record to point directly to the database replica in the secondary region to handle active-passive failover and database read queries during normal operations.
  5. E
    Configure a Route 53 Weighted routing policy with a weight of 100 for the primary ALB and a weight of 0 for the secondary S3 bucket, without enabling Route 53 Health Checks, relying instead on CloudWatch alarms to dynamically update DNS records.

Answer

Configure a Route 53 Failover record for portal.finance.example.com as an Alias record pointing to the us-east-1 ALB (Primary with Evaluate Target Health enabled and target group health checks pointing to the custom path) and configure a Route 53 Failover record as an Alias record pointing to the Amazon S3 static website endpoint in us-west-2 (Secondary with matching bucket name).
To implement active-passive failover, the architect should define a Route 53 Failover policy. The primary record is configured as an Alias record pointing to the Application Load Balancer (ALB) with 'Evaluate Target Health' enabled. This links Route 53's health decision to the ALB's target health status. The ALB's target group executes health checks against the custom script verifying database connectivity. The secondary record is also configured as a Failover Alias record pointing to the Amazon S3 static website endpoint. For Route 53 to resolve an Alias record directly to an S3 bucket, the S3 bucket name must match the domain name exactly.

Step-by-Step Solution

1
Analyze the active-passive failover requirement and identify the correct Route 53 routing policy.
Determine that a Route 53 Failover routing policy is required, featuring a primary record for normal operations and a secondary record for the maintenance page.
Failover routing is the native Route 53 policy designed specifically for active-passive disaster recovery configurations.
2
Evaluate the health-checking requirement involving the primary application and the backend database.
Identify that enabling 'Evaluate Target Health' on the primary Route 53 Alias record will delegate health evaluation to the ALB. The ALB's target group must be configured to check the custom script path that verifies database connectivity.
If target instances fail the ALB's health check due to database loss, the ALB is marked unhealthy, causing Route 53 to failover to the secondary target.
3
Establish the secondary record pointing to the static maintenance site.
Configure a secondary Failover Alias record pointing to the Amazon S3 static website endpoint. Ensure the S3 bucket name matches the domain name exactly.
Route 53 requires the S3 bucket name to match the record name (portal.finance.example.com) for Alias record resolution to work correctly.

Key Concept

Amazon Route 53 DNS Failover and health check configuration for active-passive disaster recovery architectures.
Rate this question

Topics

Route 53 Routing Policies and DNS Failover Strategies

More questions from this topic