A governance team wants a workflow that starts whenever a resource is created or deleted anywhere in a subscription, and also fans out one custom business event to three separate handler services, each retried on failure. Which combination of services should you use?
Show answer and explanation
Answer: B
Event Grid system topics publish Azure resource events, such as creation or deletion, for a subscription. A custom topic receives application events, and each event subscription routes matching events to a handler with retry delivery. Combining the two gives reactive routing to several subscribers. Event Hubs is built for high-volume streaming, and consumer groups read the stream, so it is not a fan-out router for discrete events. Service Bus topics are a messaging service for enterprise queues, not a native source of Azure resource events. Notification Hubs sends push notifications to devices.
Why the other options are wrong
- A. Event Hubs is designed for streaming telemetry at scale, not discrete resource events, and Notification Hubs only pushes notifications to devices.
- C. Service Bus topics do not receive Azure resource events natively, and Event Hubs consumer groups are for streaming reads rather than per-handler event routing.
- D. Notification Hubs sends device push messages, and polling with Logic Apps adds latency and does not provide the built-in event delivery the requirement describes.