DP-600 Maintain a Data Analytics Solution Practice Question
You are managing a Microsoft Fabric workspace integrated with Azure DevOps. You have several developers working on the same Lakehouse and Semantic Model. Which TWO actions are required to successfully resolve a merge conflict when synchronizing changes from the remote repository to the workspace?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Resolve the conflict in the Azure DevOps repository or a local Git client.
Git integration in Microsoft Fabric necessitates a clear strategy for handling conflicts that arise when multiple developers modify the same items. When the workspace and the remote branch diverge, the system cannot automatically reconcile the differences. Engineers must use external tools and specific Fabric sync commands to ensure the workspace reflects the desired state without losing critical work.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Resolve the conflict in the Azure DevOps repository or a local Git client.
Why this is correct
The Fabric web interface does not currently support line-by-line code merging for complex conflicts. Resolving the conflict in the repository ensures that the JSON or BIML definitions are syntactically correct and logically sound. Once the conflict is resolved in Git, the workspace can then be updated successfully.
- ✓
Select the 'Update all' button in the Fabric workspace after the remote conflict is resolved.
Why this is correct
After the conflict is settled in the Git provider, the workspace status will indicate that an update is available. Clicking 'Update all' pulls the reconciled version into the workspace, synchronizing the live items with the repository. This finalizes the process and restores the consistency of the environment.
- ✗
Delete the conflicting items from the workspace and re-import them.
Why it's wrong here
Deleting items is a destructive action that can break downstream dependencies and lineage. It also loses the version history associated with those specific items within the Fabric environment. This approach is inefficient and circumvents the proper Git workflow intended for collaborative development and safe maintenance of data assets.
- ✗
Use the 'Undo changes' command in the Source Control side pane.
Why it's wrong here
The 'Undo changes' command reverts local workspace modifications to match the current state of the connected branch. While this resolves the conflict status, it does so by discarding all uncommitted work in the workspace. This is not a resolution strategy but rather a complete surrender of local progress.
- ✗
Change the workspace connection to a new empty branch.
Why it's wrong here
Switching to a new branch avoids the immediate conflict but does not resolve the underlying issue in the original branch. This fragments the development process and makes it difficult to consolidate work later. It is a temporary workaround that complicates the long-term maintenance of the data analytics solution.
Visual reference
About these practice questions
This DP-600 question is part of Courseiva's 12-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
This DP-600 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-600 exam.