Connect to and consume Azure services and third-party services →mediumMultiple ChoiceObjective-mapped
AZ-204 Practice Question: Connect to and consume Azure services and third-party services
You are building an event-driven application that needs to publish messages to multiple independent subscribers. Each subscriber must be able to filter messages based on custom properties, and each subscriber must receive all messages that match its filter, even if other subscribers have different filters. The solution must guarantee message delivery. Which Azure messaging service should you use?
⚠ Common exam trap
Many candidates confuse Azure Service Bus Queues (point-to-point) with Topics (publish-subscribe), or assume Event Hubs can handle per-subscriber filtering, but Event Hubs lacks broker-side filtering and guarantees each event is consumed by only one consumer per consumer group, not by multiple independent subscribers with custom filters.
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 Service Bus Topics and Subscriptions
Azure Service Bus Topics and Subscriptions are designed for publish-subscribe messaging where multiple independent subscribers each receive a copy of every message that matches their filter criteria. The topic allows publishing messages with custom properties, and each subscription can define a SQL-like filter (using the `SqlFilter` class) to select only relevant messages. This ensures that all subscribers receive all messages matching their filter, with guaranteed delivery via the broker's persistent storage and at-least-once delivery semantics.
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 Queue Storage
Why it's wrong here
Azure Queue Storage offers a basic, highly scalable, and durable FIFO queue service. It is designed for simple asynchronous message passing between components, where each message is intended for a single consumer. Critically, it lacks built-in support for a publish/subscribe pattern, message filtering, or multiple independent subscribers receiving the same message. Therefore, it cannot effectively distribute specific events to multiple interested parties based on criteria.
- ✓
Azure Service Bus Topics and Subscriptions
Why this is correct
Azure Service Bus Topics and Subscriptions are purpose-built for implementing the publish/subscribe messaging pattern, making them ideal for event-driven architectures requiring message filtering. A publisher sends messages to a topic, and multiple independent subscriptions can be configured on that topic. Each subscription can apply SQL-like or correlation filters to receive only a subset of messages, ensuring that consumers only process events relevant to them. This enables robust fan-out capabilities with tailored message delivery.
- ✗
Azure Service Bus Queues
Why it's wrong here
Azure Service Bus Queues provide advanced point-to-point messaging capabilities, including features like dead-lettering, message deferral, and transactions. However, they are fundamentally designed for a single consumer to process each message, ensuring exclusive ownership. They do not inherently support the publish/subscribe model where multiple independent subscribers receive copies of the same message, nor do they offer built-in message filtering for diverse consumption patterns.
- ✗
Azure Event Hubs
Why it's wrong here
Azure Event Hubs is a highly scalable data streaming platform optimized for ingesting millions of events per second from various sources. While it supports multiple consumer groups, each group processes the entire stream of events from a specific offset, primarily for stream processing and analytics scenarios. It does not provide the granular, message-level filtering capabilities for individual subscribers to selectively receive specific event types, which is a key differentiator of Service Bus Topics for pub/sub patterns.
Go deeper
Related to this question
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
One of 881 original AZ-204 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
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.