You need an alert when a scheduled semantic model refresh fails. Where does this belong?
Why C is the answer
In Fabric monitoring and alert configuration
Refresh monitoring and alerts belong in Fabric monitoring. The other options are access and storage features.
In detail
- Failure alerts belong in monitoring and alert settings.
- Send alerts to a group, so one absence does not hide a failure.
Use case
An illustrative scenario, not a real incident.
A morning sales report quietly shows yesterday's numbers. An alert on refresh failure tells the owner before anyone opens it.
See it in different ways
flowchart TD
A["Monitor hub"] --> B{"Which item failed?"}
B -->|"Pipeline"| C["Activity error output"]
B -->|"Notebook"| D["Spark logs"]
B -->|"Capacity pressure"| E["Capacity Metrics app"]mindmap
root((Monitoring))
Activities
Monitor hub
Capacity
Capacity Metrics app
Warehouse
Query insights
Spark
Logs
Copy step
Run detailssequenceDiagram participant P0 as Semantic model participant P1 as Monitoring participant P2 as Data owner P0->>P1: Refresh failed P1->>P2: Alert
Key point: Alert on failed refreshes.
Why the other options are wrong
- A. In the workspace access list, by adding the owner
- Being on an access list sends no alert.
- B. In the OneLake shortcut settings for that model
- A shortcut has no alerting.
- D. In row-level security rules on the semantic model
- Row-level security is about access.