An international logistics company uses a critical PostgreSQL-compatible transactional database on AWS. The application demands high availability within its primary AWS Region () with a Recovery Time Objective (RTO) of less than and a Recovery Point Objective (RPO) of (no data loss) in the event of an Availability Zone outage. Additionally, the company requires a cross-region disaster recovery (DR) architecture in that supports an RPO of less than and an RTO of less than . Which combination of database configurations will satisfy these requirements? (Select TWO.)
- Deploy an Amazon Aurora PostgreSQL DB cluster with the primary writer instance in one Availability Zone and a reader instance in a different Availability Zone within the primary Region.Answer
- Create an Amazon Aurora Global Database and add a secondary DB cluster in the disaster recovery Region.Answer
- CDeploy a single-node Amazon RDS for PostgreSQL instance with a cross-region read replica in the secondary Region and use AWS Lambda to manage failover.
- DUse AWS Backup to take hourly database snapshots, replicate them to the secondary Region, and deploy automated restore scripts.
- EConfigure Route 53 with latency-based routing to distribute database write traffic across active-active database instances in both Regions.
Answer
Deploying an Amazon Aurora PostgreSQL DB cluster with writer and reader instances across different Availability Zones in the primary Region, and creating an Amazon Aurora Global Database with a secondary DB cluster in the disaster recovery Region.
The correct architecture combines an Amazon Aurora PostgreSQL DB cluster deployed across multiple Availability Zones in the primary Region (to achieve an RTO of less than 60 seconds and an RPO of 0 through automatic failover to a reader instance) with an Amazon Aurora Global Database secondary cluster (to achieve an RPO of less than 5 seconds and an RTO of less than 15 minutes through physical storage-level replication and managed failover).
Step-by-Step Solution
Key Concept
High availability is achieved locally using Multi-AZ deployments with synchronous replication (or shared storage architectures), whereas cross-region disaster recovery with low RPO/RTO requires low-latency asynchronous physical replication such as Amazon Aurora Global Databases.