DP-900 Azure Queue Storage Practice Question
Which TWO of the following are valid use cases for Azure Queue Storage?
⚠ Common exam trap
DP-900 often tests the distinction between Queue Storage (simple async messaging), Blob Storage (unstructured objects), Cosmos DB (document queries), and Event Hubs (streaming) — candidates frequently pick Blob or Event Hubs for queue-like scenarios.
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
✓
Building a serverless workflow with Azure Functions
Option A is correct because Azure Queue Storage is commonly used to trigger serverless workflows: Azure Functions has a Queue Storage trigger/binding that polls the queue and invokes the function when messages arrive, making it a valid use case for building serverless workflows. Option D is correct because Azure Queue Storage provides asynchronous, durable message passing that decouples front-end and back-end components, allowing the web tier to enqueue work while back-end workers process it independently. Option B is not correct because storing JSON documents for querying is a document-database scenario, best served by Azure Cosmos DB or Azure Table Storage, not a queue. Option C is not correct because storing large binary objects for a website is blob storage, i.e., Azure Blob Storage, not Queue Storage. Option E is not correct because real-time event streaming for analytics is handled by Azure Event Hubs (or Kafka), whereas Queue Storage is designed for simple asynchronous messaging, not high-throughput event streaming.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Building a serverless workflow with Azure Functions
Why this is correct
Building a serverless workflow with Azure Functions is a valid Queue Storage use case because a queue's messages can trigger Function execution through the Queue trigger binding. This pattern lets you stage work items durably, with visibility timeouts and poison-message handling, while Azure Functions scales automatically to process the queue, enabling a reliable event-driven pipeline.
- ✗
Storing JSON documents for querying
Why it's wrong here
Storing JSON documents for querying is not a queue use case because queue messages are opaque 64 KB payloads with no schema awareness, indexing, or query language. Azure Cosmos DB is purpose-built for JSON document storage, offering flexible schema, automatic indexing, and SQL-like queries over the document contents.
- ✗
Storing large binary objects for a website
Why it's wrong here
Storing large binary objects for a website is wrong for queues because each queue message is limited to 64 KB, and Queue Storage is not designed to serve assets directly over HTTP. Azure Blob Storage is the correct service for images, videos, and other binary files because it supports large objects, access tiers, and content delivery network integration.
- ✓
Decoupling front-end and back-end components in a web application
Why this is correct
Decoupling front-end and back-end components in a web application is a core Queue Storage scenario: the front end enqueues a request and returns immediately, while a background worker processes it at its own pace. This asynchronous buffer allows the two tiers to scale independently and keeps the application resilient when the back end is temporarily unavailable.
- ✗
Real-time event streaming for analytics
Why it's wrong here
Real-time event streaming for analytics is not appropriate for Queue Storage because queues provide point-to-point consumption of discrete work items rather than high-throughput, multi-consumer event streams. Azure Event Hubs is built for telemetry ingestion and streaming analytics, preserving large volumes of events so multiple downstream processors can read and analyze them.
Visual reference
Quick reference
Azure Blob Storage Tier Comparison
| Tier | Storage Cost | Retrieval Cost | Latency | Use Case |
|---|---|---|---|---|
| Hot | Highest | Lowest | Immediate | Active data, frequent reads |
| Cool | Lower | Higher | Immediate | Data accessed < once / month |
| Cold | Lower still | Higher | Immediate | Data accessed < once / quarter |
| Archive | Lowest | Highest + rehydration delay | Hours | Long-term compliance retention |
Go deeper
Related to this question
Learn chapter
Data Ingestion Patterns: Batch vs Streaming
Key term
Azure Cosmos DB
Azure Cosmos DB is a fully managed, globally distributed NoSQL database service that offers fast reads and writes anywhere in the world with automatic scaling and multiple consistency models.
Key term
Trigger
In Azure data services, a trigger is a predefined automatic action that initiates a process when a specific event occurs, such as data arriving or a schedule being met.
About these practice questions
This DP-900 question is part of Courseiva's 851-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
This DP-900 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 DP-900 exam.