A solutions architect is designing the database strategy for a new critical online transaction processing (OLTP) application. The application will be deployed in a primary AWS Region and requires a dynamic read-scaling database tier to handle unpredictable query loads. The business demands a disaster recovery (DR) solution in a secondary AWS Region with a Recovery Time Objective (RTO) of less than 15 minutes and a Recovery Point Objective (RPO) of less than 2 minutes. Furthermore, database backups must be encrypted and securely shared with a centralized security AWS account. Which database and encryption strategy will meet these requirements while minimizing operational overhead?
- Deploy an Amazon Aurora PostgreSQL Global Database. Configure Aurora Auto Scaling for the Aurora Replicas in the primary Region to handle read traffic. Promote the secondary Region in the event of a disaster. Encrypt the database cluster using a Customer Managed Key (CMK) in AWS KMS to allow cross-account sharing of backups with the security account.Answer
- BDeploy an Amazon RDS for PostgreSQL database with a Multi-AZ deployment. Direct read traffic to the standby replica and configure auto-scaling on the standby instance. Set up a cross-region read replica in the secondary Region. Encrypt the database using a Customer Managed Key (CMK) in AWS KMS.
- CDeploy an Amazon Aurora PostgreSQL database cluster in the primary Region. Configure Aurora Auto Scaling for Aurora Replicas. Use AWS Backup to copy daily snapshots to the secondary Region, and deploy a new cluster from the snapshot during a disaster. Encrypt the database using a Customer Managed Key (CMK) in AWS KMS.
- DDeploy an Amazon Aurora PostgreSQL Global Database. Configure Aurora Auto Scaling for the Aurora Replicas in the primary Region. Promote the secondary Region in the event of a disaster. Encrypt the database cluster using the default AWS-managed KMS key (aws/rds) and share the backups with the security account.
Answer
Deploy an Amazon Aurora PostgreSQL Global Database. Configure Aurora Auto Scaling for the Aurora Replicas in the primary Region to handle read traffic. Promote the secondary Region in the event of a disaster. Encrypt the database cluster using a Customer Managed Key (CMK) in AWS KMS to allow cross-account sharing of backups with the security account.
The correct option addresses all database scaling, DR, and encryption requirements. Amazon Aurora Global Database uses dedicated storage replication that offers a typical RPO of less than 1 second and RTO of under 1 minute. Aurora Auto Scaling dynamic scaling works with Aurora Replicas to handle variable read workloads. A Customer Managed Key (CMK) is required because the KMS key policy must be updated to grant permissions to the external centralized security account, which is impossible with the default AWS-managed KMS key.
Step-by-Step Solution
Key Concept
Selecting the optimal database engine and replication strategy for strict RTO/RPO targets while ensuring cross-account KMS access control.
Estimated Time:2m 0s