DP-600 Maintain a Data Analytics Solution Practice Question
Exhibit
{
"gitConfiguration": {
"branchName": "dev",
"directoryName": "/fabric_items",
"organizationName": "ContosoCorp",
"projectName": "AnalyticsMain",
"repositoryName": "FabricRepo",
"syncStatus": "Synced"
}
}Refer to the exhibit. You are reviewing the Git configuration for a Microsoft Fabric workspace. A developer reports that they cannot see their latest changes in the 'dev' branch within the workspace. Based on the exhibit, what is the most likely cause of this issue?
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
✓
The developer has committed changes to the repository but the workspace has not been updated.
When a workspace is synced with Git, the 'syncStatus' indicates the connection health, but the workspace must still be manually updated or 'pulled' to reflect changes made in the remote repository. Maintenance of a synced environment requires understanding that the 'Synced' status confirms the link is active, but individual items must be updated to match the branch's latest commit.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The workspace is connected to a repository that does not exist in the ContosoCorp organization.
Why it's wrong here
The exhibit shows a 'Synced' status, which would be impossible if the repository or organization names were invalid. If the connection were broken due to a missing repository, the sync status would display an error or a disconnected state. The configuration details provided indicate that the initial handshake and connection have been successfully established.
- ✓
The developer has committed changes to the repository but the workspace has not been updated.
Why this is correct
In Fabric Git integration, synchronization is not always automatic in both directions for every change. Even if the status is 'Synced', a user may need to click 'Update all' in the source control panel to pull the latest commits from the remote branch into the workspace. This manual step ensures developers control when their workspace environment changes.
- ✗
The 'directoryName' in the JSON configuration is incorrect and should be the root directory.
Why it's wrong here
Fabric allows users to specify a sub-directory within a repository for storing workspace items. The use of '/fabric_items' is a valid configuration choice and would not prevent changes from appearing as long as the items are correctly located in that folder. An incorrect directory would typically result in a 'Not Found' error or an empty workspace.
- ✗
The workspace is currently in a 'Read-only' state because it is connected to a Git branch.
Why it's wrong here
Connecting a workspace to a Git branch does not make it read-only. Developers can still make changes directly in the workspace and then commit those changes back to the repository. The integration is designed for bi-directional flow, allowing for both workspace-to-Git and Git-to-workspace updates to facilitate a flexible and collaborative development environment for the team.
About these practice questions
One of 12 original DP-600 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.