Use a semantic link in a notebook to dynamically execute and monitor a semantic model refresh
Monitor Fabric items
AnswerCorrect answer: D — A semantic link in a notebook lets you programmatically execute and monitor a semantic model refresh; the Monitoring hub only monitors and cannot trigger it.
You have a Fabric workspace that contains a semantic model named Model1. You need to dynamically execute and monitor the refresh progress of Model1. What should you use?
dynamic management views in Microsoft SQL Server Management Studio (SSMS)
57% of anonymous learners picked answer D.
Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The Monitoring hub observes refreshes but does not execute them; only a semantic link in a notebook lets you dynamically execute and monitor a refresh in one automated flow.
To both programmatically trigger and monitor the refresh progress of a semantic model in Fabric, use a semantic link (SemPy) inside a notebook, which lets you call the refresh and poll its status dynamically through code.
Choosing the Monitoring hub, which monitors refresh status but cannot dynamically trigger a refresh, so it does not satisfy the 'execute' part of the requirement.
Community Discussion (7 comments)
GHill1982👍 9Selected: D
If the definition of "dynamic" is the ability to execute and monitor in real-time, a semantic link in a notebook could be more suitable than the monitoring hub.
d98a23f👍 1Selected: B
i think that both of B or D allow to achive this monitoriung refresh of model 1, however, it was specified that oui need to have the refresh progress (refresh status) and not historical duration for instance. therefore, Monitor hub is the suitable way to see it.
prabhjot👍 2Selected: B
I think Monitor Hub- A semantic link to a notebook would not be the best option for dynamically executing and monitoring the refresh progress of Model1 because notebooks are typically used for interactive data exploration and analysis. While you can write custom scripts and queries within a notebook to interact with your data, it does not provide the built-in monitoring capabilities that the Monitoring hub offers. The Monitoring hub is specifically designed to centralize and streamline the monitoring process, giving you real-time insights into the health and status of your refresh operations.
toniteo👍 2Selected: D
D is correct. Question partly says "dynamically execute" refresh, which is clearly illustrated below in way #4: https://www.kevinrchant.com/2025/01/28/four-ways-to-monitor-a-semantic-model-refresh-in-microsoft-fabric/
henryphchan👍 4Selected: B
I think Monitor Hub is correct because you need to monitor the refresh progress. The Symantic link is designed to provide a reference or connection to your semantic model in a notebook context
MultiCloudIronMan👍 3Selected: B
Therefore, the correct answer is B. Monitoring hub. This tool allows you to dynamically monitor the progress of refresh operations and manage other activities related to your semantic model.
Tuki93👍 2Selected: D
I think provided answer is correct: a semantic link in a notebook
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Log in to comment, report an error, or add a note about this question.
Expert Analysis
Why the Answer Is Correct
The requirement is to 'dynamically execute and monitor the refresh progress' of a semantic model. A semantic link in a notebook (SemPy) enables programmatic control: you can start a refresh via the Fabric REST API from Python and then poll its progress, satisfying both execution and monitoring dynamically. The Monitoring hub only displays refresh history and status and does not trigger refreshes.
Why the Other Options Are Wrong
Option B (Monitoring hub) monitors refresh status but cannot execute a refresh, so it misses the 'execute' requirement. Options A and C (dynamic management views in SSMS or Azure Data Studio) are read-only diagnostic views and likewise cannot trigger or dynamically drive a refresh.
Community Comment Notes
The community was split (D 57 vs B 43). The top comment (GHill1982, 9 likes) argues that the ability to 'dynamically execute' favors a semantic link in a notebook, while several others default to Monitoring hub for monitoring alone.