DP-600 · Practice set 8 of 8
Workspace Version Control: 10 practice questions
10 free DP-600 practice questions on Workspace Version Control, with an explanation for every answer. Untimed. The full mock exam and the timed version are in the app.
-
Question 1 of 10
Which Git providers can a Fabric workspace connect to through Git integration?
- AAzure DevOps or GitLab repositories
- BGitLab or Bitbucket repositories
- CAzure DevOps or GitHub repositories
- DGitHub or Bitbucket repositories
Show the answer
Workspace Git integration connects to Azure DevOps or to GitHub, so both halves of the answer have to be one of those two providers.
Next → 1 / 10 -
Question 2 of 10
A Fabric workspace is not yet connected to any repository. Which entry point starts that connection?
- ASource control, then Commit changes
- BPower BI Desktop, then Save as
- CWorkspace settings, then Git integration
- DDeployment pipelines, then Create pipeline
Show the answer
The workspace connection starts in Workspace settings under Git integration; Source control is used after connection to review and commit workspace changes.
Next → 2 / 10 -
Question 3 of 10
A team has just chosen the organization, project, branch and folder for a workspace. What still has to happen before that setup is finished?
- AA parameter override for the workspace
- BA selective deployment to the next stage
- CAn initial synchronization with the repository
- DA local save as a binary report file
Show the answer
The initial sync aligns the mapped workspace and repository so later commits and updates can maintain their shared state.
Next → 3 / 10 -
Question 4 of 10
What does a change icon on a Git-connected workspace item indicate?
- AThe item cannot be stored in version control
- BThe item differs from its repository version
- CThe item exists only in a target workspace
- DThe item is identical in both pipeline stages
Show the answer
Workspace Git status distinguishes an item with repository differences from one that displays the synced status.
Next → 4 / 10 -
Question 5 of 10
Which action records selected workspace changes in the Git repository?
- AChoose Update all to pull them into the workspace
- BReview them in Source control and commit them
- CDeploy them from Test into Production
- DRun an initial sync against a different folder
Show the answer
A commit sends selected pending workspace changes, together with a descriptive message, into repository history; Update all operates in the opposite direction.
Next → 5 / 10 -
Keep the ones you got wrong
In the app, every question you miss comes back exactly when you’re about to forget it.
Opens in your browser. Nothing to install.
Start studyingOn your phone, with the same account
-
Question 6 of 10
Which command brings newer repository changes into a connected workspace?
- AUpdate all
- BSave as project
- CCommit selected
- DCreate pipeline
Show the answer
Update all synchronizes the workspace with the latest repository state, whereas committing sends workspace changes to the repository.
Next → 6 / 10 -
Question 7 of 10
Which three repository selections are mapped when configuring the workspace connection?
- AA stage, a capacity, and a workspace
- BA repository, a branch, and a folder
- CA table, a measure, and a relationship
- DA server, a database, and a parameter
Show the answer
Git integration maps the workspace to a specific repository location defined by its repository, branch, and folder.
Next → 7 / 10 -
Question 8 of 10
A team wants experimental workspace changes isolated from the main line until review. What should the team do?
- AMap the workspace to a Production stage
- BRun Update all against the main branch
- CCommit the experiment directly to main
- DSwitch the workspace to a feature branch
Show the answer
A feature branch provides an independent line of development, preserving isolation until the changes are reviewed for the main branch.
Next → 8 / 10 -
Question 9 of 10
A workspace contains reports, notebooks, a lakehouse, and a warehouse. The team wants centralized version history for the supported items. Which configuration fits?
- ASave every workspace item as one binary project
- BAssign a separate Git provider to each item
- CConnect the entire workspace through one Git integration
- DCreate a separate deployment stage for each item type
Show the answer
Workspace-level Git integration supports mixed Fabric content through a single connection, so the team does not need an item-by-item provider design.
Next → 9 / 10 -
Question 10 of 10
Several items in your connected workspace show a difference icon. The detailed status says the repository changed and the workspace did not: colleagues merged work into the branch this morning. What aligns the two?
- ACommit the differing items so the branch matches
- BReconnect the workspace and run the initial sync again
- CResolve each item as a conflict, keeping the workspace
- DUpdate all, which pulls the newer branch content in
Show the answer
The movement happened on the repository side only, so the workspace is the side that has to receive it.
Next → 10 / 10 -
You’ve finished this set
That’s 10 questions on Workspace Version Control. In the app the ones you miss come back exactly when you’re about to forget them.
Back to the courseOpens in your browser. Nothing to install.
Start studyingOn your phone, with the same account
The whole course, on your computer and your phone
Lessons you can read, audio you can listen to on the way to work, and practice that remembers what you got wrong.
Opens in your browser. Nothing to install.
Start studyingOn your phone, with the same account
“This app is the ‘One Lake’ for preparing the certification exams. Really worth it.”