The answer is userId, because it provides high cardinality and ensures even distribution across physical partitions while making the most common query a cost-efficient point read. In Azure Cosmos DB, partition key selection for user data must balance query patterns with storage scalability; userId works perfectly here since each user has a unique value, preventing hot partitions and enabling single-partition lookups. On the DP-900 exam, this tests your understanding that partition keys should match the most frequent query filter and have many distinct values—a common trap is choosing a low-cardinality property like language or theme, which would create uneven data distribution and increase RU costs. Remember the memory tip: “Point reads need unique leads”—if your query targets one specific item, pick a unique identifier like userId to keep reads fast and costs low.
DP-900 Practice Question: Describe considerations for working with non-relational data on Azure
This DP-900 practice question tests your understanding of describe considerations for working with non-relational data on azure. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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.
A mobile app stores user preferences as JSON documents in Azure Cosmos DB. The document includes userId, theme, language, and notification settings. The most common query retrieves the document for a specific userId. To minimize cost and ensure even distribution, which property should be chosen as the partition key?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "minimum / minimize"
Why it matters: Asks for the least resource use — fewest addresses, smallest subnet, lowest overhead. Eliminate over-provisioned options even if they would technically work.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
userId
The userId property is the ideal partition key because it provides high cardinality (each user has a unique ID) and ensures even request distribution across physical partitions. Since the most common query retrieves a document by userId, using it as the partition key makes those queries point reads (single-partition queries), which are the most cost-efficient and fastest in Azure Cosmos DB.
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.
✓
userId
Why this is correct
userId has high cardinality and evenly distributes data across partitions, minimizing Request Unit (RU) consumption for point reads.
Clue confirmation
The clue word "minimum / minimize" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
theme
Why it's wrong here
Theme has low cardinality (few unique values), leading to hot partitions and uneven distribution.
✗
language
Why it's wrong here
Language also has low cardinality, causing skewed partitions and performance issues.
✗
a concatenation of userId and language
Why it's wrong here
While userId ensures distribution, adding language is redundant and increases storage overhead without improving the main query.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often choose a concatenated key (option D) thinking it adds uniqueness or query flexibility, but Azure Cosmos DB's partition key design favors a single high-cardinality attribute for even distribution and simple point reads.
Detailed technical explanation
How to think about this question
In Azure Cosmos DB, the partition key is hashed to determine the physical partition; high-cardinality keys like userId ensure the hash space is uniformly utilized, avoiding hot partitions. Point reads using the partition key and ID consume only 1 request unit (RU) for documents up to 1 KB, making them the most efficient operation. Real-world scenarios with millions of users demonstrate that using a natural high-cardinality attribute like userId keeps RU consumption predictable and avoids 429 throttling errors.
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 startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-900 question in full detail.
Describe considerations for working with non-relational data on Azure — This question tests Describe considerations for working with non-relational data on Azure — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: userId — The userId property is the ideal partition key because it provides high cardinality (each user has a unique ID) and ensures even request distribution across physical partitions. Since the most common query retrieves a document by userId, using it as the partition key makes those queries point reads (single-partition queries), which are the most cost-efficient and fastest in Azure Cosmos DB.
What should I do if I get this DP-900 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "minimum / minimize". Asks for the least resource use — fewest addresses, smallest subnet, lowest overhead. Eliminate over-provisioned options even if they would technically work.
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-900 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-900 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.