Examkin

Question

Difficulty: HardEnhancing Reliability and Disaster Recovery

An enterprise operates a critical online transaction processing (OLTP) application on AWS. The application is deployed in a primary AWS account in the `us-east-1` Region. The architecture consists of Amazon EC2 instances in an Auto Scaling group behind an internal Application Load Balancer (ALB) and an Amazon Aurora MySQL Global Database with the primary cluster in `us-east-1` and a secondary cluster in `us-west-2`. The enterprise's AWS Organization includes a centralized Network Account that manages a Route 53 Private Hosted Zone (PHZ) for the application's internal domain name. A separate Shared Services Account hosts supporting microservices in a separate VPC that must access the OLTP application via its internal domain name.

The Solutions Architect must enhance the reliability and disaster recovery (DR) of the existing architecture to meet a recovery time objective (RTO) of less than 15 minutes and a recovery point objective (RPO) of less than 1 minute. The design must support manual failover to `us-west-2` without causing a split-brain scenario or routing traffic to unhealthy endpoints.

Which of the following actions should the Solutions Architect take to meet these requirements? (Select TWO.)

  1. Configure Amazon Route 53 Application Recovery Controller (ARC) routing controls and safety rules for the application endpoints. During a failover event, use ARC to redirect traffic to the secondary Region and initiate an unplanned failover on the Amazon Aurora Global Database to promote the cluster in `us-west-2`.Answer
  2. Create a VPC association authorization in the Network Account to authorize the association of the Private Hosted Zone (PHZ) with the Shared Services Account VPC. In the Shared Services Account, associate the VPC with the PHZ to enable correct resolution of the internal application endpoints.Answer
  3. C
    Configure Route 53 active-passive failover routing policies pointing to the internal Application Load Balancers. Attach standard Route 53 health checks directly to the internal ALBs, and configure the health checks to automatically trigger a failover of the Amazon Aurora Global Database primary cluster when the primary ALB becomes unhealthy.
  4. D
    Implement a pilot light disaster recovery strategy in `us-west-2` by keeping the secondary Aurora DB cluster in a stopped state, and use AWS CloudFormation to dynamically deploy the Application Load Balancers and Auto Scaling groups only when a regional failover is initiated.
  5. E
    Share the Route 53 Private Hosted Zone from the Network Account to the Shared Services Account using AWS Resource Access Manager (RAM) to automatically associate the hosted zone with the Shared Services VPC, bypassing the manual cross-account authorization flow.

Answer

Configure Amazon Route 53 Application Recovery Controller (ARC) routing controls and safety rules to manage failover traffic, promote the secondary Aurora cluster via an unplanned failover, and authorize/associate the cross-account Route 53 Private Hosted Zone with the Shared Services VPC.
The solution requires configuring Route 53 Application Recovery Controller (ARC) to safely shift client traffic to the secondary Region and executing an unplanned failover of the Aurora Global Database to promote the secondary cluster. It also requires establishing cross-account private DNS resolution by creating a VPC association authorization in the Network Account and associating the Shared Services VPC with the Private Hosted Zone.

Step-by-Step Solution

1
Configure DNS traffic shifting using Amazon Route 53 Application Recovery Controller (ARC) and initiate unplanned failover for the database.
The application traffic can be manually redirected to the recovery region in under a minute, and the secondary Aurora DB cluster is promoted to primary with data replication intact.
Using ARC routing controls allows precise, rapid traffic shifting. Promoting the Aurora Global Database secondary cluster via unplanned failover meets the strict RTO of under 15 minutes and RPO of under 1 minute.
2
Generate a VPC hosted zone association authorization from the Network Account for the VPC in the Shared Services Account.
The Shared Services Account VPC is authorized to associate with the Private Hosted Zone (PHZ) hosted in the Network Account.
Route 53 Private Hosted Zones are private by default and cannot be resolved by VPCs in other accounts without explicit cross-account authorization.
3
Associate the Shared Services VPC with the Private Hosted Zone from the Shared Services Account.
VPC resources in the Shared Services Account can now resolve the application's internal endpoints to the local internal ALBs in both regions.
Completing the association link ensures that DNS queries for the OLTP application are routed correctly to the active regional ALBs.

Key Concept

Multi-region and multi-account disaster recovery routing requires coordinating database promotion, traffic failover mechanisms, and cross-account Private Hosted Zone association.
Estimated Time:3m 0s
Rate this question

Topics

Enhancing Reliability and Disaster Recovery