nerdexam
Microsoft

DP-700 · Question #25

QUESTION 27 You have two Fabric workspaces named Workspace1 and Workspace2. You have a Fabric deployment pipeline named deployPipeline1 that deploys items from Workspace1 to Workspace2…

The correct answer is D. Run deployPipeline1 without modifying the items in Workspace2. When items in a source workspace are modified and paired with items in a target workspace via a Fabric deployment pipeline, simply running the pipeline will overwrite the corresponding target items. This process inherently handles the synchronization and overwriting of modified…

Implement and manage an analytics solution

Question

QUESTION 27 You have two Fabric workspaces named Workspace1 and Workspace2. You have a Fabric deployment pipeline named deployPipeline1 that deploys items from Workspace1 to Workspace2. DeployPipeline1 contains all the items in Workspace1. You recently modified the items in Workspace1. The workspaces currently contain the items shown in the following table. Workspace Items Workspace1 Model1 Notebook1 Report1 Lakehouse1 Workspace2 Model1 Notebook2 Report1 Lakehouse2 Items in Workspace1 that have the same name as items in Workspace2 are currently paired. You need to ensure that the items in Workspace1 overwrite the corresponding items in Workspace2. The solution must minimize effort. What should you do?

Options

  • ADelete all the items in Workspace2, and then run deployPipeline1.
  • BRename each item in Workspace2 to have the same name as the items in Workspace1.
  • CBack up the items in Workspace2, and then run deployPipeline1.
  • DRun deployPipeline1 without modifying the items in Workspace2.

How the community answered

(35 responses)
  • A
    6% (2)
  • C
    3% (1)
  • D
    91% (32)

Why each option

When items in a source workspace are modified and paired with items in a target workspace via a Fabric deployment pipeline, simply running the pipeline will overwrite the corresponding target items. This process inherently handles the synchronization and overwriting of modified content.

ADelete all the items in Workspace2, and then run deployPipeline1.

Deleting all items in Workspace2 first is unnecessary effort; the deployment pipeline can handle overwriting existing paired items directly.

BRename each item in Workspace2 to have the same name as the items in Workspace1.

Renaming items in Workspace2 would break the existing pairings or create new, unmanaged items instead of overwriting the intended ones.

CBack up the items in Workspace2, and then run deployPipeline1.

Backing up items in Workspace2 is a data management practice, not a technical step required for the overwrite functionality of the deployment pipeline, and it adds effort.

DRun deployPipeline1 without modifying the items in Workspace2.Correct

Fabric deployment pipelines are designed to synchronize items between stages. When items in the source stage (Workspace1) are modified and corresponding paired items exist in the target stage (Workspace2), running the deployment pipeline automatically detects the changes and overwrites the target items, ensuring consistency with minimal manual intervention.

Concept tested: Fabric deployment pipeline item synchronization and overwriting

Source: https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/understand-deployment-pipelines#deploy-content

Topics

#Fabric Deployment Pipelines#Application Lifecycle Management (ALM)#Workspace Management#Item Deployment

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full DP-700 Practice