An organization is designing an Azure Cosmos DB container to store employee profile documents. The system must support high-volume write operations and maintain efficient query performance.
Which two statements describe correct characteristics of Azure Cosmos DB partitioning that must be considered?
- Selecting a property with high cardinality, such as employee ID, distributes throughput and storage consumption evenly across physical partitions.Answer
- BSelecting a property with low cardinality, such as department, is recommended to minimize the creation of physical partitions.
- The partition key is defined when the container is created and cannot be updated for that container afterward.Answer
- DThe partition key value of an existing document can be modified directly in place, which automatically migrates the document to the corresponding physical partition.
Answer
Selecting a property with high cardinality distributes throughput and storage evenly, and the partition key cannot be updated for a container after creation.
Selecting a property with high cardinality, such as employee ID, allows Cosmos DB to scale horizontally by distributing the write and read workloads across many partitions. Additionally, the partition key of a container is immutable once created, which is a critical design constraint that requires careful initial planning.
Step-by-Step Solution
Key Concept
Azure Cosmos DB partitioning strategies, partition key immutability, and cardinality considerations.
Estimated Time:1m 0s