Question

Your team develops Fabric items in a workspace connected to an Azure DevOps repository's main branch. A developer needs to work on a risky refactor of several notebooks without affecting the shared workspace or other team members' ongoing changes. The team wants the developer to test the refactor in an isolated Fabric workspace before merging back. Which approach follows Microsoft's recommended lifecycle management practice?

Accepted Answer

Have the developer use the 'Branch out to another workspace' feature to create a new branch and a new workspace synced to it

Answer

Ask the developer to disconnect the shared workspace from Git, make changes, then reconnect after testing

Answer

Create a deployment pipeline and assign the developer's changes to the Test stage of the shared workspace

Answer

Have the developer commit directly to the main branch and revert the commit if the refactor fails