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
14 min
Governance: sensitivity labels and endorsement
Label sensitive items and mark trusted ones so people find the right data.
By the end of this lesson you can
- Apply a sensitivity label to a Fabric item and predict where it flows
- Choose between Promoted, Certified and Master data for an item
- Say who can apply each endorsement badge
- Find labels and badges in the OneLake catalog
From earlier lessons · 1 of 2
Support agents must see only the last four digits of a card number. Finance must see all of it. What fits best in a Warehouse?
Pick one answer.
From earlier lessons · 2 of 2
Which two objects do you create for row-level security in a Warehouse?
Pick one answer.
An auditor visits Northwind Rides. She asks which Fabric items hold customer payment data, and how anyone would know. Meanwhile the ops team has built reports on three different copies of the trips table. Nobody knows which copy to trust. Last lesson you controlled who sees what. This lesson you tell people what each item is.
Sensitivity labels: a tag that says how sensitive
Exam depth: know it cold.
A sensitivity label is a tag on an item that says how sensitive its data is, such as General or Confidential.
Labels come from Microsoft Purview Information Protection. Purview is Microsoft's compliance service. Your security team creates and publishes the labels there. Fabric only applies them.
To apply a label you need two things:
- A Power BI Pro or Premium Per User license.
- Edit permission on the item.
The label must also be published to you in Purview. If it isn't, it shows greyed out.
You apply a label in one of two places. Select the sensitivity indicator in the item's header, or open the item's settings and use the sensitivity section.
A label on its own is information. It controls access only when the security team links it to a Purview protection policy. Then the policy decides who can open the item.
Labels also travel with data in some exports. Export to Excel, PDF or PowerPoint, or download a .pbix file, and the label goes along. Export to .csv or .txt does not carry protection.
Inheritance: labels flow downstream
Exam depth: know it cold.
Inheritance means a label copies itself to items built from a labeled item. You don't label every item by hand. It happens three ways:
- On creation. A Notebook, Pipeline or shortcut created from a labeled Lakehouse gets the Lakehouse's label.
- Downstream. You change the label on a parent item. Its existing downstream items get the new label too.
- On a new connection. You connect a General Notebook to a Confidential Lakehouse. The Notebook becomes Confidential.
The tenant setting Automatically apply sensitivity labels to downstream content makes downstream inheritance fully automatic. It's on by default. When it's off, Fabric asks you to consent first.
You are a data engineer at Northwind Rides. A payments Lakehouse is labeled Confidential. Twelve downstream items inherited that label. An analyst manually set one report to General. You change the Lakehouse to Highly Confidential, with fully automated inheritance on. Which items change?
Pick one answer.
Endorsement: Promoted, Certified, Master data
Exam depth: know it cold.
Endorsement puts a badge on an item so people can find content they can trust. Endorsed items show the badge and often appear first in lists.
| Badge | What it means | Who can apply it |
|---|---|---|
| Promoted | The creator thinks it's ready to share. | Anyone with write permission on the item. |
| Certified | It meets the organization's quality bar. | Reviewers the Fabric admin authorizes. |
| Master data | It's the single source of truth, like a customer list. | Users the Fabric admin authorizes. |
The admin names certifiers in the Certification tenant setting, using security groups. Authorized users also need write permission on the item.
You can promote or certify any item except Power BI dashboards. Master data fits only items that hold data, such as a Lakehouse or semantic model.
Decision rule: self-check is Promoted, an official review is Certified, the one reference copy is Master data.
Match
Match each Northwind Rides item to the badge it should get
Pick an item on the left, then its match on the right.
Label or badge? They answer different questions
Exam depth: know it cold.
| Sensitivity label | Endorsement | |
|---|---|---|
| Answers | How sensitive is this? | Can I trust this? |
| Comes from | Microsoft Purview. | Fabric itself. |
| Spreads to other items | Yes, by inheritance. | No. |
| Can control access | Yes, with a protection policy. | No. |
An item can have both. A payments Lakehouse might be Confidential and Certified at once.
Decision rule: if the requirement is about protecting data, pick a label. If it's about helping people find the right data, pick a badge.
Where governance shows up: the OneLake catalog
Exam depth: recognize it.
The OneLake catalog is Fabric's central place to find and govern items. You open it from the navigation pane. It has three tabs: Explore, Govern and Secure.
- Explore lists the items you can access. It has an Endorsement column and a Sensitivity column, and you can filter by endorsement.
- Govern shows insights such as label coverage and the share of unlabeled items. It suggests actions to fix gaps.
Admins also reach tenant settings here: Govern > Configurations > Tenant settings. That's where certification is turned on.
Try it in Fabric
Labels appear only if your organization publishes them in Purview. Promotion works on any trial.
Apply a label
- Open a Lakehouse in your workspace.
- Select the sensitivity indicator in the item header.
- In the flyout, pick a label from Sensitivity.
Promote the item
- Open the settings of the same Lakehouse.
- Expand the endorsement section and select Promoted.
- Select Apply.
- Open the OneLake catalog and find the item. Check its Endorsement column.
Exam-style practice
You are a data engineer at Northwind Rides. Only the data governance team may mark items as meeting company quality standards. You have write permission on the trips semantic model but aren't on that team. You need the model to carry that mark. What should happen?
Pick one answer.
You are a data engineer at Northwind Rides. Several teams keep their own station lists. Leadership names one Lakehouse table as the single source of truth for station IDs. You need people to recognize it as that. Which badge fits?
Pick one answer.
You are a data engineer at Northwind Rides. A Lakehouse holds customer payment data. Every notebook and pipeline built from it must be flagged as sensitive, with the least manual effort. What should you do?
Pick one answer.
Worth keeping
- Sensitivity labels come from Microsoft Purview; you apply them to items with edit permission.
- Labels flow downstream, but never overwrite a manual label or a stricter one.
- Promoted needs write permission; Certified and Master data need an admin-authorized user.
- Labels protect data; endorsement badges help people find data they can trust.
- The OneLake catalog shows each item's label and badge in one list.
On the job
Back to the auditor at Northwind Rides. You label the payments Lakehouse Confidential. The notebooks and pipelines you build from it pick up the label. When she asks which items hold payment data, the answer is a filter in the catalog.
Next, the three trips tables. You agree with ops which one is correct. You promote it and request certification from the data office. Once it's certified, the ops team builds every new report on it. The other two copies get deleted.
Once a month, you open the Govern tab and check label coverage. Unlabeled items in the rides workspaces go on your to-do list.
Your items are secured, labeled and badged. Then at 6 a.m. the certified trips model fails to refresh, and nobody notices until the ops meeting. Next lesson: where to watch every run, and how to get alerted first.
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.
- [4]Microsoft Learn: Study Guide for Exam DP-700
- [209]Microsoft Learn: Apply sensitivity labels to Fabric items
- [210]Microsoft Learn: Information protection in Microsoft Fabric
- [211]Microsoft Learn: Sensitivity label downstream inheritance
- [212]Microsoft Learn: Sensitivity label inheritance upon update and relationship changes in Microsoft Fabric
- [213]Microsoft Learn: Endorsement overview
- [214]Microsoft Learn: Endorse Fabric and Power BI items
- [215]Microsoft Learn: Enable item certification
- [216]Microsoft Learn: Enable master data endorsement
- [217]Microsoft Learn: OneLake catalog overview
- [218]Microsoft Learn: Find and explore data in the OneLake catalog
- [219]Microsoft Learn: Govern and manage your Fabric data estate with the OneLake catalog