Fabric Deployment Pipeline Folder Structure Behavior

DP-600 By islever Editorial Last updated

Short answer

C DeployPipeline1 replicates Pipeline1 at the root and Lakehouse1 within Folder1 in Workspace2.

Question

You have a Fabric tenant that contains a workspace named Workspace1. Workspace1 contains a data pipeline named Pipeline1 and a lakehouse named Lakehouse1. You perform the following actions: • Create a workspace named Workspace2. • Create a deployment pipeline named DeployPipeline1 that will deploy items from Workspace1 to Workspace2. • Add a folder named Folder1 to Workspace1. • Move Lakehouse1 to Folder1. • Run DeployPipeline1. Which structure will Workspace2 have when DeployPipeline1 is complete?
  1. \Folder1\Pipeline1
  2. \Pipeline1
  3. \Pipeline1 Correct Answer
  4. \Folder1\Lakehouse1

Key Takeaways

The exam traps candidates by focusing solely on the moved item (Lakehouse1) while ignoring that all items in the source workspace are deployed unless explicitly excluded, preserving their respective folder paths.

This question tests how Microsoft Fabric deployment pipelines handle workspace folders and item hierarchy during deployment. The correct structure includes both the root-level pipeline and the folderized lakehouse.

Common mistake: Candidates often select D, assuming only the modified or moved item (Lakehouse1 in Folder1) is deployed, failing to recognize that Pipeline1 at the root is also part of the deployment scope.

Expert Analysis

Why the Answer Is Correct

When a deployment pipeline runs, it deploys all content from the source workspace to the target workspace by default, maintaining the exact folder structure of each item. Since Pipeline1 resides at the root level of Workspace1, it is deployed to the root of Workspace2. Simultaneously, Lakehouse1 was moved into Folder1 in Workspace1; therefore, it is deployed into Folder1 in Workspace2. This results in two distinct paths: \Pipeline1 and \Folder1\Lakehouse1.

Why the Other Options Are Wrong

Option B suggests both items are at the root, which ignores the fact that Lakehouse1 was moved into a folder. Option C lists only the root pipeline, missing the folderized lakehouse. Option D lists only the folderized lakehouse, incorrectly implying that Pipeline1 is not deployed or is filtered out, which is not the default behavior for deployment pipelines.

Community Comment Notes

As HUSSAIN_ALYAFEI noted, Microsoft documentation confirms that "Folders are considered part of an item’s name," meaning the path travels with the item. aks2304 initially voted for D but later corrected to C, acknowledging that Pipeline1 remains at the root. Devoteam2025 correctly explained that the folder hierarchy is automatically applied, resulting in the mixed structure seen in C.

Official Reference

https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/understand-the-deployment-process?tabs=new-ui

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

Exam Strategy

Always account for ALL items in the source workspace when analyzing deployment pipeline questions. Do not assume only changed or moved items are deployed; check the status of every asset relative to the root and any folders.

Frequently Asked Questions

Does moving an item to a folder exclude it from deployment?

No. Moving an item changes its path, but it remains part of the workspace content. The deployment pipeline deploys all items, preserving their new folder paths.

Why is Pipeline1 still at the root in Workspace2?

Pipeline1 was never moved into a folder in Workspace1. Therefore, it stays at the root level in the target workspace after deployment.

More DP-600 FAQ →

Community Votes

C
47%
D
33%
B
20%

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

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

  1. HUSSAIN_ALYAFEI 👍 4 Answered C
    Answer: C. \Pipeline1 and \Folder1\Lakehouse1 Reference from Microsoft Documentation: https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/understand-the-deployment-process?tabs=new-ui Under the "Folders in deployment pipelines (preview)" section in the provided text: Folders representation: "Folders are considered part of an item’s name (an item name includes its full path). When an item is deployed, after its path was changed (moved from folder A to folder B, for example), then Deployment pipelines applies this change to its paired item during deployment - the paired item will be moved as well to folder B. If folder B doesn't exist in the stage we're deploying to, it's created in its workspace first."
  2. Tika989 👍 2 Answered B
    B. \Pipeline1 \Lakehouse1 Explanation: Deployment pipelines in Microsoft Fabric are used to promote items between workspaces (e.g., from Workspace1 to Workspace2). Folders are not part of the deployment pipeline process—they are a workspace-level organization feature but do not impact how items are deployed. When DeployPipeline1 runs, it will deploy Pipeline1 and Lakehouse1 to Workspace2, but Folder1 will not be replicated. Thus, Workspace2 will contain only Pipeline1 and Lakehouse1 at the root level, without Folder1.
  3. aks2304 👍 2 Answered D
    The correct answer is D. \Folder1\Lakehouse1. When you run DeployPipeline1, it will replicate the structure from Workspace1 to Workspace2. Since you moved Lakehouse1 to Folder1 before running the deployment pipeline, Workspace2 will have the following structure: Workspace2 Folder1 Lakehouse1 Pipeline1 will not be inside Folder1, so it won't be included in the structure of Workspace2 as described in the other options.
  4. Devoteam2025 👍 2 Answered C
    In Microsoft Fabric, when you deploy content from one workspace to another using a deployment pipeline, the folder structure is preserved. This means that if you have a folder named Folder1 in Workspace1 containing Lakehouse1, deploying to Workspace2 via DeployPipeline1 will replicate Folder1 and its contents in Workspace2. The folder hierarchy of the deployed items is automatically applied in the target workspace.
  5. testtaker45 👍 2 Answered D
    It just makes the most sense from the question. Like, the pipeline isn't a folder, and it goes between the workspaces. You have Folder1 added to Workspace1, and then you add Lakehouse1 in Folder1. This gives \Folder1\Lakehouse1.
Show 3 more comments
  1. aks2304 👍 1 Answered C
    When you run DeployPipeline1, it will deploy the items from Workspace1 to Workspace2, maintaining the structure as it is in Workspace1. Since Lakehouse1 was moved to Folder1 in Workspace1, it will be deployed in the same structure in Workspace2. However, Pipeline1 was not moved to Folder1, so it will remain at the root level. Therefore, the structure of Workspace2 will be: C. \Pipeline1 \Folder1\Lakehouse1
  2. Pegooli 👍 1 Answered D
    Pipeline 1 is a Fabric item, not a folder structure. The workspace structure includes only Folder 1\Lakehouse 1.
  3. lorinamuca 👍 1 Answered B
    Correct answer because both items are deployed to Workspace2 without Folder1.

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.

Submitted for moderation before publishing. Keep it helpful and respectful.

Accessing OneLake Shortcuts in Fabric Notebooks

S-grade

Direct Lake Fallback to DirectQuery with Row-Level Security

S-grade

Displaying All Rows in Power BI Python Visuals

S-grade

Which file format and shortcut location enable Fabric SQL endpoint queries?

S-grade

Practice All DP-600 Questions

Access 115 questions with complete answers and detailed explanations.

View Full DP-600 Practice Test →

← Back to DP-600 Study Guide