Examkin

Soru

Zorluk: OrtaHigh-Performing Database Solutions

A financial technology company is launching a global peer-to-peer payment application. The application requires a database backend that can handle two distinct workloads. First, it must record millions of transaction ledger entries per day in Amazon DynamoDB with low latency, avoiding partition write bottlenecks. Second, it must support a reporting database using Amazon RDS for PostgreSQL that requires high availability, automatic low-latency failover, and offloading read queries to optimize primary database performance. Which two database design configurations should the solutions architect select to meet these performance and high availability requirements? (Select two.)

  1. Design the Amazon DynamoDB table using a partition key with high cardinality, such as a combination of transaction UUID and user ID, to distribute write operations evenly across partitions.Cevap
  2. Configure Amazon RDS for PostgreSQL in a Multi-AZ deployment to provide automatic failover to a standby instance, and deploy RDS read replicas to offload read-heavy query traffic.Cevap
  3. C
    Design the Amazon DynamoDB table using the transaction date formatted as YYYY-MM-DD as the partition key to group daily transactions and maximize sequential write performance.
  4. D
    Configure Amazon RDS for PostgreSQL with read replicas in a different Availability Zone, and configure the application client to automatically promote a read replica to the primary role during an outage to minimize write downtime.

Cevap

The solutions architect should design the Amazon DynamoDB table using a partition key with high cardinality, such as a transaction UUID and user ID, to distribute writes evenly. Additionally, they should configure Amazon RDS for PostgreSQL in a Multi-AZ deployment and deploy read replicas to offload read traffic.
Designing the DynamoDB table with a high-cardinality partition key distributes write operations evenly across multiple partitions, preventing hot keys. Deploying Amazon RDS in a Multi-AZ configuration enables synchronous replication and automated, low-latency failover, while read replicas offload read operations from the primary instance.

Adım Adım Çözüm

1
Analyze the DynamoDB write performance requirement to identify potential bottlenecks.
Determine that choosing a partition key with high cardinality (transaction UUID + user ID) prevents write throttling by distributing traffic uniformly, whereas a sequential date key leads to a hot partition.
DynamoDB partitions data based on the partition key hash value; uneven distribution causes hot partitions and throttles throughput.
2
Analyze the Amazon RDS for PostgreSQL high availability and read-scaling requirements.
Select a Multi-AZ configuration to ensure synchronous replication and automatic failover, and deploy read replicas to handle read queries.
Multi-AZ is the primary mechanism for automatic failover in RDS, whereas read replicas are intended for scaling reads asynchronously and cannot serve as automated failover targets without manual configuration.

Anahtar Kavram

High-performance database architectures require designing high-cardinality partition keys for Amazon DynamoDB to avoid write throttling, and deploying Amazon RDS in a Multi-AZ configuration with read replicas to achieve automated failover and read scaling.
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

High-Performing Database Solutions

Bu konudan daha fazla soru