A financial SaaS company is designing a new multi-region disaster recovery (DR) architecture for its customer portal. The application is deployed across us-east-1 (Primary) and us-west-2 (Secondary) behind Application Load Balancers. The database layer uses Amazon Aurora. The portal requires private DNS resolution for internal microservices across both VPCs via a Route 53 Private Hosted Zone (PHZ). The company needs to design a cost-effective DR strategy that meets a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 1 minute. Which of the following architectures meets these requirements while minimizing costs?
- AConfigure daily Amazon Aurora snapshot sharing and copy the snapshots from us-east-1 to us-west-2. Deploy redundant NAT Gateways across multiple Availability Zones in the VPCs of both Regions. Associate the Route 53 Private Hosted Zone with the VPCs in both us-east-1 and us-west-2. Create a Route 53 Failover routing record group pointing to the Application Load Balancer in each Region.
- BConfigure Amazon Aurora Global Database with the primary database cluster in us-east-1 and a warm standby cluster in us-west-2 containing a single Aurora Replica. Deploy a single NAT Gateway in a single Availability Zone within the VPC of each Region to minimize idle cost. Associate the Route 53 Private Hosted Zone with the VPCs in both us-east-1 and us-west-2. Create a Route 53 Failover routing record group pointing to the Application Load Balancer in each Region.
- Configure Amazon Aurora Global Database with the primary database cluster in us-east-1 and a warm standby cluster in us-west-2 containing a single Aurora Replica. Deploy redundant NAT Gateways across multiple Availability Zones in the VPCs of both Regions. Associate the Route 53 Private Hosted Zone with the VPCs in both us-east-1 and us-west-2. Create a Route 53 Failover routing record group pointing to the Application Load Balancer in each Region.Answer
- DConfigure Amazon Aurora Global Database with the primary database cluster in us-east-1 and a warm standby cluster in us-west-2 containing a single Aurora Replica. Deploy redundant NAT Gateways across multiple Availability Zones in the VPCs of both Regions. Associate the Route 53 Private Hosted Zone only with the VPC in us-east-1, relying on inter-region VPC peering for name resolution from us-west-2. Create a Route 53 Failover routing record group pointing to the Application Load Balancer in each Region.
Answer
The configuration that sets up Amazon Aurora Global Database with redundant NAT Gateways in both Regions, associates the Route 53 Private Hosted Zone with both VPCs, and configures Route 53 Failover routing.
The correct architecture uses Amazon Aurora Global Database to achieve near-zero replication lag, satisfying the 1-minute RPO. It deploys redundant NAT Gateways across multiple Availability Zones in each VPC to eliminate single points of failure for outbound traffic. It also associates the Private Hosted Zone with both VPCs, ensuring private DNS resolution remains operational across regions during a failover.
Step-by-Step Solution
Key Concept
Multi-region high availability and disaster recovery architecture integrating Aurora Global Database, Private Hosted Zone VPC associations, and NAT Gateway redundancy.