The answer is to use PartitionKey as the customer ID and RowKey based on a sortable timestamp. This design is correct because Azure Table Storage queries are most efficient when they target a single partition, and using the customer ID as the PartitionKey ensures all session records for one customer are co-located. The RowKey, formatted as a sortable timestamp such as inverted ticks, then allows the service to perform efficient range queries by scanning only the relevant rows in that partition’s natural index order, avoiding a full table scan. On the AZ-204 exam, this scenario tests your understanding of how to optimize for common query patterns—specifically, the trade-off between partition distribution and query performance. A common trap is choosing a timestamp as the PartitionKey, which scatters data across partitions and forces cross-partition queries. Remember the memory tip: “Partition for equality, Row for range”—the PartitionKey should match the exact filter, while the RowKey handles the range.
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.
A table stores session records in Azure Table Storage. Queries frequently retrieve all records for one customer in a time range. What key design is best?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
PartitionKey as customer ID and RowKey based on sortable timestamp
Option C is correct because Azure Table Storage queries are most efficient when they target a single partition key. Using the customer ID as the PartitionKey ensures all records for a customer are in the same partition, and using a sortable timestamp (e.g., inverted ticks) as the RowKey allows efficient range queries within that partition, leveraging the table's natural index order.
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.
✗
RowKey as a constant value
Why it's wrong here
A constant RowKey prevents useful ordering and uniqueness.
✗
PartitionKey as a random GUID for every record
Why it's wrong here
Random partitions prevent efficient customer-range queries.
✓
PartitionKey as customer ID and RowKey based on sortable timestamp
Why this is correct
This supports efficient partition filtering and range scans by time.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
PartitionKey as the full JSON payload
Why it's wrong here
Large unstructured keys are inefficient and do not match the query pattern.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may think randomizing the PartitionKey improves load balancing, but for query-heavy workloads targeting a single entity group, a fixed PartitionKey is essential for performance, and Azure Table Storage handles hot partitions through other mechanisms like entity-level throttling.
Detailed technical explanation
How to think about this question
Azure Table Storage uses a composite index on (PartitionKey, RowKey) for fast point lookups and range scans. By choosing a sortable RowKey like 'DateTime.MaxValue.Ticks - DateTime.UtcNow.Ticks', you can reverse-chronologically order records within a partition, enabling efficient time-range queries with a single partition scan. This design also supports server-side filtering on RowKey, reducing data transfer and cost.
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: PartitionKey as customer ID and RowKey based on sortable timestamp — Option C is correct because Azure Table Storage queries are most efficient when they target a single partition key. Using the customer ID as the PartitionKey ensures all records for a customer are in the same partition, and using a sortable timestamp (e.g., inverted ticks) as the RowKey allows efficient range queries within that partition, leveraging the table's natural index order.
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.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
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-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.