Merging a Fabric feature branch back into Workspace1

DP-700 By islever Editorial Last updated

Short answer

A Merge the feature branch into the main branch, then sync Workspace1 so Warehouse1 gains the stored procedure and the table.

Question

You have a Fabric workspace named Workspace1 that contains a warehouse named Warehouse1. Warehouse1 is integrated with a Git repository. Each branch in the repository is linked to a separate workspace in Fabric.
You perform the following actions:
• To Warehouse1, add a new table that is linked to the main branch and commit the change to source control.
• Create a new branch from the main branch, which also creates a second workspace named Workspace2.
• To Workspace2, add a stored procedure to Warehouse1 and commit the change to source control.
You need to ensure both the new table and the stored procedure are available in Workspace1. The solution must ensure that all performed commits are documented in the commit history of the main branch.
What should you do?
  1. Merge the feature branch into the main branch. Sync Workspace1 with the merged branch. Correct Answer
  2. Merge the branches. Add a stored procedure to Warehouse1. Commit the change to source control. Sync Workspace1.
  3. Merge the branches. Clone the repository locally. Add a stored procedure to Warehouse1. Commit and push the change. Sync Workspace1.
  4. Add a stored procedure to the main branch of Workspace1 and commit the change to source control. Merge the branches. Sync Workspace1 with the updated branch.

Key Takeaways

The test is the merge-then-sync pattern across branch-linked workspaces; the trap is re-creating a stored procedure that already exists as a commit on the feature branch.

This DP-700 scenario tests Git branch handling in Microsoft Fabric: merging the feature branch into main and then syncing Workspace1 (answer A) makes both the new table and the stored procedure available in Warehouse1.

Common mistake: Option D — adding the stored procedure again on the main branch before merging — reaches a similar end state but duplicates an object already committed on the feature branch, causing a conflicting version of the same procedure during the merge.

Expert Analysis

Why A is correct The stored procedure was created and committed on the feature branch, which Fabric materialized as the separate Workspace2. Because each branch maps to its own workspace, Workspace1 — which is bound to the main branch — cannot see that commit until the branch is merged into main. Merging the feature branch into main places the stored procedure into main's commit history, and a subsequent sync of Workspace1 applies both changes to Warehouse1: the table that was already committed on main and the stored procedure that arrives by merge. One merge, one sync, no duplicate authoring.

The attractive trap: Option D Option D looks like the most thorough answer: it writes the stored procedure directly into Workspace1, commits it to source control, and then merges. It does reach an end state where both objects exist and commits land on main. But the stored procedure already exists as a commit on the feature branch, so authoring it again on main means the same database object is created twice, and the later merge brings a second, conflicting definition of that same procedure — the merge fails or silently overwrites the branch version. It also throws away the branch-isolated workflow the scenario deliberately set up: Workspace2 exists so that changes are developed on the branch and delivered by merge.

Why B and C fail Both start correctly with the merge, but then re-add the stored procedure — which, after the merge, is already present in main — so the extra commit duplicates an existing object. Option C compounds this by cloning the repository locally and pushing manually, bypassing the workspace-to-Git sync behavior this question is testing while still re-creating the same procedure.

The rule Feature-branch change plus a main-only change equals: merge the branch, then sync the main-bound workspace.

Exam Strategy

In Fabric Git questions, first identify which branch each change was committed to, then remember the canonical delivery path: merge the feature branch into main, then sync the workspace bound to main. Immediately discount any option that re-creates an object the scenario already says was committed elsewhere — duplication is the giveaway. Also discount options that clone and push manually, since workspace-level sync is the behavior being tested.

Frequently Asked Questions

Why does syncing Workspace1 alone not bring in the stored procedure?

Workspace1 is bound to the main branch, and the stored procedure was committed only on the feature branch. Until the feature branch is merged into main, a sync has nothing new to apply from source control.

Why not just add the stored procedure directly to the main branch?

That duplicates an object already committed on the feature branch, so the later merge produces a conflicting definition of the same procedure. Merging the branch delivers the existing commit instead.

More DP-700 FAQ →

Community Votes

A
100%

100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 1 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 1

  1. nahida 👍 1 Answered A
    The important concept: When multiple Fabric workspaces are connected to different Git branches, use Merge → Sync to bring feature-branch changes into the main workspace.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

← Back to DP-700 Study Guide