A data engineer owns several import-mode semantic models in a Microsoft Fabric workspace. The business wants a single chat message posted to a Microsoft Teams channel within moments of any of these models completing a refresh that ends in failure, and the rule should react to the refresh event itself rather than poll on a fixed clock. The engineer wants a managed, no-code path that watches the item event and sends the Teams message. Which Microsoft Fabric capability should the engineer use to drive this notification?
- AAdd a scheduled trigger to a Data Factory pipeline that runs every five minutes, reads the refresh history, and posts to Teams when it finds a failed run.
- BTurn on the scheduled refresh failure email notification on each model and rely on a mailbox rule to forward those messages into the Microsoft Teams channel.
- CConfigure a Data Activator (Activator) rule that listens to the semantic model refresh failure event and sends a Microsoft Teams message when a failed refresh is detected. Correct
- DBuild a Spark notebook that queries the refresh history through the API on a timer and calls a Teams webhook whenever it observes a failed refresh of any model.
Why A is wrong: A scheduled pipeline can post to Teams, but it polls on a fixed clock and adds operational overhead, which the requirement to react to the event without polling rules out.
Why B is wrong: Refresh failure email is built in, but it sends email to owners rather than a Teams channel, and a forwarding rule is an external workaround outside Fabric rather than a managed event-driven path.
Why C is correct: Data Activator can watch Fabric item events such as a semantic model refresh failure and trigger a Microsoft Teams message with no code and no fixed polling interval, matching the requirement exactly.
Why D is wrong: A notebook on a timer could post to Teams, but it requires custom code and timed polling, the opposite of the managed, no-code, event-driven approach the requirement calls for.