Question

Difficulty: MediumDatabase and Storage Strategy

A gaming company is designing a new multiplayer game. The backend requires a database for a NoSQL workload to store real-time player session states with sub-millisecond latency. It also requires an Object storage solution to store historical game telemetry logs for analytical processing, which must be replicated to a centralized security logging account in a secondary AWS Region. The key performance indicators (KPIs) include write latency under 10 ms10\text{ ms} for player state updates, 99.99%99.99\% availability, and a disaster recovery requirement of Recovery Time Objective (RTO) under 15 minutes15\text{ minutes} and Recovery Point Objective (RPO) under 5 minutes5\text{ minutes}. Encryption at rest is required for all data. Which two options should the solutions architect choose to meet these requirements?

  1. Deploy Amazon DynamoDB with global tables enabled across two AWS Regions to store player session states, using on-demand capacity mode.Answer
  2. Configure Amazon S3 Cross-Region Replication (CRR) to copy telemetry logs to the centralized security account's S3 bucket, using a customer managed KMS key in the source region and authorizing replication in the destination key policy.Answer
  3. C
    Deploy an Amazon RDS for MySQL Multi-AZ DB instance to store player session states, and route read traffic to the standby instance during high-concurrency events to satisfy latency requirements.
  4. D
    Configure Amazon S3 Cross-Region Replication (CRR) using the default AWS-managed S3 KMS key (aws/s3) to encrypt the replicated logs in the destination centralized account.
  5. E
    Deploy Amazon DynamoDB in the primary region to store player session states, and configure an AWS Lambda function to trigger on a daily schedule to back up the data and copy it to the secondary region.

Answer

Deploy Amazon DynamoDB with global tables enabled across two AWS Regions to store player session states, and configure Amazon S3 Cross-Region Replication (CRR) to copy telemetry logs to the centralized security account's S3 bucket, using a customer managed KMS key.
Deploying Amazon DynamoDB global tables provides multi-region active-active deployment, satisfying the RTO and RPO limits and providing sub-millisecond latencies. Replicating S3 telemetry logs to a centralized account across regions requires using a customer managed KMS key, as the default key policy of AWS-managed KMS keys cannot be modified to authorize cross-account actions.

Step-by-Step Solution

1
Evaluate the database requirements for the player session NoSQL workload.
Amazon DynamoDB with global tables is selected because it offers active-active multi-region replication, sub-millisecond latency, and satisfies the RTO under 15 minutes15\text{ minutes} and RPO under 5 minutes5\text{ minutes} constraints.
Relational options like standard RDS Multi-AZ cannot serve read traffic from standby nodes, and manual backup replication models fail the RPO targets.
2
Evaluate the object storage replication and encryption requirements for telemetry logs.
Amazon S3 Cross-Region Replication (CRR) configured with a customer managed KMS key is selected.
Cross-account replication with KMS encryption requires a customer managed key because the default AWS-managed KMS key policy cannot be modified to grant cross-account access.

Key Concept

Designing highly available, low-latency cross-region architectures using Amazon DynamoDB global tables and secure cross-account Amazon S3 replication using customer managed KMS keys.
Estimated Time:3m 0s
Rate this question