Examkin

Question

Difficulty: MediumHigh-Performing Database Solutions

A media streaming platform stores user playback state and profile metadata. The application requires a database that can handle over 50,00050,000 writes per second of small (<2 KB< 2 \text{ KB}) items. The database must provide sub-millisecond read latency for active sessions. The platform is deployed in both the `us-east-1` and `eu-west-3` regions, and users in both regions must be able to read and write to their local region with minimal latency.

Which combination of database strategies should a solutions architect recommend to meet these performance requirements? (Select TWO.)

  1. Configure Amazon DynamoDB global tables with replicas in us-east-1 and eu-west-3.Answer
  2. Design the database table using a combination of UserID and SessionID as the partition key.Answer
  3. C
    Design the database table using the playback timestamp as the partition key to ensure sequential sorting.
  4. D
    Deploy an Amazon RDS for MySQL Multi-AZ database in us-east-1 and set up a cross-region read replica in eu-west-3 to process local writes.
  5. E
    Deploy a single-region Amazon DynamoDB table in us-east-1 and configure Amazon ElastiCache replication groups to synchronize writes to eu-west-3.

Answer

The correct strategies are to configure Amazon DynamoDB global tables with replicas in us-east-1 and eu-west-3, and to design the database table using a combination of UserID and SessionID as the partition key.
The correct approach uses Amazon DynamoDB global tables to handle multi-region, active-active low-latency reads and writes, combined with a high-cardinality partition key (UserID and SessionID) to distribute writes evenly across partitions and avoid hot partition bottlenecks.

Step-by-Step Solution

1
Analyze the active-active multi-region requirement.
Identify that the solution must allow local reads and writes in both US and European regions.
Amazon DynamoDB global tables are designed to support fully managed, active-active, multi-region deployments with low-latency local reads and writes.
2
Evaluate the partition key design for high write throughput.
Select a partition key with high cardinality to distribute data and requests uniformly.
Using a combined key like UserID and SessionID ensures uniform distribution, whereas a sequential key like a timestamp would create a hot partition and throttle write throughput.

Key Concept

Designing high-performing, multi-region database architectures using Amazon DynamoDB global tables and proper partition key design to prevent hot partitions.
Rate this question

Topics

High-Performing Database Solutions

More questions from this topic