Git Integration Workflow: 10 practice questions

Question 1 of 10

Which Git providers can a Fabric workspace connect to through Git integration?

1. AAzure DevOps Server and GitHub Enterprise Server on a private network
2. BWhichever Git host the team uses, if it is reachable through HTTPS
3. CAzure DevOps, GitHub, and GitHub Enterprise, in their cloud versions
4. DGitLab and Bitbucket, in their cloud versions

Question 2 of 10

A workspace that holds several items is connected to a Git branch that already contains different items. What happens at the first sync?

1. AThe person connecting has to choose which side overwrites the other.
2. BFabric merges the two sets, so the items of both sides are kept.
3. CFabric copies the workspace into the branch without asking first.
4. DThe content of the branch always replaces the workspace items.

Question 3 of 10

Which workspace role is required to connect a Fabric workspace to a Git repository?

1. AViewer or higher, since the connection is per user
2. BMember or higher, once the tenant switch is on
3. CAdmin, and no lower role can do it
4. DContributor or higher, with write on all items

Question 4 of 10

A Contributor edits a notebook in a Git-connected workspace. The Source control panel lists the notebook under Changes and two other items under Updates. There is no conflict, but Commit is disabled. Why?

1. AA commit has to include each changed item, and one is not selected.
2. BA workspace Admin is the one role that can commit, as with connecting.
3. CThe Git branch has new commits that the workspace has not pulled yet.
4. DA Contributor can update from Git but needs the Member role to commit.

Question 5 of 10

The Updates list of the Source control panel shows a pipeline, a notebook, and a lakehouse that changed in Git. A developer wants only the notebook change in the workspace for now. What does Update do?

1. AIt stays disabled until the other two changes are reverted in Git.
2. BIt brings all three items to the latest commit; items cannot be picked.
3. CIt updates the notebook and marks the other two items as Conflict.
4. DIt updates just the notebook she selects and leaves the other two pending.

Question 6 of 10

A notebook shows the status Conflict. During Update, the developer opens Resolve Conflicts and chooses Keep current content for it. What is the Git status of the notebook after the update completes?

1. AUncommitted changes, since the workspace version is not in the branch yet
2. BUpdate required, since the version from Git is still waiting to arrive
3. CConflict, since both versions of the notebook still exist side by side
4. DSynced, since the workspace version replaces the version in the branch

Question 7 of 10

A data engineer has the Contributor role, with write permission on all items, in a Git-connected workspace. From time to time she must point this same workspace at a release branch. The workspace Admin wants to remain the one person who can connect or disconnect the workspace. What should the Admin do?

1. AEnable the workspace setting that lets Contributors change the branch
2. BHave her use Branch out to another workspace on the release branch
3. CPromote her to Member, because Members can switch branches by default
4. DAsk the tenant admin to turn on branch switching across the whole tenant

Question 8 of 10

A notebook shows Conflict after a teammate commits to the connected branch. A workspace Admin made the workspace edits, is not sure which version is right, and must not lose them. Other items in the workspace also hold uncommitted work that has to stay. Which approach fits?

1. AChoose Accept incoming changes for the notebook in Resolve Conflicts
2. BDisconnect the workspace, reconnect it, and sync from the Git branch
3. CCheck out a new branch, commit there, merge in Git, then switch back
4. DUse Undo on the notebook, and then update the workspace from Git

Question 9 of 10

A team uses Git integration to bring a development workspace into a new, empty workspace. The source holds a lakehouse with Delta tables and shortcuts, and a PySpark notebook that reads those tables. The notebook must run in the new workspace right after the sync. What should the team plan for?

1. ARebuilding the shortcuts by hand, because Git skips shortcut definitions
2. BLoading the table data again, because Git carries just lakehouse metadata
3. CCommitting the notebook as an .ipynb file so that its code gets tracked
4. DTurning on table tracking in the lakehouse settings to version the tables

Question 10 of 10

A team connects a new, empty workspace to a GitHub branch. The connected folder holds 1,300 small items, in folders two levels deep. The first sync into the workspace fails. What should the team do?

1. AMove the repository to Azure DevOps and sync with a user account
2. BSplit the items across workspaces on different branches
3. CAsk the tenant admin to enable cross-geo export for GitHub
4. DBreak the first sync into several commits of less than 50 MB each