A financial technology company is migrating its core transaction ledger application to AWS. The application runs on Amazon EC2 instances behind an Application Load Balancer and uses an Amazon RDS for PostgreSQL database. To comply with regulatory standards, the company requires a multi-Region disaster recovery (DR) strategy with a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 2 minutes. The design must minimize the ongoing infrastructure cost in the recovery Region. Which combination of actions should a solutions architect recommend to meet these requirements? (Select TWO.)
- Migrate the database to Amazon Aurora PostgreSQL Global Database, placing the primary cluster in the active Region and a secondary cluster in the recovery Region.Cevap
- Deploy the application tier in the recovery Region using an Auto Scaling group with the desired capacity set to zero, and configure Amazon Route 53 active-passive failover routing with health checks.Cevap
- CConfigure the database with an Amazon RDS for PostgreSQL cross-Region Read Replica in the recovery Region, and configure the replica to serve as the automatic failover target for the primary database.
- DConfigure an Amazon Route 53 latency-based routing policy to automatically redirect user traffic to the recovery Region if the active Region becomes unavailable.
- EImplement a Warm Standby strategy by running duplicate EC2 instances at full capacity in the recovery Region, while using daily database snapshots copied to Amazon S3 Glacier Flexible Retrieval to restore data.
Cevap
The solutions architect should migrate the database to Amazon Aurora PostgreSQL Global Database and deploy the application tier using an Auto Scaling group with desired capacity set to zero combined with Amazon Route 53 active-passive failover routing.
The correct combination requires migrating the database to Amazon Aurora PostgreSQL Global Database and deploying the application tier using an Auto Scaling group with zero running EC2 instances combined with Route 53 failover routing. Aurora Global Database has a replication lag of less than a second, meeting the 2-minute RPO, and can be promoted in under a minute, meeting the 15-minute RTO. Scaling the EC2 instances to zero minimizes compute costs in the recovery Region during normal operations, representing a Pilot Light strategy. Route 53 active-passive failover routing ensures that traffic is redirected to the recovery Region once the health checks report that the primary Region is unavailable.
Adım Adım Çözüm
Anahtar Kavram
Designing Multi-Region Architectures for Disaster Recovery under strict RTO/RPO and cost constraints.
Tahmini Süre:3m 0s