Examkin

Question

Difficulty: Medium

A logistics company is designing a new international package tracking application. The application requires a relational database to store shipping transit logs (OLTP workload). The system must meet a recovery point objective (RPO) of under 5 seconds and a recovery time objective (RTO) of under 2 minutes in the event of a regional outage. Additionally, the database must support low-latency local read access and horizontal read scaling for users in both the primary and secondary AWS regions. Which database and storage strategy meets these requirements?

  1. A
    Deploy Amazon RDS for PostgreSQL with Multi-AZ enabled in the primary region and a cross-region read replica in the secondary region. Route local read traffic in the primary region to the Multi-AZ standby database instance to scale read performance during peak tracking hours.
  2. Deploy an Amazon Aurora Global Database. Use a customer managed KMS key in the primary region and a corresponding customer managed KMS key in the secondary region for encryption. Configure Aurora Auto Scaling for readers in both the primary and secondary regions to handle read traffic spikes.Answer
  3. C
    Deploy an Amazon Aurora Global Database. Encrypt the primary cluster using the default AWS-managed KMS key (aws/rds), and modify the default key policy to grant the secondary region's replication infrastructure access to decrypt the data.
  4. D
    Deploy a single-region Amazon Aurora PostgreSQL database. Configure AWS Backup to take continuous backups and copy them to the secondary region. In the event of a regional outage, restore the database from the copied backup in the secondary region.

Answer

Deploy an Amazon Aurora Global Database with customer managed KMS keys in both regions and configure Aurora Auto Scaling for readers in both the primary and secondary regions.
Deploying an Amazon Aurora Global Database with customer managed KMS keys and reader auto scaling satisfies all requirements. Aurora Global Database has sub-second replication latency (meeting RPO) and can be promoted to a primary cluster in under a minute (meeting RTO). Reader auto scaling handles peak loads in both regions, and customer managed KMS keys allow the required cross-region decryption configurations.

Step-by-Step Solution

1
Evaluate the RTO/RPO requirements.
An RPO under 5 seconds and RTO under 2 minutes require continuous, low-latency cross-region replication and rapid promotion of the secondary cluster, which are features of Amazon Aurora Global Database.
This rules out backup-and-restore strategies that take hours.
2
Determine the scale-out reader requirements.
Using Aurora Auto Scaling on readers in both regions allows local read performance scaling during traffic surges.
Amazon RDS Multi-AZ standby instances cannot serve traffic and do not solve read performance spikes.
3
Analyze cross-region database encryption constraints.
Customer managed KMS keys must be used because AWS-managed KMS keys do not support policy modifications required for cross-region encryption key sharing.
Ensures the replication infrastructure has the necessary permissions to decrypt data in the secondary region.

Key Concept

Multi-region database design balancing replication lag, read scaling, and KMS encryption compatibility.
Rate this question