The answer is a property frequently used as a filter in queries. This is correct because in Azure Cosmos DB, the partition key determines how data and request unit (RU) consumption are distributed across physical partitions; selecting a property that appears often in your WHERE clauses ensures that queries are efficiently routed to a single partition, minimizing cross-partition queries and avoiding hot partitions that throttle throughput. On the Microsoft Azure Solutions Architect Expert AZ-305 exam, this concept tests your ability to design for performance and scalability, often appearing in scenario-based questions where you must choose between candidate keys like timestamp, user ID, or device type. A common trap is selecting a high-cardinality key like a GUID, which distributes data evenly but fails as a query filter, leading to poor performance. Remember the memory tip: "Filter first, then spread" — prioritize query patterns over even distribution alone.
AZ-305 Design data storage solutions Practice Question
This AZ-305 practice question tests your understanding of design data storage solutions. 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.
Which THREE factors should you consider when selecting a partition key for an Azure Cosmos DB container? (Select three.)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Even distribution of request unit (RU) consumption
Option A is correct because an even distribution of request unit (RU) consumption across physical partitions prevents hot partitions, which can throttle throughput and degrade performance. In Azure Cosmos DB, the partition key determines how data and throughput are distributed; if RU consumption is skewed, some partitions become overloaded while others remain underutilized, violating the design goal of uniform load.
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.
✓
Even distribution of request unit (RU) consumption
Why this is correct
Even RU distribution prevents throttling.
Related concept
Read the scenario before looking for a memorised answer.
✗
Low cardinality to reduce overhead
Why it's wrong here
Low cardinality causes hot partitions.
✓
High cardinality (many distinct values)
Why this is correct
High cardinality ensures even distribution across partitions.
Related concept
Read the scenario before looking for a memorised answer.
✗
Property with large binary data
Why it's wrong here
Large binary properties are inefficient as partition keys.
✓
Property frequently used as a filter in queries
Why this is correct
Using the partition key in queries minimizes cross-partition queries.
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 confuse low cardinality with efficiency, but Cosmos DB requires high cardinality to avoid storage limits and hot partitions, and they may also mistakenly think large binary properties are acceptable partition keys despite the 2 KB limit and indexing overhead.
Detailed technical explanation
How to think about this question
Under the hood, Cosmos DB uses a hash-based partitioning scheme where the partition key value is hashed to determine the physical partition. A high-cardinality key (e.g., user ID or device ID) ensures that the hash space is evenly populated, distributing both data and RU consumption across partitions. In real-world scenarios, choosing a partition key like `/date` with only daily values can cause a hot partition on the current day, while a key like `/userId` with millions of distinct values avoids this bottleneck.
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 AZ-305 question in full detail.
Design data storage solutions — This question tests Design data storage solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Even distribution of request unit (RU) consumption — Option A is correct because an even distribution of request unit (RU) consumption across physical partitions prevents hot partitions, which can throttle throughput and degrade performance. In Azure Cosmos DB, the partition key determines how data and throughput are distributed; if RU consumption is skewed, some partitions become overloaded while others remain underutilized, violating the design goal of uniform load.
What should I do if I get this AZ-305 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 AZ-305 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 AZ-305 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.