The answer is stable key values that do not change, even distribution of request volume across partitions, and high cardinality. These three factors are correct because Azure Cosmos DB uses the shard key to map each document to a specific physical partition; a stable key ensures the document stays in its assigned partition for life, avoiding costly cross-partition queries, while even distribution of request volume prevents hot partitions from throttling throughput, and high cardinality guarantees that the logical partitions are numerous enough to spread writes and reads evenly across the physical infrastructure. On the Microsoft Azure Data Engineer Associate DP-203 exam, this concept tests your understanding of partition-level performance and throughput management, often appearing in scenario-based questions where a poorly chosen key leads to uneven load or query inefficiency. A common trap is selecting a key with low cardinality, like a boolean or a date truncated to month, which creates hot partitions. Remember the mnemonic “SHE” for Stable, High cardinality, and Even distribution to lock in the correct choices.
DP-203 Design and implement data storage Practice Question
This DP-203 practice question tests your understanding of design and implement data storage. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which THREE factors should you consider when choosing a shard key for Azure Cosmos DB to ensure even distribution and optimal performance?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Stable key values that do not change
Stable key values that do not change (Option A) are correct because Azure Cosmos DB uses the shard key to determine the physical partition for each document. If the key value changes after insertion, the document cannot be moved to a different partition, leading to cross-partition queries and degraded performance. A stable key ensures that the partition assignment remains consistent throughout the document's lifetime, which is essential for optimal query routing and throughput management.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Stable key values that do not change
Why this is correct
Stable keys avoid partition splits and data movement.
Related concept
Read the scenario before looking for a memorised answer.
✗
Frequent updates to the key value
Why it's wrong here
Updates to shard key can cause performance overhead and partition splits.
✓
High cardinality of the key
Why this is correct
High cardinality ensures many distinct values for even distribution.
Related concept
Read the scenario before looking for a memorised answer.
✗
Low cardinality of the key
Why it's wrong here
Low cardinality leads to uneven distribution and hot partitions.
✓
Even distribution of request volume across partitions
Why this is correct
Prevents hot partitions and throttling.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse 'low cardinality' with 'high cardinality' or assume that frequently updated keys are acceptable because they think Cosmos DB can repartition dynamically, but in reality, the shard key is immutable after document creation.
Detailed technical explanation
How to think about this question
Under the hood, Cosmos DB uses a hash-based partitioning scheme where the shard key value is hashed to determine the physical partition (a logical partition within a physical partition). High cardinality ensures that the hash space is well-utilized, avoiding scenarios where a single logical partition exceeds the 20 GB storage limit or the 10,000 RU/s throughput cap per partition. In a real-world IoT scenario, using a device ID (high cardinality) as the shard key distributes writes evenly, whereas using a region code (low cardinality) would concentrate all writes from a popular region into one partition, causing throttling.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-203 question in full detail.
Design and implement data storage — This question tests Design and implement data storage — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Stable key values that do not change — Stable key values that do not change (Option A) are correct because Azure Cosmos DB uses the shard key to determine the physical partition for each document. If the key value changes after insertion, the document cannot be moved to a different partition, leading to cross-partition queries and degraded performance. A stable key ensures that the partition assignment remains consistent throughout the document's lifetime, which is essential for optimal query routing and throughput management.
What should I do if I get this DP-203 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This DP-203 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-203 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.