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
An application publishes order events that multiple independent subscribers must process. Subscribers may be added later without changing the publisher. Which Azure messaging service should be used? The team wants the control to be enforceable during normal operations.
⚠ Common exam trap
It's easy for candidates to confuse Azure Storage Queue (point-to-point) with Service Bus topics (pub/sub), missing the requirement for multiple independent subscribers that can be added later without changing the publisher.
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 topic
Azure Service Bus topics support a publish/subscribe pattern where multiple independent subscribers can each receive a copy of every published message. Subscribers can be added later without modifying the publisher, and the team can enforce control during normal operations using topic-level authorization rules and subscription filters.
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 lifecycle policy
Why it's wrong here
Azure Blob Storage lifecycle policies are designed to automate the management of objects stored within Blob Storage containers, handling tasks like tiering, archiving, or deleting blobs based on defined rules. This service is fundamentally a persistent object storage solution and does not provide any native capabilities for real-time event publishing or distributing messages to multiple independent subscribers. It lacks the messaging semantics and delivery guarantees required for an event distribution system.
- ✗
Azure Storage Queue
Why it's wrong here
Azure Storage Queues provide a basic, durable, and scalable message queuing service primarily designed for point-to-point communication patterns. In this model, each message placed onto the queue is intended for a single consumer, which retrieves and processes it before it is removed. Storage Queues do not natively support the publish-subscribe pattern where multiple independent applications can simultaneously receive and process the same event message.
- ✗
Azure Cache for Redis list only
Why it's wrong here
While Azure Cache for Redis offers various data structures, including lists for queue-like operations and a native publish-subscribe feature, it is fundamentally an in-memory data store optimized for caching and low-latency access. It is not designed as a durable, enterprise-grade messaging broker for complex event distribution scenarios requiring guaranteed delivery, advanced subscription management, or dead-lettering capabilities. Relying solely on Redis lists for this requirement would lack the robustness of a dedicated messaging service.
- ✓
Azure Service Bus topic
Why this is correct
Azure Service Bus Topics are purpose-built for enterprise-grade asynchronous messaging, specifically implementing the publish-subscribe pattern. Publishers send messages to a topic, and multiple independent applications can each create their own distinct subscriptions to that topic. Each subscription receives a copy of the messages published to the topic, enabling diverse consumers to process the same event concurrently and independently. This service provides robust features like message filtering, dead-lettering, and guaranteed delivery, making it ideal for distributing events to multiple systems.
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
This AZ-204 question is part of Courseiva's 881-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 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.