Several Microsoft Fabric ingestion pipelines and notebooks in a workspace began running noticeably slower and some operations were delayed during a busy afternoon. The engineer suspects the shared capacity was overloaded and wants to confirm whether compute demand exceeded the capacity and triggered throttling at that time. Which tool gives the clearest evidence?
- AThe Monitoring hub run list, filtered to the afternoon, showing each pipeline and notebook run's status and duration for the period in question.
- BThe refresh history of each affected item, which records the start and end time of every run so the engineer can confirm the capacity was throttling that afternoon.
- CThe Spark UI for one slow notebook, whose stage timeline shows the cluster was overloaded and therefore confirms the whole capacity was throttling that afternoon.
- DThe Microsoft Fabric Capacity Metrics app, whose utilisation and throttling views show whether compute demand exceeded the capacity and caused throttling during that window. Correct
Why A is wrong: The run list shows individual run status and duration but not whether the capacity itself was overloaded or throttling, so it shows the symptom rather than confirming the capacity cause.
Why B is wrong: Per-item refresh history gives run timings but no capacity utilisation or throttling signal, so it cannot confirm that compute demand exceeded the capacity during the slowdown.
Why C is wrong: The Spark UI explains one application's internal stages but reflects a single job, not the shared capacity's utilisation, so it cannot establish that the capacity as a whole exceeded its limit and throttled.
Why D is correct: The Capacity Metrics app charts capacity utilisation, overload, and throttling over time, so it is the tool that confirms whether afternoon demand exceeded the capacity and slowed the items.