Quick Answer
The correct answer is that lower cost for simple key-value workloads is a valid reason to choose Azure Table Storage over Azure Cosmos DB. This is because Table Storage operates on a pay-per-query model with no need to provision throughput, whereas Cosmos DB requires explicit configuration of Request Units per second (RU/s) for each container, adding operational overhead and cost for lightweight, infrequent access patterns. On the AZ-204 exam, this distinction tests your understanding of when to select a simpler, cheaper storage solution versus a globally distributed, multi-model database; a common trap is assuming Cosmos DB is always superior due to its features, but for basic key-value lookups with minimal latency requirements, Table Storage’s OData-based REST API and lack of reserved capacity make it more straightforward and cost-effective. Remember the mnemonic “Simple Saves” — for simple schemas and sparse queries, Table Storage saves both money and management effort.
This AZ-204 practice question tests your understanding of develop for azure storage. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 TWO of the following are valid reasons to use Azure Table Storage instead of Azure Cosmos DB?
Global distribution with multi-master writes
Why wrong: Cosmos DB provides global distribution.
Lower latency and higher throughput
Why wrong: Cosmos DB offers better performance.
Simpler API and no need for throughput provisioning
Table Storage has a simpler model.
Lower cost for simple key-value workloads
Table Storage is cheaper.
Support for complex queries with indexing
Why wrong: Cosmos DB has richer query support.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Simpler API and no need for throughput provisioning
Option C is correct because Azure Table Storage offers a simpler REST API based on OData and does not require explicit throughput provisioning (RU/s). In contrast, Azure Cosmos DB requires you to configure request units per second for each container, which adds operational complexity. For simple key-value workloads, Table Storage's pay-per-query model with no reserved capacity is more straightforward.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Global distribution with multi-master writes
Why it's wrong here
Cosmos DB provides global distribution.
Lower latency and higher throughput
Why it's wrong here
Cosmos DB offers better performance.
Simpler API and no need for throughput provisioning
Why this is correct
Table Storage has a simpler model.
Related concept
Read the scenario before looking for a memorised answer.
Lower cost for simple key-value workloads
Why this is correct
Table Storage is cheaper.
Related concept
Read the scenario before looking for a memorised answer.
Support for complex queries with indexing
Why it's wrong here
Cosmos DB has richer query support.
Common exam traps
The trap here is that candidates assume 'simpler' always means 'better performance,' but Azure Table Storage's simplicity comes at the cost of limited indexing and throughput, making it unsuitable for low-latency or complex query scenarios.
Detailed technical explanation
Azure Table Storage uses a schema-less design with a fixed index on PartitionKey and RowKey, making it ideal for fast point lookups but inefficient for range scans or filtering on non-key attributes. Under the hood, Table Storage is backed by Azure Storage partitions that scale to 20,000 IOPS per partition, whereas Cosmos DB uses a distributed database engine with automatic indexing and tunable consistency levels. In a real-world scenario, a logging system storing millions of simple event records per day would benefit from Table Storage's lower cost and simpler management, while an e-commerce product catalog requiring real-time faceted search would need Cosmos DB's indexing and query capabilities.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Develop for Azure storage — study guide chapter
Learn the concepts, then practise the questions
Develop for Azure storage practice questions
Targeted practice on this topic area only
All AZ-204 questions
997 questions across all exam domains
Microsoft Azure Developer Associate AZ-204 study guide
Full concept coverage aligned to exam objectives
AZ-204 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise AZ-204 questions linked to Develop Azure compute solutions.
Practise AZ-204 questions linked to Develop for Azure storage.
Practise AZ-204 questions linked to Implement Azure security.
Practise AZ-204 questions linked to Connect to and consume Azure services and third-party services.
Practise AZ-204 questions linked to Monitor, troubleshoot, and optimize Azure solutions.
Practise AZ-204 questions linked to AZ-204 fundamentals.
Practise AZ-204 questions linked to AZ-204 scenario.
Practise AZ-204 questions linked to AZ-204 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Develop for Azure storage — This question tests Develop for Azure storage — Read the scenario before looking for a memorised answer..
The correct answer is: Simpler API and no need for throughput provisioning — Option C is correct because Azure Table Storage offers a simpler REST API based on OData and does not require explicit throughput provisioning (RU/s). In contrast, Azure Cosmos DB requires you to configure request units per second for each container, which adds operational complexity. For simple key-value workloads, Table Storage's pay-per-query model with no reserved capacity is more straightforward.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Last reviewed: Jun 24, 2026
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.