DP-600 study scenarios: three profiles
To study for DP-600 well, match your background to the outline’s three domains: Prepare data is 45 to 50%, while Maintain a data analytics solution and Implement and manage semantic models are 25 to 30% each. The exam runs 100 minutes with a passing score of 700 on a 1 to 1000 scale, and the English outline changes on October 19, 2026.
Example profiles, not real people. The profiles below are illustrative planning examples built from the official exam outline. They are not reviews or reports of anyone’s result.
Budgets start from the site’s four-week study plan, which assumes 8 to 10 hours a week, roughly 32 to 40 hours, and a Fabric workspace for hands-on practice. Hour counts are planning assumptions, not guarantees.
Profile one: the Power BI report author stepping into Fabric
Starting point. This candidate builds reports and models in Power BI, writes measures with CALCULATE and variables, and knows relationships. Much of the semantic models domain is familiar. Lakehouses, T-SQL transforms and KQL are not.
Where the time goes. Prepare data (45 to 50%): getting data, choosing between a lakehouse, warehouse and eventhouse, and writing views and stored procedures. Governance and deployment pipelines in Maintain (25 to 30%) are the second gap.
The trap. Spending most of the hours on DAX because it is comfortable. The semantic model domain has newer objectives such as Direct Lake on OneLake versus the SQL analytics endpoint, fallback and calculation groups, but it is only about a quarter of the marks.
Suggested order. Weeks one and two of the study plan first, then a focused semantic model pass on the newer features, then governance.
Time budget. A reasonable planning assumption is 16 to 18 hours on Prepare data, 8 on semantic models, and 8 on maintain and practice.
Profile two: the data warehouse developer with strong T-SQL
Starting point. This candidate writes views, functions, stored procedures and star schemas without notes, which covers the Transform data sub-area almost completely. DAX, storage modes and Power BI Desktop projects are new.
Where the time goes. Implement and manage semantic models (25 to 30%) and the lifecycle half of Maintain: Git, .pbip, deployment pipelines, impact analysis and the XMLA endpoint. KQL is the remaining query-language gap inside Prepare data.
The trap. Assuming a warehouse is the answer to every store-choice question. The outline asks you to choose between data stores, and a scenario may point to a lakehouse or an eventhouse.
Suggested order. Semantic models and DAX first, then Direct Lake, then governance and lifecycle, then KQL.
Time budget. A reasonable planning assumption is 14 hours on semantic models, 8 on maintain objectives, 6 on KQL and store choice, and 6 on practice.
Profile three: the Spark data engineer from a Fabric or lakehouse project
Starting point. This candidate ingests and transforms data with notebooks and pipelines, understands lakehouses and may have used Dataflows Gen2. Getting and transforming data is comfortable.
Where the time goes. The analytics side of the role: DAX, semantic model design, security at row, column, object and file level, sensitivity labels and endorsement. The DP-600 vs DP-700 page explains why ingestion depth is mostly outside this exam.
The trap. Preparing as if for the data engineer exam. DP-600 touches ingestion lightly, and the marks are in modelling for consumption and in governance facts.
Suggested order. Semantic models, then security and governance, then lifecycle, then a gap check on SQL and KQL.
Time budget. A reasonable planning assumption is 12 hours on semantic models, 10 on maintain, 6 on query gaps, and 6 on practice.
The three DP-600 profiles compared
| Profile | Front-load | Main risk |
|---|---|---|
| Power BI report author | Prepare data (45-50%), governance | Over-studying DAX |
| Warehouse developer | Semantic models, lifecycle, KQL | Defaulting to a warehouse |
| Spark data engineer | Semantic models, governance | Preparing for DP-700 instead |
How to check which DP-600 profile fits before booking
Run the prerequisites self-test and the free official practice assessment, then sort misses by domain. Take the sample questions and the practice test under 100 minutes. The exam format page explains which outline applies on your booking date, and what changed in October 2026 lists the newer objectives.
If your work leans towards reports rather than models, compare with PL-300 before committing.