All 33 lessons
Start here: cloud and data basics
- 1. Start here: the exam, the plan and what you already know
- 2. Cloud in plain words: SaaS, PaaS, IaaS and where Fabric fits
- 3. Data basics: files, tables, formats and the lakehouse idea
- 4. A tour of Microsoft Fabric: OneLake, workspaces and items
- 5. The three languages: SQL, PySpark and KQL side by side
- 6. Getting data in: the map of Fabric tools
Store, ingest and transform batch data (exam area 2, 30-35%)
- 7. Choosing a data store and a transformation tool
- 8. Shortcuts and mirroring: use data without copying it
- 9. Ingest data with pipelines and Copy job
- 10. Transform with PySpark and SQL: join, denormalize, aggregate
- 11. Messy data: duplicates, missing values and late arrivals
- 12. Full and incremental loads, and loading a star schema
Orchestrate and stream (exam areas 1 and 2)
Set up and secure a Fabric solution (exam area 1, 30-35%)
- 18. Workspace settings: Spark, domains, OneLake and data workflows
- 19. Version control with Git and database projects
- 20. Deployment pipelines: development, test and production
- 21. Who can see what: workspace roles and item permissions
- 22. Fine-grained security: rows, columns, objects, files and masking
- 23. Governance: sensitivity labels and endorsement
Monitor, fix and optimize (exam area 3, 30-35%)
- 24. Monitoring hub, alerts and Activator
- 25. Fixing errors in pipelines, dataflows and notebooks
- 26. Fixing errors in Eventhouse, Eventstream and T-SQL
- 27. Optimize lakehouse tables: V-Order, OPTIMIZE, VACUUM and partitions
- 28. Optimize Spark, pipelines and warehouses
- 29. Optimize eventstreams, eventhouses and queries
Exam practice and final review
18 min
Deployment pipelines: development, test and production
Move content between stages with deployment pipelines and change settings per stage.
By the end of this lesson you can
- Set up a deployment pipeline with a workspace per stage
- Say what a deployment copies and what stays behind
- Choose a deployment rule to change settings per stage
- Combine Git and deployment pipelines in one release flow
From earlier lessons · 1 of 2
Northwind Rides wants its Fabric notebooks under version control. Which Git providers can a Fabric workspace connect to?
Pick one answer.
From earlier lessons · 2 of 2
A Member of the Northwind dev workspace tries to connect it to a Git repository and can't. Which workspace role can do this?
Pick one answer.
Monday, 8 a.m. at Northwind Rides. Someone edited the trip-cleaning notebook straight in the production workspace on Friday. It broke, and the ops team's report shows zero rides. Your manager sets a new rule. Nothing reaches production until it passes test. You need a way to move work from dev to test to prod, safely and the same way every time.
What a deployment pipeline is
Exam depth: know it cold.
A deployment pipeline is a Fabric tool that copies content from one workspace to the next, so you can test it before users see it.
- A pipeline has 2 to 10 stages. The default is three: Development, Test and Production.
- Each stage is one workspace. You assign a workspace to a stage, or let a deployment create one.
- To deploy is to copy items from a source stage to an adjacent target stage.
- Content usually moves forward. Moving it backward has limits, covered below.
- Each workspace must sit on a Fabric capacity.
You set the number of stages and their names when you create the pipeline. You can't change them later.
Deploying: full, selective and backward
Exam depth: know it cold.
You have three ways to deploy.
- Deploy all content: every item goes to the adjacent stage.
- Selective deployment: you tick only the items you want. Use Select related to add the items they depend on, such as a report's semantic model.
- Backward deployment: content goes from a later stage to an earlier one. It works only when the earlier stage is empty, and only as a full deployment.
Pairing decides what gets overwritten. An item is paired with its twin in the next stage when you assign a workspace or first deploy it. On later deploys, the source item overwrites its pair. The target item keeps its ID, URL and permissions. Items that exist only in the target are left alone.
You are a data engineer at Northwind Rides. A production workspace already exists and users rely on it. You need to build empty dev and test stages from it with the least rework. What should you do?
Pick one answer.
What moves and what stays
Exam depth: know it cold.
A deployment copies metadata, the definition of each item. It never copies data.
| Copied to the target | Not copied |
|---|---|
| Data sources and parameters. | Data in tables, files and models. |
| Report pages, visuals and dashboard tiles. | Item URL and ID. |
| Model metadata and item relationships. | Workspace and item permissions. |
| Sensitivity labels, in some cases. | Workspace settings and app content. |
| Lakehouse shortcut definitions. | Model refresh schedule and credentials. |
A Lakehouse deployed to an empty stage arrives as a new, empty Lakehouse with the same name. Its tables and files are never overwritten by a deployment.
Compare stages before you deploy
Exam depth: recognize it.
Each stage card after the first shows a compare indicator. Green means the metadata matches the previous stage. Orange means at least one item was changed, added or removed.
Open a stage to see a label on each item. Same as source means no change. Different from source items will be overwritten. Only in source items will be copied. Not in source items aren't touched. For semantic models and dataflows, the Compare button shows a line-by-line view of what will change.
Deployment rules: different settings per stage
Exam depth: know it cold.
A deployment rule swaps a setting as content lands in a stage. Dev can read sample data while prod reads the real database.
| Rule type | Items it works on |
|---|---|
| Data source rule. | Semantic model, Dataflow Gen1 (the older dataflow type), paginated report, mirrored database. |
| Parameter rule. | Semantic model, Dataflow Gen1. |
| Default lakehouse rule. | Notebook. |
Rules you must know:
- You define a rule on the target stage. You can't create rules in the development stage.
- You must own the item to create its rule.
- A rule takes effect on the next deployment to that stage.
- A data source rule can only switch to a source of the same type.
You are a data engineer at Northwind Rides. A notebook uses NR_Dev_Lakehouse as its default lakehouse. After deployment to Production, it must write to NR_Prod_Lakehouse, with no code edits in prod. What should you configure?
Pick one answer.
Git and deployment pipelines together
Exam depth: know it cold.
Git and deployment pipelines do different jobs. Git integration versions your work while you build it. Deployment pipelines release it.
The common pattern: only the Dev workspace connects to Git. From there, a deployment pipeline moves content Dev to Test to Prod. Test and Prod have no Git branch of their own.
Microsoft lists other release options that use Git for every stage. Those use per-stage branches or a tagged release with code-first tools. Pick the deployment pipeline route when the team wants a low-code release inside Fabric.
Put in order
Put Northwind's release steps in order, from a merged pull request to production
Drag, or focus an item and press Space, move with the arrow keys, then Space to drop.
- Merge the approved pull request into the branch linked to the Dev workspace
- Run tests in the Test stage
- Deploy from Dev to Test with the deployment pipeline
- After approval, deploy from Test to Prod
- Update the Dev workspace from Git
Who can deploy
Exam depth: know it cold.
Pipeline access and workspace roles are separate. A pipeline has one permission: pipeline admin. It lets you view, share, edit and delete the pipeline. It gives no access to workspace content.
| Task | What you need |
|---|---|
| Deploy to a stage that has a workspace. | Pipeline admin plus Contributor or higher on both workspaces. |
| Deploy to an empty stage. | Pipeline admin plus Contributor on the source workspace. |
| Assign a workspace to a stage. | Pipeline admin plus Admin of that workspace. |
| Create or view a rule. | Pipeline admin, Contributor on the target, and item owner. |
A pipeline admin with no workspace role can see and share the pipeline. That person can't deploy.
You are a data engineer at Northwind Rides. A release manager must deploy items from Test to Prod. Least privilege is required. Both workspaces are already assigned. What access should the release manager get?
Pick one answer.
Try it in Fabric
A free Fabric trial is enough. These steps follow the new deployment pipelines UI, which is in preview. Use a trial workspace that holds a Notebook and a Lakehouse, where you're Admin.
- From the Workspaces flyout, select Deployment pipelines.
- Select Create pipeline (or + New pipeline).
- Enter a name, such as Northwind release, and select Next.
- Keep the three default stages and select Create.
- Assign your workspace to the Development stage.
- Select the Test stage, choose Development as the source, select your items, then select Deploy. A new Test workspace is created.
- In the Test stage, select Deployment rules. Open your notebook and look at the Default lakehouse rule.
Exam-style practice
You are a data engineer at Northwind Rides. You deployed a semantic model and its report from Dev to a new, empty Test stage. The report opens in Test but shows no data. You need it to show data. What should you do first?
Pick one answer.
You are a data engineer at Northwind Rides. You want the Dev stage's semantic model to read a small sample database. You try to add a data source rule in the Development stage and can't. What should you do?
Pick one answer.
Worth keeping
- A deployment pipeline has 2-10 fixed stages, one workspace each.
- Deployments copy metadata, never data or permissions; refresh models afterwards.
- Deployment rules swap data sources, parameters or a notebook's lakehouse per stage.
- Git versions the Dev workspace; the pipeline releases Dev to Test to Prod.
- To deploy: pipeline admin plus Contributor on both workspaces.
Permissions don't travel with a deployment. A workspace created by your first deploy has one admin: you. Next lesson: who should be Admin, Member, Contributor or Viewer, and how to share one item without opening the whole workspace.
Leaderboard
Loading…
50 XP for each lesson you finish, 10 for each right answer. Names show only for learners who turn on Show me on leaderboards.
Sources for this lesson (10)
Each fact in the lesson is marked with the number of the page it comes from.
- [4]Microsoft Learn: Study Guide for Exam DP-700
- [176]Microsoft Learn: Lakehouse git integration and deployment pipelines
- [184]Microsoft Learn: Introduction to deployment pipelines
- [185]Microsoft Learn: The deployment pipelines process
- [186]Microsoft Learn: Deploy content using Deployment pipelines
- [187]Microsoft Learn: Create deployment rules
- [188]Microsoft Learn: Compare content in different deployment stages
- [189]Microsoft Learn: Get started with deployment pipelines
- [190]Microsoft Learn: Choose the best Fabric CI/CD workflow option for you
- [191]Microsoft Learn: Roles in workspaces in Microsoft Fabric