Subdomain 1.2: Maintain the analytics development lifecycle
1.You are managing a Microsoft Fabric workspace connected to an Azure DevOps Git repository. You have created a new semantic model in Power BI Desktop and saved it as a Power BI Project (.pbip). You commit and push the files to the remote branch. You need to ensure the new semantic model is visible in the Fabric workspace. What should you do?
- A.From the Workspace settings, disconnect and reconnect the Git repository.
- B.From the Source Control icon in the workspace, select 'Update from Git'.
- C.From Power BI Desktop, publish the report to the workspace.
- D.From the Deployment Pipeline, deploy the content from the Development stage.
Show answer & explanation
Correct answer: B — From the Source Control icon in the workspace, select 'Update from Git'.
- A. Disconnecting and reconnecting the Git repository is an unnecessary and disruptive action. It is not required to pick up new commits, as the workspace provides a built-in mechanism to synchronize changes from the connected branch without reconfiguring the connection.
- B. This is the correct workflow for Microsoft Fabric Git integration. Once changes are pushed to the remote branch, the workspace UI will indicate that there are incoming changes. Selecting 'Update' (or 'Update from Git') from the Source Control pane pulls the latest committed metadata into the Fabric workspace, effectively creating the new semantic model.
- C. Publishing from Power BI Desktop bypasses the Git-driven workflow. While publishing a .pbix file to the service is common, it is not the correct approach when using .pbip projects managed via Git. Relying on Desktop publishing can lead to conflicts between the service and the Git repository's source of truth.
- D. Deployment Pipelines are used to move Fabric items between different workspace environments (such as Dev, Test, and Prod). They do not serve as the mechanism to import or synchronize new content from a Git repository into the initial workspace.