The answer is to use device ID as the partition key and timestamp as the row key. This strategy maximizes write throughput by distributing the 10,000 events per second across multiple partitions, each of which can handle up to 20,000 operations per second, thus avoiding throttling at a single partition. At the same time, using timestamp as the row key enables efficient range queries for a specific device within a time window because Azure Table Storage automatically sorts rows by row key within a partition. On the AZ-204 exam, this scenario tests your understanding of partition key design for Azure Table Storage under high-throughput telemetry loads, often appearing as a scenario where a single partition key like timestamp would cause hot partitions and throttling. A common trap is choosing timestamp as the partition key, which would funnel all writes into one partition and limit throughput. Memory tip: think “Device divides, time sorts”—the partition key spreads the load, the row key orders the results.
AZ-204 Develop for Azure storage Practice Question
This AZ-204 practice question tests your understanding of develop for azure storage. 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.
You are developing an application that writes telemetry data to Azure Table Storage. Each telemetry event is about 5 KB in size, and the application writes up to 10,000 events per second. The data is queried by device ID and timestamp range. What is the most efficient partitioning strategy to maximize write throughput and query performance?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use device ID as the partition key and timestamp as the row key.
Option B is correct because using device ID as the partition key distributes writes across multiple partitions, avoiding throttling from a single partition's scalability limit (up to 20,000 operations per second per partition). Using timestamp as the row key enables efficient range queries for a specific device within a time window, leveraging the table's natural sort order on row key.
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.
✗
Use timestamp as the partition key and device ID as the row key.
Why it's wrong here
Timestamp as partition key creates hot partitions.
✓
Use device ID as the partition key and timestamp as the row key.
Why this is correct
This distributes writes across partitions and allows efficient range queries.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use device type as the partition key and timestamp as the row key.
Why it's wrong here
Device type is not unique enough and may cause uneven distribution.
✗
Use a single partition key for all events and use timestamp as the row key.
Why it's wrong here
A single partition key limits write throughput.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often choose timestamp as the partition key (Option A) because they think it naturally supports time-range queries, but they overlook the severe write throttling caused by a hot partition at each timestamp second.
Detailed technical explanation
How to think about this question
Azure Table Storage partitions are load-balanced across storage nodes, and each partition can handle up to 2,000 IOPS (20,000 operations per second for small entities). By using device ID as partition key, you distribute writes across potentially thousands of partitions, achieving linear scalability. The row key's lexicographic order allows efficient range scans for timestamps, and the combination ensures that queries for a device's data within a time range hit a single partition, minimizing latency.
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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
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: Use device ID as the partition key and timestamp as the row key. — Option B is correct because using device ID as the partition key distributes writes across multiple partitions, avoiding throttling from a single partition's scalability limit (up to 20,000 operations per second per partition). Using timestamp as the row key enables efficient range queries for a specific device within a time window, leveraging the table's natural sort order on row key.
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. An application stores sensor readings in Azure Table Storage. Each sensor produces thousands of readings per hour. Queries always filter by sensor ID and time range. A developer needs to choose the partition key and row key. Which design best balances query performance and write throughput?
medium
✓ A.Partition key: sensor ID; row key: ISO timestamp of the reading
B.Partition key: a single constant ('all-sensors'); row key: sensor ID + timestamp
C.Partition key: timestamp (rounded to the hour); row key: sensor ID
D.Partition key: random GUID per reading; row key: timestamp
Why A: Option A is correct because it uses sensor ID as the partition key, which ensures all readings for a given sensor are stored in the same partition, enabling efficient range queries by row key (timestamp). This design avoids hot partitions by distributing writes across different sensors, while the row key allows fast point lookups and range scans within a time window, balancing query performance and write throughput.
Last reviewed: Jun 24, 2026
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.
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.