A 311 triage publisher must route the same incident message so housing and public-works AI workers each receive only their category. What Service Bus feature fits?
Select an answer to reveal the explanation.
Short Explanation
A Service Bus topic is like the city radio dispatcher broadcasting once while housing and public-works each keep their own filtered radio—same incident, different desks, no spam.
Full Explanation
When a single 311 incident publication must reach multiple municipal AI workers—but each department should only see its own category—Service Bus topics with filtered subscriptions are the designed pub/sub pattern. The triage publisher sends one message to a topic; housing and public-works each maintain a subscription with a SQL or correlation filter on category (or equivalent application properties). Service Bus evaluates those filters server-side so housing workers never compete for public-works messages and vice versa. That preserves one publish path, independent scale per department, and clear ownership of each subscription’s dead-letter queue.
A single FIFO queue that every department must scan and discard fails conceptually: competing consumers on one queue deliver each message to only one receiver, and forcing every worker to inspect-and-NACK unwanted categories wastes lock time, increases contention, and invites accidental completion of another desk’s work. Nightly full exports of all 311 tickets into each department database fail on latency and freshness: emergency or same-day triage AI cannot wait for batch dumps, and exports are not a messaging contract with filters and retries. Sending duplicate synchronous HTTP posts from the publisher to every worker couples availability: if one department endpoint is down, the publisher either blocks, partially succeeds, or invents ad-hoc retry logic that Service Bus already provides.
Exam caveat: topics fan out; queues compete. Choosing a queue when multiple independent consumers must each process the same logical incident is a common distractor. Operational check: publish a test incident with category=housing and verify only the housing subscription receives it, confirm public-works filter rules exclude it, and watch subscription metrics for active message counts rather than relying on workers to discard noise.