The correct fix for Cosmos DB hot partition throttling is to choose a partition key with higher cardinality and even request distribution. This resolves the issue because a partition key with only five possible values forces all writes and reads into a handful of logical partitions, overwhelming the underlying physical partitions and triggering rate-limiting 429 errors. On the AZ-204 exam, this scenario tests your understanding of partition key design as a core performance strategy for Cosmos DB—a common trap is assuming any unique field will work, when in fact the key must also distribute load evenly across partitions. Remember the memory tip: "High cardinality, even traffic—no hot spots, no throttling."
AZ-204 Develop for Azure storage Practice Question
This AZ-204 practice question tests your understanding of develop for azure storage. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 Cosmos DB container for session records receives hot-partition throttling because the partition key has only five possible values. What should the developer change?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Choose a partition key with higher cardinality and even request distribution
Option C is correct because a partition key with only five values leads to hot partitions, where one or a few partitions handle the majority of requests, causing throttling. By choosing a partition key with higher cardinality (many distinct values) and even request distribution, the load is spread evenly across physical partitions, eliminating hot spots and throttling.
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.
✗
Increase the default TTL
Why it's wrong here
TTL controls item expiry, not partition distribution.
✗
Enable analytical store only
Why it's wrong here
Analytical store supports analytics but does not correct transactional hot partitions.
✓
Choose a partition key with higher cardinality and even request distribution
Why this is correct
A good partition key spreads storage and throughput across logical partitions.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use a stored procedure for every write
Why it's wrong here
Stored procedures do not fix a hot partition key.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse throttling with performance tuning (TTL) or data storage (analytical store), rather than recognizing that the root cause is an insufficiently granular partition key leading to uneven request distribution.
Detailed technical explanation
How to think about this question
Under the hood, Cosmos DB uses the partition key to hash documents into physical partitions; with only five distinct key values, the hash space is severely limited, causing all requests to concentrate on a few physical partitions. In a real-world scenario, a session ID or user ID (high cardinality) would distribute writes evenly, whereas a status field like 'Active' or 'Inactive' (low cardinality) creates hot partitions that trigger rate-limiting (429 errors) even if total RU/s is sufficient.
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 AZ-204 question in full detail.
Develop for Azure storage — This question tests Develop for Azure storage — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Choose a partition key with higher cardinality and even request distribution — Option C is correct because a partition key with only five values leads to hot partitions, where one or a few partitions handle the majority of requests, causing throttling. By choosing a partition key with higher cardinality (many distinct values) and even request distribution, the load is spread evenly across physical partitions, eliminating hot spots and throttling.
What should I do if I get this AZ-204 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 →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A Cosmos DB container for session records receives hot-partition throttling because the partition key has only five possible values. What should the developer change? The design must avoid adding custom operational scripts.
medium
A.Increase the default TTL
B.Enable analytical store only
✓ C.Choose a partition key with higher cardinality and even request distribution
D.Use a stored procedure for every write
Why C: Option C is correct because hot-partition throttling occurs when a partition key has low cardinality (few distinct values), causing uneven request distribution and exceeding the physical partition's throughput limits. Choosing a partition key with higher cardinality and even request distribution spreads operations across more physical partitions, eliminating throttling without custom scripts.
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-204 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-204 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.