Question

Difficulty: HardDatabase and Storage Strategy

A global digital publishing platform is designing a new high-throughput content management system (NoSQL and Object storage workloads). The system consists of:

1. A metadata database storing article configurations and user session states, which requires multi-region active-active writes and database write and read latencies under 10 ms10\text{ ms}.
2. An asset repository storing millions of media files, which must be stored in Amazon S3 and replicated from the primary region (uswest2us-west-2) to a secondary disaster recovery region (useast1us-east-1) with a strict recovery point objective (RPO) of 15 minutes15\text{ minutes}.

All data must be encrypted at rest using Customer Managed Keys (CMKs). Cross-account access to the asset repository is required for a security audit application running in a dedicated audit account.

Which combination of database and storage configurations will meet these requirements? (Select TWO.)

  1. Configure Amazon DynamoDB global tables with replicas in us-west-2 and us-east-1. Encrypt the tables using regional Customer Managed Keys (CMKs) in each region.Answer
  2. Configure Amazon S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled. Encrypt the source and destination S3 buckets using Customer Managed Keys (CMKs), and update the KMS key policies and bucket policies to grant read access to the audit account's IAM role.Answer
  3. C
    Configure Amazon S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) enabled. Encrypt the S3 buckets using AWS managed keys (aws/s3), and configure the bucket policies to grant read access to the audit account's IAM role.
  4. D
    Configure Amazon S3 Cross-Region Replication (CRR) without S3 Replication Time Control (S3 RTC) to replicate assets between regions, relying on standard replication to meet the 15-minute RPO at a lower cost.
  5. E
    Deploy an Amazon Aurora Global Database with the primary cluster in us-west-2 and a secondary cluster in us-east-1. Enable write forwarding on the secondary cluster to allow active-active writes in both regions with sub-10 millisecond write latency.

Answer

Configure Amazon DynamoDB global tables with replicas in us-west-2 and us-east-1, encrypting them with regional Customer Managed Keys, and configure Amazon S3 Cross-Region Replication with S3 Replication Time Control enabled, encrypting the buckets with Customer Managed Keys and granting the audit account permission via the KMS key policy and S3 bucket policy.
The correct options are configuring Amazon DynamoDB global tables with regional Customer Managed Keys (CMKs) and configuring Amazon S3 Cross-Region Replication with S3 Replication Time Control (S3 RTC) enabled using Customer Managed Keys (CMKs). DynamoDB global tables enable active-active replication with local sub-10ms latency. S3 RTC guarantees the 15-minute RPO. Customer Managed Keys are required for both systems to support custom key policies that delegate cross-account decryption access to the external audit account's role.

Step-by-Step Solution

1
Analyze database requirements: active-active multi-region writes and sub-10ms read/write latency.
Amazon DynamoDB global tables provide local sub-10ms read/write operations with multi-region active-active capabilities, whereas Amazon Aurora write forwarding redirects writes to a single region, causing cross-region network latency.
To ensure database latency meets the sub-10ms threshold in both regions, writes must occur locally and replicate asynchronously.
2
Analyze S3 replication requirements: strict 15-minute RPO.
Amazon S3 Replication Time Control (S3 RTC) provides a SLA-backed replication guarantee of 15 minutes, whereas standard S3 Cross-Region Replication does not guarantee delivery times.
Meeting a strict 15-minute RPO requires S3 RTC configuration.
3
Analyze encryption and cross-account access requirements: Customer Managed Keys (CMKs) and access for an audit account.
AWS managed KMS keys (such as aws/s3) cannot have their policies modified, preventing cross-account access delegation. Customer Managed Keys are required so that the key policies can be updated to permit the external audit account to decrypt the data.
Cross-account resource sharing with KMS encryption requires CMKs and explicit cross-account key policy configurations.

Key Concept

Selecting the optimal database and storage architecture to meet strict multi-region latency, RPO, and cross-account encryption requirements.
Estimated Time:3m 0s
Rate this question