AZ-305 Practice Question 100: Service Bus Topics Subscription Filters

Microsoft Azure Solutions Architect Expert (AZ-305) · Test 10 · question 10 of 10

Infrastructure Solutionseasy

A logistics company publishes a single ShipmentUpdated event whenever any shipment changes status. Four independent downstream systems each need their own copy of every event that matches their own criteria: the billing system needs only events where the status is Delivered, the customer notification system needs every event, the warehouse system needs only events for a specific set of warehouse IDs, and the analytics system needs every event. Each system must process its own copy at its own pace without one slow consumer affecting the others. What should you include in the messaging design?

Select one answer
Show answer and explanation

Answer:

  • A. A single Azure Service Bus topic with one subscription per downstream system, using subscription filters to select the events each system needs

Service Bus topics implement publish and subscribe: the publisher sends each event once to the topic, and every subscription gets its own copy. A subscription filter, such as a SQL filter on the status property or the warehouse ID, lets billing and the warehouse system receive only the events they need, while a subscription with the default filter (or no filter) lets notifications and analytics receive everything. Each subscription is processed independently, so a slow consumer on one subscription does not affect the others.

Option B is wrong because a queue with sessions is designed to distribute related messages to a single consumer per session for ordered processing, not to fan the same event out to multiple independent systems; competing consumers on a queue would each get only a subset of messages, not a full copy. Option C is wrong because it makes the publisher responsible for filtering and for knowing about every downstream consumer, which does not scale and duplicates message delivery logic that the broker should own. Option D is wrong because Event Hubs is built for high-throughput telemetry ingestion and replay by consumer groups reading the same stream, but it has no built-in per-consumer content filtering, so the billing and warehouse systems would still need their own filtering logic on every event they receive.

Reference: Service Bus queues, topics, and subscriptions

Practice Test 10 ›

Study guides for AZ-305