Add an eventhouse to the Dev/Test/Prod deployment through the deployment pipeline

DP-700 By islever Editorial Last updated

Implement lifecycle management in Fabric

Short answer

B The eventhouse is added directly to the existing deployment pipeline, the built-in Fabric mechanism that deploys items across Dev, Test, and Prod.

Question

You have a Fabric deployment pipeline that uses three workspaces named Dev, Test, and Prod. You need to deploy an eventhouse as part of the deployment process. What should you use to add the eventhouse to the deployment process?
  1. GitHub Actions
  2. a deployment pipeline Correct Answer
  3. an Azure DevOps pipeline

Key Takeaways

Deployment pipelines support eventhouses as deployable items; when a pipeline already exists, the eventhouse is assigned to a stage in that pipeline rather than deployed through an external CI system.

The eventhouse is added to the existing Fabric deployment pipeline: deployment pipelines are the built-in CI/CD mechanism that publishes supported items such as eventhouses across the Dev, Test, and Prod workspaces.

Common mistake: Reaching for GitHub Actions or an Azure DevOps pipeline because the company has Azure DevOps; the question asks how to add the eventhouse to the existing deployment process, which is the Fabric deployment pipeline.

Expert Analysis

Why the Answer Is Correct

Deployment pipelines in Fabric are the built-in mechanism for copying items between Dev, Test, and Prod workspaces, and eventhouses are among the supported deployable items. To include the eventhouse in the deployment process you add it to the deployment pipeline and deploy it through its stages, reusing the pipeline the team already uses.

Why the Other Options Are Wrong

Option A (GitHub Actions) and Option C (an Azure DevOps pipeline) are external CI/CD tools that could deploy Fabric content through APIs or Git integration, but the scenario already uses a Fabric deployment pipeline, and the question asks how to add the eventhouse to that deployment process, not to introduce a new toolchain.

Community Comment Notes

The community strongly favors B (88). QAZdbarhate12345678 (5 likes) notes deployment pipelines are the recommended built-in method for deploying artifacts like eventhouses across environments, and Tuki93 links the get-started and deployment-process documentation. hebertorosillo's dissent for C relies on the company already having DevOps, but the pipeline in the scenario is already a Fabric deployment pipeline.

Official Reference

https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/get-started-with-deployment-pipelines

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

Community Votes

B
100%

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

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

  1. QAZdbarhate12345678 👍 5 Answered B
    In Microsoft Fabric, deployment pipelines are the recommended and built-in method for managing and deploying artifacts (like eventhouses, lakehouses, datasets, and reports) across environments such as Dev, Test, and Prod.
  2. Tuki93 👍 2 Answered B
    https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/get-started-with-deployment-pipelines?tabs=from-fabric%2Cnew%2Cstage-settings-new https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/understand-the-deployment-process?tabs=new
  3. hebertorosillo 👍 1 Answered C
    This is a use case question. The company Contoso already has DevOps.for my is letter C.

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