Question

Difficulty: MediumDatabase and Storage Strategy

A healthcare software company is designing a new patient record archiving platform. The application stores high-resolution medical scan files as object storage and a metadata catalog as an OLTP database. The metadata database must support read operations across two AWS Regions with a disaster recovery target of near-zero RPO and an RTO of under 1 minute1 \text{ minute}. The system must automatically scale read capacity during peak query hours. Additionally, the scan files must be shared securely with an external auditor's AWS account, requiring encryption using keys that support cross-account policy delegation. Which database and storage strategy meets these requirements?

  1. A
    Deploy a single-region Amazon Aurora PostgreSQL database. Configure AWS Backup to take hourly database snapshots and replicate them to the secondary Region. In a disaster recovery event, use a Pilot Light strategy to restore the database in the secondary Region. Store the medical scan files in Amazon S3 buckets in both Regions, configured with S3 Cross-Region Replication (CRR).
  2. B
    Deploy Amazon RDS for PostgreSQL with Multi-AZ configured across two Regions. Configure the standby DB instance to serve read traffic and auto-scale dynamically during peak hours. Store the medical scan files in Amazon S3 buckets in both Regions, configured with S3 Cross-Region Replication (CRR) and encrypted using Customer Managed Keys (CMKs).
  3. Deploy an Amazon Aurora Global Database. Use Aurora Auto Scaling to dynamically adjust the number of Aurora Replicas in both Regions. Store the medical scan files in Amazon S3 buckets in both Regions, configured with S3 Cross-Region Replication (CRR) and encrypted using Customer Managed Keys (CMKs) with key policies that allow cross-account access.Answer
  4. D
    Deploy an Amazon Aurora Global Database. Use Aurora Auto Scaling to dynamically adjust the number of Aurora Replicas in both Regions. Store the medical scan files in Amazon S3 buckets in both Regions, configured with S3 Cross-Region Replication (CRR) and encrypted using the default AWS managed key (aws/s3), allowing the external auditor to access the files via S3 bucket policies.

Answer

Deploy an Amazon Aurora Global Database, using Aurora Auto Scaling to dynamically scale Aurora Replicas in both Regions. Store the medical scan files in Amazon S3 buckets in both Regions, configured with S3 Cross-Region Replication (CRR) and encrypted using Customer Managed Keys (CMKs) with key policies that allow cross-account access.
The correct option correctly pairs Amazon Aurora Global Database to achieve the required sub-minute RTO and near-zero RPO, utilizes Aurora Auto Scaling to scale read capacity dynamically via Aurora Replicas, and uses Customer Managed Keys (CMKs) to enable cross-account access delegation for the external auditor to decrypt S3 object data.

Step-by-Step Solution

1
Select the database engine that supports multi-region read capacity scaling and low-latency disaster recovery metrics (RTO < 1 minute, near-zero RPO).
Amazon Aurora Global Database provides sub-second replication latency across regions, satisfying the near-zero RPO and under 1 minute RTO requirements.
Traditional RDS snapshots or standard RDS Multi-AZ deployments do not support cross-region active reads or near-zero RPO with sub-minute failovers.
2
Configure read scaling mechanisms for the global database.
Apply Aurora Auto Scaling to dynamically adjust the number of Aurora Replicas in both regions based on CPU utilization or connection count.
This offloads read traffic from the primary instance and dynamically scales capacity during peak hours.
3
Select the encryption and cross-account access strategy for medical scan files in Amazon S3.
Encrypt the S3 buckets with Customer Managed Keys (CMKs) and configure key policies to allow cross-account KMS access for the external auditor.
AWS-managed KMS keys (like aws/s3) cannot be modified to delegate access to other AWS accounts, making customer-managed CMKs mandatory for cross-account sharing.

Key Concept

Selecting and configuring AWS database and storage services to meet specific RTO/RPO, scaling, and cross-account encryption requirements.
Estimated Time:2m 0s
Rate this question