AZ-204 Develop for Azure storage Practice Question
Your application writes millions of small records (each under 1 KB) to Azure Table Storage every day. You notice that query performance degrades over time. Which design change would most improve performance?
⚠ Common exam trap
Candidates often assume increasing throughput limits (Option C) or using a single partition key (Option D) will fix performance, but Azure's per-partition scaling constraints mean only distributing the partition key (Option B) addresses the hot partition bottleneck.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a hash of the timestamp as the PartitionKey to distribute writes evenly.
Using a hash of the timestamp as the PartitionKey distributes writes evenly across partition ranges, preventing hot partitions. Azure Table Storage scales by splitting partitions across storage nodes; sequential timestamps create a hot partition on the last node, degrading throughput. A hash ensures uniform load, maximizing the account's 20,000 IOPS per partition target.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Store all records in a single blob and use Blob Storage.
Why it's wrong here
Storing millions of small, frequently updated records in a single Azure Blob Storage blob is highly inefficient and impractical. Blob Storage is optimized for storing large, immutable files or for append-only scenarios, not for granular record-level updates. Each modification to a single record within such a blob would necessitate downloading the entire blob, performing the small change, and then re-uploading the complete blob, leading to excessive I/O, increased latency, and significantly higher transaction costs.
- ✓
Use a hash of the timestamp as the PartitionKey to distribute writes evenly.
Why this is correct
Using a hash of the timestamp as the PartitionKey is an effective strategy for distributing high-volume writes evenly across multiple partitions in Azure Table Storage. This approach prevents the creation of "hot partitions" by ensuring that records arriving in close temporal proximity are not necessarily grouped into the same physical partition. By spreading the write load, this method maximizes the overall throughput and scalability of the table, allowing the application to handle millions of small records efficiently without encountering throttling.
- ✗
Increase the storage account's throughput limits.
Why it's wrong here
Increasing the storage account's overall throughput limits does not directly resolve performance bottlenecks caused by "hot partitions" within a specific service like Azure Table Storage. While a storage account has aggregate limits, individual partitions also have their own throughput ceilings. If all write operations are concentrated on a single partition due to a poor PartitionKey strategy, that specific partition will still become saturated and throttle requests, regardless of the higher account-level limits. The issue is at the partition level, not solely the account level.
- ✗
Use a single PartitionKey and a sequential RowKey.
Why it's wrong here
Employing a single PartitionKey for all records, even with a sequential RowKey, will inevitably lead to a severe performance bottleneck and throttling in Azure Table Storage. All write operations would be directed to that single partition, quickly exceeding its inherent throughput capacity. Azure Table Storage scales by distributing data and operations across multiple partitions; concentrating all data into one partition negates this fundamental scaling mechanism, resulting in poor performance for high-volume write scenarios.
Go deeper
Related to this question
About these practice questions
Courseiva writes every AZ-204 question from scratch — 881 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.