A retail company operates a multi-tier application across two AWS accounts within an AWS Organization. The primary infrastructure is located in us-east-1 (Account 1), and a disaster recovery (DR) site is set up in us-west-2 (Account 2). The database layer is an Amazon Aurora PostgreSQL Global Database with the primary cluster in us-east-1 and a read-only secondary cluster in us-west-2. Internal service names and database endpoints are resolved using a Route 53 private hosted zone corp.internal managed in Account 1. The company has a Recovery Time Objective (RTO) of minutes and a Recovery Point Objective (RPO) of minute. During a DR drill, the failover fails because the secondary region's Application Load Balancer cannot resolve the database endpoints, and manual failover steps take too long. Which TWO actions should a Solutions Architect recommend to automate the failover and meet the RTO and RPO requirements?
- Associate the Route 53 private hosted zone corp.internal with the VPC in us-west-2 by authorizing the association from Account 1 and creating the association from Account 2.Cevap
- Use AWS Route 53 Application Recovery Controller (ARC) routing controls to redirect application traffic, and promote the secondary DB cluster in us-west-2 using the managed failover feature of Aurora Global Databases.Cevap
- CCreate a duplicate Route 53 private hosted zone named corp.internal in Account 2 and associate it with the us-west-2 VPC, creating local database DNS records pointing to the secondary cluster.
- DConfigure Route 53 failover routing records pointing directly to the private IP address of the primary DB instance, using a standard Route 53 health check that directly probes the database port to automate routing changes.
- ETransition the DR architecture to a pilot light model by deleting all database instances in the secondary Aurora cluster to reduce costs, and restore a new instance from a cross-region snapshot during failover.