Question 539 of 997
Develop for Azure storagemediumMultiple ChoiceObjective-mapped

Quick Answer

The correct choice is to store the counter in Azure Cosmos DB and use stored procedures to increment atomically. This works because Cosmos DB stored procedures execute within a server-side transactional scope, providing ACID-compliant atomic operations that serialize concurrent writes from multiple instances, preventing conflicts. In contrast, Azure Blob Storage relies on eventual consistency and lacks native atomic increment support, making it unsuitable for this requirement. On the Microsoft Azure Developer Associate AZ-204 exam, this scenario tests your understanding of transactional guarantees in Cosmos DB versus Blob Storage’s limitations—a common trap is assuming Blob Storage’s lease or append blobs can achieve atomicity, but they cannot guarantee serialized increments under high concurrency. Remember the memory tip: “Blob for blobs, Cosmos for counters” to quickly recall that atomic counter operations demand the database engine’s transactional scope, not storage-level primitives.

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 designing a solution that requires atomic operations on a counter stored in Azure Blob Storage. The counter must be updated by multiple instances without conflicts. Which approach should you use?

Question 1mediummultiple 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

Store the counter in Azure Cosmos DB and use stored procedures to increment atomically.

Option A is correct because Azure Cosmos DB stored procedures execute within the database engine's transactional scope, providing ACID-compliant atomic operations. This ensures that concurrent increments from multiple instances are serialized without conflicts, which is not natively supported by Azure Blob Storage's eventual consistency model.

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.

  • Store the counter in Azure Cosmos DB and use stored procedures to increment atomically.

    Why this is correct

    Cosmos DB supports atomic operations via stored procedures.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Use Azure Queue Storage to queue increment messages.

    Why it's wrong here

    Queue storage is for messaging, not for storing state.

  • Store the counter in Azure Table Storage and use optimistic concurrency with ETags.

    Why it's wrong here

    Optimistic concurrency requires retries; not atomic.

  • Use Append Blob to append each increment as a new block and sum them later.

    Why it's wrong here

    Append Blob does not provide atomic updates; summing later may miss increments.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates assume Azure Blob Storage's lease or append features can provide atomicity, but Blob Storage lacks server-side atomic read-modify-write operations, making Cosmos DB the only Azure service among the options that natively supports atomic counter updates with stored procedures.

Detailed technical explanation

How to think about this question

Cosmos DB stored procedures run as a single transaction on the primary replica, leveraging the database's multi-version concurrency control (MVCC) to isolate writes. The stored procedure can read the current counter value, increment it, and write back—all within a single server-side script that holds a resource lock, ensuring no other concurrent operation interferes. This pattern is commonly used for distributed counters, sequence generators, or rate limiters where strong consistency is required.

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: Store the counter in Azure Cosmos DB and use stored procedures to increment atomically. — Option A is correct because Azure Cosmos DB stored procedures execute within the database engine's transactional scope, providing ACID-compliant atomic operations. This ensures that concurrent increments from multiple instances are serialized without conflicts, which is not natively supported by Azure Blob Storage's eventual consistency model.

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 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.

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.