Deploying a restructured workspace creates Folder1, relocates Pipeline1, and deploys Lakehouse1

DP-700 By islever Editorial Last updated

Implement lifecycle management in Fabric

Short answer

A Deployment pipelines recreate Folder1 in Workspace2 with Pipeline1 inside, and Lakehouse1 is deployed to its paired target as usual.

Question

You have a Fabric workspace named Workspace1 that contains a data pipeline named Pipeline1 and a lakehouse named Lakehouse1. You have a deployment pipeline named deployPipeline1 that deploys Workspace1 to Workspace2. You restructure Workspace1 by adding a folder named Folder1 and moving Pipeline1 to Folder1. You use deployPipeline1 to deploy Workspace1 to Workspace2. What occurs to Workspace2?
  1. Folder1 is created, Pipeline1 moves to Folder1, and Lakehouse1 is deployed. Correct Answer
  2. Only Pipeline1 and Lakehouse1 are deployed.
  3. Folder1 is created, and Pipeline1 and Lakehouse1 move to Folder1.
  4. Only Folder1 is created and Pipeline1 moves to Folder1.

Key Takeaways

Deployment pipelines preserve folder organization: folders in the source workspace are created in the target stage and paired items deploy into them, while unchanged supported items like Lakehouse1 continue to deploy normally.

Deployment pipelines replicate the source workspace's folder structure in the target stage: after moving Pipeline1 into Folder1 and deploying with deployPipeline1, Workspace2 gets Folder1 containing Pipeline1, and Lakehouse1 is deployed to its paired target as usual.

Common mistake: Assuming a folder restructure blocks the deployment of other items or that folders are not supported; the pipeline creates Folder1 in Workspace2, places Pipeline1 inside, and still deploys Lakehouse1.

Expert Analysis

Why the Answer Is Correct

When content from the source stage is copied to the target stage, Fabric identifies existing content in the target and overwrites it, and deployment pipelines support folders by recreating the source folder structure in the target. After moving Pipeline1 into Folder1 and deploying, Workspace2 gets Folder1 containing Pipeline1, and Lakehouse1 - a supported, unchanged item - is deployed to its paired target as part of the same deployment.

Why the Other Options Are Wrong

Option B ignores that folder structures are supported and created in the target stage. Option C wrongly claims Lakehouse1 moves into Folder1 - only Pipeline1 was moved, and Lakehouse1 keeps its own location. Option D ignores that Lakehouse1 is still deployed as a paired item even though it did not change.

Community Comment Notes

The community favors A (80 vs 20). 8d6881f (2 likes) cites the deployment-process documentation stating Fabric identifies and overwrites existing target content, and Goye (1 like) confirms option A by testing the scenario live in Fabric.

Official Reference

https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/understand-the-deployment-process

This link opens the official vendor documentation in a new tab.

Community Votes

A
80%
D
20%

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

Discussion 4 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 4

  1. 8d6881f 👍 2 Answered A
    https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/understand-the-deployment-process?tabs=new-ui#deploy-content-from-one-stage-to-another "When content from the source stage is copied to the target stage, Fabric identifies existing content in the target stage and overwrites it. "
  2. ce6fb55 👍 1 Answered D
    Wouldn't it be D if Lakehouse1 is already in Workspace2 and wasn't changed? Usecase says, that only a restructure takes place.
  3. Goye 👍 1 Answered A
    A is correct, I tested it in fabric
  4. MultiCloudIronMan 👍 1 Answered A
    Correct

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.

A 500-million-row fact table exceeds the F32 Direct Lake guardrail, so increase the capacity to F64

S-grade

Shortcut caching supports only S3/GCS shortcuts and excludes files larger than 1 GB

S-grade

Updating warehouse tables requires at least the Contributor workspace role because Write is not shareable to a Viewer

S-grade

Run T-SQL in a KQL database only by prefixing the query with a -- comment line

S-grade

← Back to DP-700 Study Guide