A data engineering team wants to place a Microsoft Fabric workspace under version control so item definitions are committed to a remote repository and changes can be reviewed in pull requests. They will use Azure Repos as the provider. When the team connects the workspace through Git integration, what does a single workspace connection bind to?
- AAn entire Azure DevOps organisation, so that every project and repository in the organisation is synchronised into the one workspace at once.
- BSeveral branches of one repository simultaneously, letting the workspace switch between any branch on each commit without reconnecting.
- COne repository, one branch, and a specific folder within that branch, so the workspace tracks exactly that location for commit and update. Correct
- DA read-only mirror of the default branch, so the workspace can pull commits but can never push its own changes back to the repository.
Why A is wrong: Tempting because an organisation contains the repositories, but Git integration connects to one repository and branch, not to a whole organisation of projects.
Why B is wrong: Multi-branch development is done by connecting separate workspaces to separate branches; one connection tracks a single branch, so this is wrong.
Why C is correct: Fabric Git integration binds a workspace to a single branch and a chosen folder in one repository, which is the unit it commits to and updates from.
Why D is wrong: The connection is two-way, allowing both commit from the workspace and update into it, so describing it as read-only is incorrect.