AZ-900 Describe Azure architecture and services Practice Question

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 is a simple REST-based message queue designed for basic FIFO processing, but it lacks enterprise-grade features such as topics and subscriptions, dead-letter queuing, exactly-once delivery, or transaction support. It is best suited for decoupling components in small applications, not for critical enterprise integration scenarios where advanced messaging patterns and guaranteed ordering are required. For this scenario, Azure Service Bus provides those richer capabilities, making Queue Storage incorrect.

• ✗

  Azure Event Grid

  Why it's wrong here

  Azure Event Grid is an event routing service that delivers discrete event notifications reactively from sources such as Azure resources or custom apps to subscribers using a publish/subscribe model. It does not provide a message queue with FIFO guarantees, dead-lettering for application-level errors, or the long-lived message retention needed for enterprise messaging workloads. Event Grid is ideal for event-driven serverless responses, but it is not designed for the ordered, reliable messaging that Azure Service Bus offers.

• ✓

  Azure Service Bus

  Why this is correct

  Azure Service Bus is the correct choice because it is a fully managed enterprise message broker that supports topics and subscriptions for pub/sub messaging, dead-letter queues for poison-message handling, and session-based FIFO ordering with duplicate detection. It also offers transactions, at-least-once and exactly-once delivery options, and integration with enterprise protocols like AMQP, which are essential for reliable, ordered application integration. These features go far beyond simple queue and event routing, aligning with the requirement for robust enterprise messaging.

• ✗

  Azure Event Hubs

  Why it's wrong here

  Azure Event Hubs is built for massive-scale telemetry and log streaming, ingesting millions of events per second and focusing on throughput rather than enterprise application messaging semantics. It does not natively provide message sessions, transactions, or dead-letter queues, and it treats consumers as independent partition readers with a replay model, not as competing consumers receiving ordered messages. While Event Hubs can ingest and stream data, it is not a replacement for the broker-based, feature-rich messaging that Azure Service Bus provides.