Prepstellar
Get the app

DP-600 · Practice set 4 of 8

Workspace Version Control: 10 practice questions

10 questions · Untimed · Free

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.

Set 4 · Workspace Version Control · 10 questions Read the lesson

  1. Question 1 of 10

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

    1. AFabric REST or XMLA endpoints
    2. BPower BI Desktop or local project folders
    3. CAzure DevOps or GitHub repositories
    4. DDevelopment or Test workspaces
    Show the answer

    Workspace Git integration uses Azure DevOps or GitHub as the repository provider; the other choices are interfaces, environments, or authoring locations rather than supported Git providers.

    Next → 1 / 10

  2. Question 2 of 10

    Where do you begin configuring Git integration for a Fabric workspace?

    1. ASource control, then Commit changes
    2. BDeployment pipelines, then Create pipeline
    3. CWorkspace settings, then Git integration
    4. DPower BI Desktop, then Save as
    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

  3. Question 3 of 10

    What completes the initial configuration after mapping a repository, branch, and folder?

    1. AA parameter override for the workspace
    2. BA selective deployment to the next stage
    3. CA local save as a binary report file
    4. DAn initial synchronization with the repository
    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

  4. Question 4 of 10

    What does a change icon on a Git-connected workspace item indicate?

    1. AThe item cannot be stored in version control
    2. BThe item differs from its repository version
    3. CThe item exists only in a target workspace
    4. 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

  5. Question 5 of 10

    Which action records selected workspace changes in the Git repository?

    1. AChoose Update all to pull them into the workspace
    2. BReview them in Source control and commit them
    3. CDeploy them from Test into Production
    4. 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

  6. Keep the ones you got wrong

    In the app, every question you miss comes back exactly when you’re about to forget it.

    Get the app

  7. Question 6 of 10

    Which command brings newer repository changes into a connected workspace?

    1. AUpdate all
    2. BSave as project
    3. CCommit selected
    4. 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

  8. Question 7 of 10

    Which three repository selections are mapped when configuring the workspace connection?

    1. AA stage, a capacity, and a workspace
    2. BA repository, a branch, and a folder
    3. CA table, a measure, and a relationship
    4. 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

  9. Question 8 of 10

    A team wants experimental workspace changes isolated from the main line until review. What should the team do?

    1. AMap the workspace to a Production stage
    2. BRun Update all against the main branch
    3. CCommit the experiment directly to main
    4. 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

  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?

    1. ASave every workspace item as one binary project
    2. BAssign a separate Git provider to each item
    3. CConnect the entire workspace through one Git integration
    4. 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

  11. Question 10 of 10

    A collaborator has newer repository changes, while your connected workspace has no pending edits. Which action aligns the workspace to the collaborator's version?

    1. ACommit the unchanged workspace to the repository
    2. BCreate an initial sync with another provider
    3. CDeploy the current workspace to a target stage
    4. DUse Update all to pull the repository changes
    Show the answer

    The needed direction is repository to workspace, which is the Update all operation rather than a commit or a deployment.

    Next → 10 / 10

  12. 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 course Next lesson: Power BI Desktop ProjectsGet the app
Keep your progress · Get the app

The whole course, on your phone

Lessons you can read, audio you can listen to on the way to work, and practice that remembers what you got wrong.

Get the app