Azure Cosmos DB – Consistency, Partitioning and SDK · AZ-204: Developing Solutions for Microsoft Azure Develop for Azure Storage
An Azure Cosmos DB container stores orders for 10,000 retail stores. Most queries retrieve orders for a specific store, and writes are distributed re…
Practice question from Azure Cosmos DB – Consistency, Partitioning and SDK (AZ-204: Developing Solutions for Microsoft Azure Develop for Azure Storage), with the correct answer and a step-by-step solution.
medium · MCQ · Q-67E383
An Azure Cosmos DB container stores orders for 10,000 retail stores. Most queries retrieve orders for a specific store, and writes are distributed relatively evenly across stores. Which partition key is the best choice for the container?
- A./orderStatus
- B./orderDate
- C./storeIdCorrect answer
- D./customerType
Solution
The partition key should support the dominant query pattern and distribute data and request load across many logical partitions. /storeId matches the store-scoped queries and has high enough cardinality to distribute the workload. Status, date, and customer type are more likely to create less useful or uneven partitioning.
More from Azure Cosmos DB – Consistency, Partitioning and SDK
- An application uses Azure Cosmos DB to update a user's profile and then immediately read the profile during the same user session. The read…
- A Cosmos DB container stores telemetry for many tenants. Its current partition key is /tenantId, but one tenant produces most of the teleme…
- A .NET application uses the Azure Cosmos DB SDK v3. The container's partition key path is /customerId, and the application must retrieve th…
- A globally distributed Azure Cosmos DB account must allow reads from any region, but each read may lag behind the latest write by no more t…
Practise more Develop for Azure Storage
Sign up free for adaptive practice on this chapter, with instant feedback and hints on every question.
Start practising freeFree to start · No credit card needed