A hemlock-draw OrderPlaced message must reach billing, shipping, and email independently. How should Service Bus be shaped?
Select an answer to reveal the explanation.
Short Explanation
One publish, three independent readers — that is topic plus subscriptions. Billing, shipping, and email each get their own subscription copy.
Full Explanation
When a hemlock-draw OrderPlaced message must reach billing, shipping, and email independently, shape Service Bus as a topic with a dedicated subscription per team. Publishers send once to the topic; each subscription receives its own copy and can process, retry, and dead-letter without blocking sibling teams. That publish-subscribe pattern is how one business event fans out to multiple durable downstream workflows.
Using a single queue and requiring teams to delete each other's messages fails because competing consumers on one queue deliver each message to only one receiver—teams would steal work instead of each getting a copy. Storing OrderPlaced only in Cosmos DB change feed with no messaging entity fails conceptually for this exam slice: change feed is a Cosmos pattern, not a substitute for giving each team a durable Service Bus subscription. Sending one Event Hubs Capture file and hoping each team finds it fails because Capture produces lake archives for analytics, not independent transactional subscriptions for operational handlers.
Exam caveat: without subscription filters, every subscription receives every message—add SQL or correlation filters when a team should see only a subset. Operational check: publish one OrderPlaced to the topic and confirm billing, shipping, and email subscriptions each show an active message copy that can be completed independently.