Examkin

Question

Difficulty: MediumRoute 53 Routing Policies and DNS Failover Strategies

A company hosts a critical customer registration service at the apex domain example.com. The backend API is deployed using Regional Amazon API Gateway endpoints in us-east-1 (primary) and us-west-2 (secondary standby). The company needs to design an active-passive disaster recovery strategy that automatically routes all API traffic to us-west-2 if the us-east-1 regional endpoint becomes unavailable. The DNS records are managed in Amazon Route 53.

Which combination of actions will meet these requirements? (Select TWO.)

  1. Create an HTTPS-based Route 53 health check that monitors the health of the primary regional API Gateway endpoint, and associate this health check with the primary DNS record.Answer
  2. Configure a primary Failover Alias record for the apex domain pointing to the primary regional API Gateway custom domain name, and configure a secondary Failover Alias record pointing to the secondary regional API Gateway custom domain name, setting 'Evaluate Target Health' to 'No' on both.Answer
  3. C
    Configure primary and secondary Latency-based Alias records for the apex domain, enabling 'Evaluate Target Health' to allow Route 53 to automatically redirect traffic to the standby region during an outage.
  4. D
    Create a CNAME record at the apex domain pointing to the primary regional API Gateway, and configure Route 53 to automatically promote the standby database replica to primary during a failover event.
  5. E
    Configure a Route 53 health check to monitor a scaled-down Pilot Light environment in the standby region, enabling Route 53 to automatically start the standby Amazon EC2 instances and database engine when the primary region fails.

Answer

Configure an HTTPS-based Route 53 health check for the primary regional API Gateway endpoint and associate it with the primary DNS record, and create primary and secondary Failover Alias records pointing to the regional custom domain names with 'Evaluate Target Health' set to 'No'.
To configure active-passive failover for regional API Gateway endpoints at the apex domain, you must use Route 53 Failover Alias records. Because API Gateway regional custom domains do not support Route 53's automatic 'Evaluate Target Health' functionality, you must set 'Evaluate Target Health' to 'No' on both alias records. Additionally, you must create a custom HTTPS Route 53 health check that probes the primary regional API Gateway endpoint and associate this health check with the primary Failover Alias record.

Step-by-Step Solution

1
Create an HTTPS-based Route 53 health check to monitor the health of the primary API Gateway regional endpoint.
A DNS health check is created that regularly probes the status of the primary API Gateway endpoint.
API Gateway regional custom domain names do not support the automated 'Evaluate Target Health' feature, so an external health check is required to detect endpoint failure.
2
Configure primary and secondary Failover Alias records for the apex domain pointing to the regional API Gateway custom domains.
DNS queries to the apex domain will resolve to the primary endpoint under normal operation and fail over to the secondary standby endpoint if the health check fails.
Failover routing policies are required for active-passive DNS configurations, and setting 'Evaluate Target Health' to 'No' allows the custom health check to govern the failover state.

Key Concept

Configuring active-passive Route 53 DNS failover for regional API Gateway endpoints using custom health checks and Failover Alias records.
Rate this question

Topics

Route 53 Routing Policies and DNS Failover Strategies

More questions from this topic