Question 451 of 997
Develop for Azure storageeasyMultiple ChoiceObjective-mapped

Quick Answer

The answer is Azure Table Storage, because it is a NoSQL key-value store designed for low-latency access to individual items by partition key and row key, making it ideal for storing millions of small JSON documents (~1 KB) that undergo frequent concurrent updates. Its optimistic concurrency control, implemented through ETags, allows multiple users to update the same document without locking, as each write checks the ETag to prevent overwriting stale data. On the AZ-204 exam, this scenario tests your ability to differentiate between Azure Table Storage and Cosmos DB, where a common trap is choosing Cosmos DB for its global distribution features when the requirement is simply low-latency, single-region access with no complex querying. Remember the memory tip: “ETags for tags on small docs” — ETags handle concurrent updates on tiny JSON payloads, and Table Storage excels at cheap, fast key-value lookups for structured data under 1 MB.

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 need to store millions of small JSON documents (each ~1 KB) that are frequently updated by multiple concurrent users. You require low-latency access to individual documents. Which Azure Storage solution should you use?

Question 1easymultiple choice
Full question →

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

Azure Table Storage

Azure Table Storage is a NoSQL key-value store optimized for storing large volumes of structured, non-relational data with low-latency access by partition key and row key. It supports millions of small JSON documents (~1 KB) and handles frequent concurrent updates via optimistic concurrency control using ETags, making it ideal for this scenario.

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.

  • Azure Blob Storage with Block blobs

    Why it's wrong here

    Blob Storage is better for larger objects (>1 MB). For small documents, the overhead and cost are higher compared to Table Storage.

  • Azure Table Storage

    Why this is correct

    Table Storage is a NoSQL store designed for large quantities of small entities with partition key and row key, ideal for this scenario.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Azure Files with SMB protocol

    Why it's wrong here

    Azure Files is for file shares and not optimized for high-volume concurrent updates on small documents.

  • Azure Cosmos DB for NoSQL

    Why it's wrong here

    Cosmos DB provides low latency but is significantly more expensive than Table Storage for simple document storage.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often choose Azure Cosmos DB for NoSQL because it is a more feature-rich document database, but the question emphasizes cost-effectiveness and simplicity for high-volume, low-latency key-value access, which is exactly where Azure Table Storage excels.

Detailed technical explanation

How to think about this question

Azure Table Storage partitions data by partition key, enabling fast point queries using the combination of partition key and row key, with consistent latency under 10 ms for a single document. It uses ETags for optimistic concurrency, allowing multiple concurrent users to update the same document without locking, and supports batch operations within the same partition. In a real-world scenario like a gaming leaderboard or IoT device state store, Table Storage handles millions of small records with high throughput at a fraction of the cost of Cosmos DB.

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.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related AZ-204 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free AZ-204 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this AZ-204 question test?

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: Azure Table Storage — Azure Table Storage is a NoSQL key-value store optimized for storing large volumes of structured, non-relational data with low-latency access by partition key and row key. It supports millions of small JSON documents (~1 KB) and handles frequent concurrent updates via optimistic concurrency control using ETags, making it ideal for this scenario.

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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 11, 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.

Loading comments…

Sign in to join the discussion.

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.