Match each Azure messaging pattern to its description.
Drag a concept onto its matching description — or click a concept then click the description.
Point-to-point messaging for decoupling components
Pub/sub messaging with multiple subscribers
Big data streaming ingestion service
Push notification service for mobile apps
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Azure Queue Storage: Simple message queuing for decoupling application components.
Azure messaging patterns include Queue Storage for simple queuing, Service Bus Topics for pub-sub with filters, Event Grid for event routing, and Event Hubs for streaming. Common confusions involve attributing advanced features like dead-lettering to Queue Storage or mixing IoT scenarios with Service Bus Topics.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Azure Queue Storage: Simple message queuing for decoupling application components.
Why this is correct
Azure Queue Storage offers a straightforward and cost-effective message queuing solution primarily designed for basic asynchronous communication. It enables the decoupling of application components, allowing producers to send messages and consumers to process them independently at their own pace. This service is ideal for scenarios requiring simple message delivery guarantees and where advanced features like dead-lettering or message scheduling are not critical.
Azure Service Bus Topic: Publish-subscribe messaging with multiple subscribers and filters.
Why this is correct
Azure Service Bus Topics implement a robust publish-subscribe messaging pattern, facilitating one-to-many communication within enterprise applications. Publishers send messages to a topic, and multiple subscribers can receive copies of these messages through their respective subscriptions. Crucially, Service Bus Topics support advanced filtering capabilities, allowing subscribers to define rules (e.g., SQL filters) to selectively receive only the messages relevant to their specific business logic.
Azure Event Grid: Event routing service for reacting to changes in Azure resources.
Why this is correct
Azure Event Grid is a fully managed event routing service that enables reactive, event-driven architectures by efficiently distributing events from various sources to designated handlers. It specializes in reacting to state changes in Azure resources (e.g., a new blob created in storage, a VM powered on) and custom applications. Event Grid operates on a push-based model, delivering events reliably to subscribers like Azure Functions, Logic Apps, or custom webhooks for immediate processing.
Azure Event Hubs: Big data streaming and event ingestion platform.
Why this is correct
Azure Event Hubs is a highly scalable data streaming platform and event ingestion service specifically engineered for processing millions of events per second. It excels in big data scenarios, serving as the front door for telemetry, logs, and real-time data streams from diverse sources. Event Hubs provides a partitioned, append-only log for event retention, enabling multiple consumer groups to process the same stream independently for analytics, archiving, or other stream processing tasks.
Azure Queue Storage: Reliable message delivery with dead-lettering and scheduling.
Why it's wrong here
This statement is incorrect because Azure Queue Storage does not natively provide advanced enterprise messaging features such as dead-lettering or message scheduling. While it offers basic message reliability through visibility timeouts and retries, capabilities like automatically moving unprocessable messages to a dead-letter queue or delaying message delivery are exclusive to Azure Service Bus queues and topics, which are designed for more complex enterprise integration patterns.
Azure Service Bus Topic: Real-time IoT device communication.
Why it's wrong here
This statement is incorrect because Azure Service Bus Topics are not optimized for real-time IoT device communication. While they support publish-subscribe, their design is geared towards enterprise application integration with higher latency and cost per message compared to specialized IoT services. For high-volume, low-latency device-to-cloud and cloud-to-device messaging, along with device management, Azure IoT Hub or Azure Event Hubs are the appropriate and more efficient choices.
Go deeper
Learn chapter
Azure Functions Development
Key term
Azure Queue Storage
Azure Queue Storage is a cloud service for storing and retrieving large numbers of messages that can be accessed from anywhere, enabling asynchronous communication between application components.
Key term
Azure Service Bus
Azure Service Bus is a cloud-based message broker that allows applications, services, and devices to send and receive messages reliably, even when they are not all running at the same time.
About these practice questions
Courseiva writes every AZ-204 question from scratch — 881 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.