All 35 lessons
Start here: cloud, data, Fabric and Power BI 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. Power BI in plain words: semantic models, reports and DAX
Prepare data: get data in (exam area 2, 45-50%)
- 6. Connect to data and find it: connections, gateways, OneLake catalog and Real-Time hub
- 7. Choosing a data store: lakehouse, warehouse or eventhouse
- 8. Use data without copying: shortcuts, mirroring and OneLake integration
- 9. Ingest data: Dataflow Gen2, pipelines, Copy job and notebooks
- 10. Power Query in Dataflow Gen2: filter, data types, merge and new columns
- 11. Messy data: duplicates, missing values and nulls
Prepare data: transform and query (exam area 2)
Design and build semantic models (exam area 3, 25-30%)
- 18. Choose a storage mode: Import, DirectQuery, Direct Lake and Dual
- 19. Relationships: star schemas, bridge tables and many-to-many
- 20. DAX foundations: measures, filter context, CALCULATE and variables
- 21. DAX functions the exam tests: iterators, table filters, windows and information functions
- 22. Calculation groups, dynamic format strings and field parameters
- 23. Composite models and large semantic model storage format
Optimize models, then secure them (exam areas 3 and 1)
- 24. Direct Lake in depth: fallback, refresh and the two flavors
- 25. Incremental refresh for semantic models
- 26. Faster reports and DAX: finding and fixing slow queries
- 27. Who can see what: workspace roles and item permissions
- 28. Fine-grained security: rows, columns, objects and files
- 29. Governance: sensitivity labels and endorsement
Lifecycle, then exam practice (exam area 1)
20 min
Deployment pipelines and impact analysis
Promote content through development, test and production with deployment pipelines, and check what breaks downstream before you change something.
By the end of this lesson you can
- Set up a deployment pipeline with one workspace per stage
- Say what a deployment copies, and what you must redo in each stage
- Choose a deployment rule, including for Direct Lake models
- Run an impact analysis and notify the owners of affected items
From earlier lessons · 1 of 2
A teammate merged changes into the branch your Juniper dev workspace syncs with. Which Source control action brings them into the workspace?
Pick one answer.
From earlier lessons · 2 of 2
Which file in a Power BI project holds the local copy of the model's data and is kept out of Git?
Pick one answer.
Monday, 8 a.m. at Juniper Coffee. Someone edited the Regional Sales model straight in the production workspace on Friday. The store managers' report now shows blanks. Your manager sets a rule: nothing reaches production until it passes test. And next week the data team renames a lakehouse column. Who will that break?
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. You test changes before users see them.
- A pipeline has 2 to 10 stages. The default is three: Development, Test and Production.
- Each stage is one workspace. You assign an existing workspace, or a first deployment creates one.
- To deploy is to copy items from one stage to an adjacent stage.
- Every workspace must sit on a Fabric capacity.
- One deployment carries at most 300 items.
You set the number of stages and their names when you create the pipeline. Both are permanent.
Deploying: all, selected 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. Select related adds what 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 into an empty stage, and only for all items.
Pairing decides what gets overwritten. An item pairs with its twin in the next stage when you assign a workspace or first deploy it. Later deploys overwrite the paired item. It keeps its ID, URL and permissions.
You are an analytics engineer at Juniper Coffee. A finance workspace is already live and users rely on it. You need empty development and test stages built 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 and visuals. | Item URL and ID. |
| Model metadata and item relationships. | Workspace and item permissions. |
| Sensitivity labels, in some cases. | Workspace settings and app content. |
| Model role assignment (RLS members). | |
| Model refresh schedule and data source credentials. | |
| Model endorsement settings. |
On later deploys, a target model keeps its data when it can. A breaking schema change or a new data source connection needs a full refresh.
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 a sample database while prod reads the real one.
| Rule type | Items it works on |
|---|---|
| Data source rule | Semantic model, Dataflow Gen1, paginated report, mirrored database. |
| Parameter rule | Semantic model, Dataflow Gen1. |
| Default lakehouse rule | Notebook. |
Rules you must know:
- You create a rule on the target stage, never 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.
Dataflow Gen2 isn't on this list; it takes no deployment rules.
You are an analytics engineer at Juniper Coffee. You deployed a lakehouse and its Direct Lake on SQL semantic model from Test to Production. The production model still reads the Test lakehouse. You need it to read the Production lakehouse after every deployment. What should you do?
Pick one answer.
Git or deployment pipelines?
Exam depth: know it cold.
They do different jobs, and teams often use both.
| Git integration | Deployment pipeline | |
|---|---|---|
| Job | Version control: history, review, rollback. | Release: copy content between stages. |
| Works on | One workspace and one branch. | 2 to 10 workspaces in a row. |
| Changes per stage | None. | Deployment rules. |
| Who it suits | Developers merging work. | Low-code release inside Fabric. |
The common pattern: only the Dev workspace connects to Git. A deployment pipeline then moves content from Dev to Test to Prod.
Decision rule: need history or merging, use Git. Need to promote between environments, use a deployment pipeline.
Put in order
Put Juniper'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
- Test the reports in the Test stage
- Deploy from Dev to Test with the deployment pipeline
- After sign-off, 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 with a workspace | Pipeline admin, plus Contributor or higher on both workspaces. |
| Deploy to an empty stage | Pipeline admin, plus Contributor on the source. |
| 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 the pipeline but can't deploy.
You are an analytics engineer at Juniper Coffee. A release manager must deploy items from Test to Prod. Both workspaces are already assigned. Least privilege is required. What access should the release manager get?
Pick one answer.
Lineage view and impact analysis
Exam depth: know it cold.
Lineage view is a map of how items connect, such as source to lakehouse to semantic model to report. Every workspace has one. Open it from the workspace toolbar or an item's menu.
It shows:
- All items in the workspace and their links.
- Upstream items outside the workspace, one level up.
It does not show downstream items in other workspaces. Anyone with a workspace role can open it, but Viewers don't see data sources.
Impact analysis answers "what breaks if I change this?" across all workspaces. It works for lakehouses, warehouses, dataflows, semantic models and more. Open it from the item's card in lineage view, or from its details page.
The pane has:
- Child items (one step down) and All downstream items tabs, with item and workspace counts.
- Browse by item type or Browse by workspace.
- Notify contacts: emails the contact lists of every affected workspace.
You need write permission on the item. Items you can't access show as Limited access, but your message still reaches them. For a semantic model, the pane also shows report views from the last 30 days.
You are an analytics engineer at Juniper Coffee. You plan to rename a column in the Sales lakehouse. Semantic models and reports in other teams' workspaces may use it. You need to list every affected item and warn the owners before the change. What should you do?
Pick one answer.
Try it in Fabric
A trial workspace is enough. Publish a semantic model that uses a Power Query parameter, such as ServerName. You must be the workspace Admin and the model owner.
- From the Workspaces flyout, select Deployment pipelines, then Create pipeline.
- Name it Juniper release and keep the three default stages.
- Assign your workspace to the Development stage.
- Select Test and choose Development to deploy from. Tick your report, select Select related to add its model, then Deploy.
- In the Test stage, select Deployment rules and open your semantic model.
- Under Parameter rules, select Add rule, pick ServerName, and type a test value.
- Deploy from Development to Test again. The rule applies now. Set credentials and refresh the Test model.
Exam-style practice
You are an analytics engineer at Juniper Coffee. The Regional Sales model has RLS roles, one per region. In Test, each store manager sees only their region. After you deploy to a new Production stage and refresh, managers see no rows. What should you do?
Pick one answer.
You are an analytics engineer at Juniper Coffee. You want the Development stage's semantic model to read a small sample database. You try to add a data source rule in Development and can't. What should you do?
Pick one answer.
Worth keeping
- A deployment pipeline has 2-10 fixed stages, one workspace each, on Fabric capacity.
- Deployments copy metadata, never data, permissions, RLS members or refresh schedules.
- Rules swap data sources, parameters or a notebook's lakehouse on the target stage; Direct Lake needs one to rebind.
- Git versions the Dev workspace; the pipeline releases Dev to Test to Prod.
- Impact analysis crosses workspaces and notifies contacts; lineage view stays inside one.
The pipeline moves whole models, but finance wants to refresh just one partition and add a calculation group without Desktop. Next lesson: the XMLA endpoint, plus the templates, data source files and shared models that stop every team rebuilding the same thing.
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 (12)
Each fact in the lesson is marked with the number of the page it comes from.
- [6]Microsoft Learn: Study guide for Exam DP-600: Implementing Analytics Solutions Using Microsoft Fabric
- [294]Microsoft Learn: Basic concepts in Git integration
- [300]Microsoft Learn: Power BI Desktop projects
- [305]Microsoft Learn: Introduction to deployment pipelines
- [306]Microsoft Learn: The deployment pipelines process
- [307]Microsoft Learn: Deploy content using Deployment pipelines
- [308]Microsoft Learn: Create deployment rules
- [309]Microsoft Learn: Get started with deployment pipelines
- [310]Microsoft Learn: Choose the best Fabric CI/CD workflow option for you
- [311]Microsoft Learn: Lineage in Fabric
- [312]Microsoft Learn: Impact analysis
- [313]Microsoft Learn: Semantic model impact analysis