Question 10
UnclassifiedA team wants to put unrelated entities with different scale and access patterns into one container. What should they consider?
Correct answer: C
Explanation
A single container shares partitioning, throughput, and indexing settings across all items, so unrelated entities with different scale or access patterns may compete for the same resources. The team should check whether "shared partitioning, throughput, and indexing behavior" fits every entity before combining them.
Why each option is right or wrong
A. Whether a single container always improves every design.
B. Whether entity names are alphabetically close.
C. Whether shared partitioning, throughput, and indexing behavior fits all entities.
In Azure Cosmos DB, a container is the scope for a single partition key strategy, provisioned throughput, and indexing policy, so all item types inside it are governed by the same settings under the container-level resource model. Because throughput is allocated at the container level and indexing is applied according to one policy for the whole container, unrelated entities with different read/write patterns can contend for RU/s and suffer mismatched indexing costs or query performance.
D. Whether monitoring can be turned off.