An analytics engineer must rename a column in a certified "semantic model" that is published to a "Microsoft Fabric" workspace. Several reports and other semantic models consume it, and the change must not silently break consumers. Before editing the model, which built-in capability identifies every downstream item that would be affected by the rename?
- AOpen the workspace settings pane and review the Microsoft Entra access list to see which users currently hold build permission on the semantic model.
- BRun a scheduled refresh of the semantic model and inspect the refresh history log, treating any failed refresh as the list of items broken by the rename.
- CUse the impact analysis view from the semantic model's lineage to list the downstream reports and dependent models the column change would affect. Correct
- DExport the semantic model definition to a "Power BI template" file and diff it against the previous template to find which fields downstream reports reference.
Why A is wrong: Access permissions show who may read the model, not which reports or models consume the column, so they do not reveal the downstream items a rename would break.
Why B is wrong: Refresh history reports load outcomes for this one model and runs only after a change, so it cannot proactively enumerate the downstream consumers before you edit.
Why C is correct: Impact analysis traces the lineage of a semantic model to enumerate the reports and dependent items downstream, which is exactly the proactive consumer list the rename requires.
Why D is wrong: A template captures one model's structure without data, but it holds no record of which external reports bind to the column, so diffing it cannot list downstream consumers.