Leadership wants to be notified by email the moment the nightly ticketing semantic model refresh fails, rather than discovering it the next morning when the dashboard looks wrong. Which approach lets them configure that kind of automatic, condition-based notification?
Select an answer to reveal the explanation.
Short Explanation
Waiting to check the dashboard each morning is like checking the mailbox once a day for a package that needs a signature right now. A Data Activator alert is the courier that texts leadership the instant something goes wrong.
Full Explanation
Data Activator lets a condition be defined against monitored data or events, such as a semantic model refresh failing, and pairs that condition with an automatic action, like sending an email or a Teams message, which is exactly the proactive, immediate notification leadership is asking for instead of a manual daily check. Manually checking the refresh history dashboard each morning is reactive by definition; it only reveals a failure hours after it happened, which is the exact problem leadership wants solved. The Capacity Metrics app reports on capacity consumption and throttling trends; it has no daily summary feature tied to a specific item's refresh outcome and wouldn't notice a single failed refresh. Adding a comment to an item is a collaboration feature for discussion among people already looking at the item; it does not monitor anything or notify anyone automatically. Once the alert exists, it's worth confirming the notification actually reaches the right distribution list or channel, since a correctly configured trigger with the wrong recipient is a silent failure of its own.