Launch Deal · 50% off 1st month ·
← DP-600 study guide

Domain 1 – Maintain a Data Analytics Solution (25–30%)

7 lessons, each ending with a practice scenario

Log in to save your progress.

  1. ✓1.1 — Plan and Configure the Analytics EnvironmentBefore building anything, an analytics engineer chooses the capacity, the tenant and workspace settings, and the gateways the solution needs. Exam questions here are usually about requirements: which SKU, which setting, which gateway.
  2. ✓1.2 — Workspace and Item Access, and Data SharingAn analytics engineer decides who can build, who can query and who can only view reports. Fabric gives you three layers: workspace roles (everything in a workspace), item permissions (one item) and data-level security (lesson 1.3).
  3. ✓1.3 — Row-, Column-, Object- and File-Level Access ControlWorkspace roles and sharing decide who can reach an item. Granular controls decide which rows, columns, tables and files they see. Where you enforce them depends on the engine people query through.
  4. ✓1.4 — Sensitivity Labels and EndorsementGovernance on DP-600 focuses on semantic models and lakehouses: how to label them so that sensitivity follows the data downstream, and how to endorse them so that people find and trust the right ones.
  5. ✓1.5 — Version Control and Power BI Desktop Projects (.pbip)Version control on DP-600 has two sides. In the service, a workspace is connected to Git. On the desktop, a report and its model are saved as a Power BI Desktop project (.pbip): plain text files that Git can track and that you can review in pull requests.
  6. ✓1.6 — Deployment Pipelines and Impact AnalysisChanges have to reach production safely. Deployment pipelines move content between stages, and impact analysis tells you who and what breaks if you change an upstream item.
  7. ✓1.7 — XMLA Endpoint and Reusable AssetsEnterprise semantic models are often managed outside Power BI Desktop, through the XMLA endpoint. Teams also save time by reusing templates, data source files and shared models instead of rebuilding them.
Domain recapQuick overview of all lessons
  • Plan the environment: capacity SKUs, admin portal settings, gateways and report themes
  • Implement security and governance: workspace and item access, data sharing, row-, column-, object- and file-level security, sensitivity labels and endorsement
  • Maintain the development lifecycle: Git integration, Power BI Desktop projects (.pbip), deployment pipelines and impact analysis
  • Manage semantic models through the XMLA endpoint, and reuse .pbit templates, .pbids files and shared semantic models
Next domain

Domain 2: Prepare data →