A startup is deploying a new web application on AWS that handles customer order processing. The primary architecture is deployed in `us-east-1` and consists of an Application Load Balancer (ALB), an Auto Scaling group of Amazon EC2 instances, and an Amazon Aurora PostgreSQL database cluster. The startup needs to establish a disaster recovery (DR) strategy in `us-west-2` that achieves a Recovery Time Objective (RTO) of minutes and a Recovery Point Objective (RPO) of minute. The DR strategy must minimize ongoing infrastructure costs and operational complexity. Which combination of actions should a Solutions Architect implement to meet these requirements? (Select TWO.)
- Configure an Amazon Route 53 failover routing policy. Create a primary failover record pointing to the Application Load Balancer in `us-east-1` with an active Route 53 health check, and a secondary failover record pointing to the Application Load Balancer in `us-west-2`.Cevap
- Deploy an Amazon Aurora Global Database with the primary cluster in `us-east-1` and a secondary cluster in `us-west-2` containing zero DB instances. During a failover event, promote the secondary cluster to a standalone cluster and add an Aurora DB instance.Cevap
- CConfigure Amazon Route 53 with a latency-based routing policy to distribute traffic to both Regions. Set up an Amazon EventBridge rule in `us-east-1` to delete the DNS record pointing to `us-east-1` if the primary application health check fails.
- DConfigure cross-Region snapshot copies for the Aurora cluster to copy snapshots from `us-east-1` to `us-west-2` every minutes. During a failover event, restore the database cluster in `us-west-2` from the latest copied snapshot.
- EAssociate a Route 53 Private Hosted Zone created in the primary VPC with the VPC in `us-west-2`, and configure weighted routing records to direct public user traffic to the healthy endpoints.
Cevap
The correct options are to configure an Amazon Route 53 failover routing policy with active health checks to the load balancers, and to deploy an Amazon Aurora Global Database with a secondary cluster containing zero DB instances that can be scaled up and promoted during failover.
To achieve the -minute RPO and -minute RTO while keeping costs low, the architecture must utilize a high-performance replication mechanism and an automated DNS routing strategy. Deploying an Amazon Aurora Global Database with a secondary cluster that has no database instances provides sub-second replication lag (meeting the RPO) with zero active compute costs in the secondary region. During a failover, a DB instance can be added to the secondary cluster, and the cluster promoted to primary, which fits well within the -minute RTO. Additionally, configuring an Amazon Route 53 failover routing policy with health checks ensures that public traffic is automatically rerouted to the secondary Application Load Balancer once the primary endpoint is detected as unhealthy.
Adım Adım Çözüm
Anahtar Kavram
Designing Multi-Region Disaster Recovery using Aurora Global Database (Pilot Light model with zero DB instances) and Route 53 active-passive DNS failover.