Examkin

Soru

Zorluk: OrtaHigh-Performing Database Solutions

A solutions architect is designing the database backend for a new multiplayer online game. The matchmaking system requires sub-millisecond read latency for fetching player state and matching profiles, and it must support a write throughput of 1500015{}000 writes per second during peak hours. Player profiles are updated frequently with new match statistics. The database must also support automatic failover across Multiple Availability Zones (Multi-AZ) with minimal downtime. Which database architecture should the solutions architect recommend to meet these requirements?

  1. Configure an Amazon DynamoDB table with DynamoDB Accelerator (DAX) for caching, utilizing a composite primary key consisting of a hashed player ID as the partition key and a game session ID as the sort key.Cevap
  2. B
    Configure an Amazon DynamoDB table with DynamoDB Accelerator (DAX) using a partition key based on the player registration timestamp formatted as YYYY-MM-DD-HH.
  3. C
    Configure an Amazon RDS for PostgreSQL database with a read replica in a second Availability Zone to serve as the primary automatic failover target, paired with Amazon ElastiCache for Redis.
  4. D
    Configure an Amazon DynamoDB table with DynamoDB Accelerator (DAX) using Provisioned Capacity Mode set to a fixed 1500015{}000 Write Capacity Units (WCUs).

Cevap

Configure an Amazon DynamoDB table with DynamoDB Accelerator (DAX) for caching, utilizing a composite primary key consisting of a hashed player ID as the partition key and a game session ID as the sort key.
The configuration utilizing Amazon DynamoDB with DynamoDB Accelerator (DAX) and a composite key based on a hashed player ID is correct. DynamoDB natively replicates data across multiple Availability Zones, and DAX delivers sub-millisecond read latency for player profile lookups. A hashed partition key provides high cardinality, distributing the write load of 1500015{}000 writes per second evenly across partitions.

Adım Adım Çözüm

1
Analyze the read latency and write throughput requirements.
Reads require sub-millisecond latency (pointing to caching like DAX or ElastiCache), and writes require high throughput (1500015{}000 writes per second).
To narrow down the database service and caching layers that can handle the target metrics.
2
Evaluate partition key design for the high write volume.
A partition key must distribute write traffic evenly across physical DynamoDB partitions to avoid hot keys.
Monotonically increasing keys like timestamps create write hotspots, whereas hashed identifiers ensure horizontal scalability.
3
Assess high availability and automatic failover requirements.
DynamoDB inherently provides Multi-AZ replication and automatic failover, whereas RDS requires a Multi-AZ deployment rather than relying on read replicas for disaster recovery.
To ensure the architecture is resilient and meets SAA best practices for high availability.

Anahtar Kavram

Selecting and configuring high-performance database architectures with appropriate caching and partition key strategies to avoid bottlenecks.
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

High-Performing Database Solutions

Bu konudan daha fazla soru