Examkin

Question

Difficulty: EasyAzure Cosmos DB and NoSQL Solutions

You are designing an Azure Cosmos DB solution for a global retail application that manages product inventory. The application requires global replication across three Azure regions to support low-latency reads and writes, and it must scale to handle a 10:9010:90 read-to-write ratio. The database must achieve a 99.999%99.999\% write availability SLA and prevent hot partitions.

Which configuration should you recommend?

  1. Configure multi-region writes and set the partition key to a high-cardinality field such as ItemId.Answer
  2. B
    Configure multi-region writes and set the partition key to a low-cardinality field such as ProductStatus.
  3. C
    Configure Locally Redundant Storage (LRS) for regional replication and set the partition key to a high-cardinality field such as ItemId.
  4. D
    Configure multi-region writes, set the partition key to ItemId, and authenticate clients using a Shared Access Signature (SAS) token configured with a three-year lifetime.

Answer

Configure multi-region writes and set the partition key to a high-cardinality field such as ItemId.
Configuring multi-region writes allows writes to be processed locally in multiple regions, which meets the 99.999%99.999\% availability SLA and ensures low latency. Using a high-cardinality key like ItemId ensures write workloads are evenly distributed across physical storage partitions.

Step-by-Step Solution

1
Analyze the availability and replication requirements.
The solution must support low-latency reads and writes across three regions with a 99.999%99.999\% write availability SLA, which requires configuring multi-region writes.
Single-region writes cannot meet the 99.999%99.999\% SLA or provide low-latency writes globally.
2
Evaluate the partition key strategy to prevent hot partitions under a 10:9010:90 read-to-write (write-heavy) workload.
The partition key must have high cardinality to distribute writes evenly across physical partitions.
Low-cardinality keys like ProductStatus will bundle writes into a few logical partitions, causing throttling.
3
Select the option that correctly combines these design decisions.
Configuring multi-region writes with a high-cardinality partition key like ItemId satisfies all constraints.
This configuration provides the necessary scale, availability, and throughput distribution.

Key Concept

Azure Cosmos DB partition key selection and multi-region replication configuration
Estimated Time:1m 0s
Rate this question

Topics

Azure Cosmos DB and NoSQL Solutions

More questions from this topic