AZ-204 Practice Question: Connect to and consume Azure services and third-party services

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 Cosmos DB

  Why it's wrong here

  Azure Cosmos DB is a globally distributed, multi-model database service designed for storing and querying data with low latency and high availability. It is fundamentally a data persistence layer, not a messaging queue or broker. While it could technically be used to store messages, it lacks the native queuing semantics like message visibility timeouts, automatic deletion upon processing, and efficient consumer polling mechanisms inherent in dedicated messaging services, making it an unsuitable and inefficient choice for asynchronous microservice decoupling.

• ✓

  Azure Service Bus

  Why this is correct

  Azure Service Bus is an enterprise-grade message broker offering advanced features like message sessions, topics for publish/subscribe patterns, transactions, and dead-lettering. While excellent for complex integration scenarios requiring guaranteed message delivery and sophisticated routing, it introduces more overhead and cost than necessary for simple asynchronous decoupling between microservices. For basic point-to-point message queuing, its extensive feature set is often overkill, making it a less optimal choice when simplicity is paramount.

• ✗

  Azure Queue Storage

  Why it's wrong here

  Azure Queue Storage provides a simple, highly scalable, and cost-effective cloud messaging service for large volumes of messages. It is specifically designed for asynchronous message passing, enabling microservices to communicate without direct dependency, thus achieving effective decoupling. Messages are stored in a queue and retrieved by a single consumer, making it ideal for basic task distribution, work item queues, and simple asynchronous workflows where message order is not strictly guaranteed across all messages but individual message processing is robust.

• ✗

  Azure Event Hubs

  Why it's wrong here

  Azure Event Hubs is a highly scalable data streaming platform and event ingestion service optimized for capturing, retaining, and processing millions of events per second. It is designed for scenarios involving telemetry, log aggregation, and real-time analytics where multiple consumers might read the same stream of events. Unlike a traditional queue, Event Hubs does not remove messages upon consumption; instead, it retains them for a configurable period, making it unsuitable for simple task-based decoupling where messages are processed once and then logically removed.