Soru

Zorluk: OrtaAzure Cosmos DB and NoSQL Solutions

You are an Azure Solutions Architect designing a data storage solution for a global media streaming platform. The platform must store real-time user playback progress and watch history. The workload has a read-to-write ratio of approximately 40:6040:60. The solution must be distributed across three regions (East US, West Europe, and East Asia) to achieve sub-10ms write latency at the 99th percentile and support an active-active setup. The platform requires a 99.999% availability SLA for both reads and writes. High availability and regional disaster resilience must be guaranteed for all data, including database backups.

Which two configuration options should you include in the architectural design to meet these requirements? (Select TWO)

  1. Enable multi-region writes for the Azure Cosmos DB account to support the active-active global configuration and satisfy the low latency and high availability SLA.Cevap
  2. Select a high-cardinality partition key, such as a combination of user ID and session ID, to distribute read and write operations evenly across logical partitions.Cevap
  3. C
    Set the partition key to the user's country region to align data storage with regional access patterns and simplify query routing.
  4. D
    Configure the Azure Cosmos DB backup storage redundancy as Locally Redundant Storage (LRS) to minimize operational costs while relying on manual failover scripts.
  5. E
    Secure user profile images in the associated Azure Blob Storage account by generating Shared Access Signature (SAS) tokens with a five-year expiration directly in the database without a stored access policy.

Cevap

Enable multi-region writes for the Azure Cosmos DB account and select a high-cardinality partition key, such as a combination of user ID and session ID.
The correct solution involves enabling multi-region writes for the Azure Cosmos DB account and selecting a high-cardinality partition key (user ID + session ID). Multi-region writes ensure write operations are committed locally in all designated regions, satisfying both the sub-10ms write latency and the 99.999% write availability SLA. A high-cardinality partition key guarantees that the write-heavy workload is evenly distributed across logical and physical partitions, avoiding resource hot spots.

Adım Adım Çözüm

1
Analyze global availability and latency requirements.
Identified that active-active multi-region writes are required to meet sub-10ms write latency and the 99.999% availability SLA.
Single-region write models incur cross-region network latency for writes originating in other regions, which exceeds the sub-10ms limit, and only offer 99.99% availability for writes.
2
Evaluate partitioning strategy for write-heavy workload.
Determined that a high-cardinality partition key like user ID and session ID is necessary to avoid physical partition throughput limits.
Cosmos DB distributes data based on partition keys. Low-cardinality keys like region create hot partitions that bottleneck writes and waste RU/s.
3
Evaluate backup redundancy and security configuration.
Ruled out Locally Redundant Storage (LRS) for backups and long-lived Shared Access Signatures without stored access policies.
LRS does not survive datacenter outages, and long-lived SAS tokens cannot be easily revoked if leaked, failing resiliency and security best practices.

Anahtar Kavram

Azure Cosmos DB Multi-Region Replication and Partitioning Design
Bu soruyu puanla