Adding an Eventhouse to a Fabric Deployment Pipeline

DP-700 By islever Editorial Last updated

Short answer

B Add the eventhouse to the Fabric deployment pipeline so it maps across the Dev, Test, and Prod workspace stages.

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

It tests Fabric deployment pipeline item support, and the trap is choosing an external CI/CD system (Azure DevOps or GitHub Actions) when the pipeline already lives in Fabric.

This DP-700 question tests how a Microsoft Fabric eventhouse joins a three-stage Dev, Test, and Prod deployment. The answer is B: configure the eventhouse inside the Fabric deployment pipeline's stage settings.

Common mistake: Option C (Azure DevOps pipeline) is the plausible wrong pick: it looks like a real CI/CD answer, but the question is about adding an item to an existing Fabric deployment pipeline, not about automating from a repository.

Expert Analysis

The scenario already names the tool. The question states you have a Fabric deployment pipeline spanning three workspaces — Dev, Test, and Prod — and asks what you use to add an eventhouse to that deployment process. That is a configuration step inside the Fabric deployment pipeline itself: you select the stage, open the items list, and add the eventhouse to the deployment process so it is assigned to each stage and copied when the pipeline runs. Eventhouse is a supported item type alongside lakehouses, notebooks, data pipelines, semantic models, and reports, so option B is the correct choice.

Why A and C are traps. GitHub Actions and Azure DevOps are external CI/CD systems. They are relevant when you drive deployments through the deployment pipeline REST APIs or Git integration from a repository, but they are not how an item is added to a Fabric deployment pipeline that already exists. One comment argues for Azure DevOps because the company "already has DevOps," and another notes these options are external repositories that do not themselves move items between workspaces. The question's own wording — "a Fabric deployment pipeline that uses three workspaces" — overrides that scenario-flavoured reasoning.

What would flip the answer. If the question asked how to trigger deployments automatically from source control, or to deploy outside Fabric using APIs and service principals, then Azure DevOps or GitHub Actions would become correct. Likewise, if the item were not deployed pipeline-to-pipeline but needed migration between unrelated workspaces, you would use a different mechanism. The decisive pivot here is that the process in question is already a Fabric deployment pipeline.

Operational consequence. Failing to add the eventhouse means the item never gets a stage assignment: it is missing from Test and Prod after a run, queries break in higher environments, and you must deploy it manually — the exact drift deployment pipelines exist to prevent. During the exam, treat "add to deployment process" and "stage settings" as Fabric deployment pipeline vocabulary, not DevOps vocabulary.

Official Reference

Exam Strategy

Read the stem for the deployment mechanism it already names; when it says "Fabric deployment pipeline," the answer is almost always a Fabric-native setting, not an external CI/CD tool. Eliminate options that operate outside Fabric (GitHub Actions, Azure DevOps) unless the stem mentions repositories, APIs, or triggers. Then confirm the item type is supported by deployment pipelines before committing.

Frequently Asked Questions

Which Fabric items can a deployment pipeline deploy, including eventhouses?

Deployment pipelines support lakehouses, warehouses, notebooks, data pipelines, dataflows Gen2, semantic models, reports, and eventhouses, among other Fabric items. You add each item to the deployment process and map it to stages before running the pipeline.

When should I use Azure DevOps or GitHub Actions instead of a Fabric deployment pipeline?

Use them when deployments must be triggered from source control or orchestrated outside Fabric, typically by calling the deployment pipeline REST APIs with a service principal. For stage-to-stage promotion inside Fabric, the built-in deployment pipeline is the answer.

What happens if I forget to add the eventhouse to the deployment process?

The eventhouse gets no stage assignment, so it is absent from Test and Prod after each run and must be deployed by hand. That creates environment drift and broken queries in higher stages.

More DP-700 FAQ →

Community Votes

B
80%
C
20%

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

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

  1. QAZdbarhate12345678 👍 17 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. Wipag 👍 7 Answered B
    Microsoft Fabric deployment pipelines now support eventhouses along with other Fabric items like: • Lakehouses • Warehouses • Notebooks • Dataflows Gen2 • Data pipelines • Semantic models • Reports • Eventhouses
  3. alirana3 👍 2 Answered B
    B. a deployment pipeline Here’s why: Microsoft Fabric deployment pipelines are designed for managing the deployment of resources (including eventhouses) across different environments (e.g., Dev, Test, Prod). You use a deployment pipeline to automate and control the deployment process across workspaces, ensuring that the eventhouse (along with other resources) is deployed correctly through the stages of your workflow. GitHub Actions and Azure DevOps pipelines could also be used for deployment, but the Fabric deployment pipeline is specifically built for this use case within Microsoft Fabric and integrates directly with the workspace and stage management. For details, check the official documentation: Get started with deployment pipelines https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/get-started-with-deployment-pipelines?tabs=from-fabric%2Cnew-ui
  4. 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
  5. hebertorosillo 👍 1 Answered C
    This is a use case question. The company Contoso already has DevOps.for my is letter C.
Show 4 more comments
  1. DarioReymago 👍 1 Answered B
    B las otras opciones son repositorios externos no generan el movimiento
  2. smanzana 👍 1 Answered B
    B- deployment pipeline or event stream
  3. DasyGY 👍 1 Answered B
    deployement pipeline
  4. xDeadEnd123x 👍 1 Answered C
    deployment pipeline

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