DP-600 remains the exam for Microsoft Certified: Fabric Analytics Engineer Associate. As of October 4, 2026, Microsoft’s certification page states that the English exam will be updated on October 19, 2026. That means candidates testing before that date should use the current live scope measured as of July 21, 2026, while also being aware that Microsoft has already published the upcoming October 19 objectives.
The current DP-600 weighting is stable across the published versions: Maintain a data analytics solution at 25–30%, Prepare data at 45–50%, and Implement and manage semantic models at 25–30%. Microsoft currently lists 100 minutes and a U.S. price of $165, with regional pricing varying. A passing score is 700 or higher.
The role is broader than Power BI report development
Microsoft describes the candidate as someone who designs, creates, and manages analytical assets such as semantic models, warehouses, and lakehouses. Responsibilities include preparing and enriching data, securing and maintaining analytics assets, and implementing and managing semantic models.
A Fabric Analytics Engineer perspective is useful because the role sits between data engineering, analytics, modeling, and governance rather than inside one Power BI artifact.
Maintain a data analytics solution begins with security and governance
The current scope includes workspace-level and item-level access controls, row-level, column-level, object-level, and file-level security, sensitivity labels, and endorsement. This requires candidates to understand how governance applies at different layers of Fabric.
Security is not simply “who can open the workspace.” A user may need access to an item while still being restricted from specific rows, columns, objects, or files.
Development lifecycle is now a core analytics skill
The exam includes workspace version control, Power BI Desktop projects (.pbip), deployment pipelines, impact analysis of downstream dependencies, XMLA endpoint management, and reusable assets such as templates, data source files, and shared semantic models.
This reflects a mature analytics lifecycle. Enterprise Fabric work should be versioned, reviewed, deployable, and understandable across environments.
Prepare data is the largest domain at 45–50%
Data preparation includes creating connections, discovering data through OneLake catalog and Real-Time hub, ingesting or accessing data, choosing data stores, and implementing OneLake integration for Eventhouse and semantic models.
The architect or analytics engineer must understand where data lives and how it should be accessed before building transformations or models.
Transformation spans lakehouse, warehouse, and relational logic
The current objectives include views, functions, stored procedures, new columns and tables, star schemas for lakehouses or warehouses, denormalization, aggregation, joins, duplicate and null handling, type conversion, and filtering.
The Microsoft Fabric and Power BI relationship becomes important here because Fabric extends the analytical environment upstream into lakehouse and warehouse design.
SQL, KQL, DAX, and Visual Query Editor all appear in analysis
Candidates should be able to select, filter, and aggregate by using the Visual Query Editor, SQL, KQL, and DAX. The exam therefore expects conceptual fluency across several query languages and interfaces.
Use the language that fits the data and engine. The skill is not to force every problem into DAX.
Semantic-model design remains a major exam responsibility
The current scope includes storage mode, star schemas, relationships including bridge tables and many-to-many designs, DAX variables, iterators, table filtering, windowing and information functions, calculation groups, dynamic format strings, field parameters, large semantic model storage, and composite models.
A Power BI data-modeling foundation and DAX understanding remain highly relevant, but DP-600 expects enterprise-scale Fabric context around those skills.
Direct Lake is a central enterprise semantic-model topic
The optimization section includes Direct Lake configuration, default fallback and refresh behavior, choosing between Direct Lake on OneLake and Direct Lake on the SQL analytics endpoint, and incremental refresh for semantic models.
Candidates should understand when a storage mode is chosen, what fallback means, and how freshness and performance interact with the underlying Fabric data architecture.
Performance troubleshooting spans model, query, and visual layers
Microsoft expects candidates to implement performance improvements in queries and report visuals and improve DAX performance. A slow report can originate in the semantic model, DAX, underlying warehouse or lakehouse query, or visual design.
Optimization should start with evidence about which layer is responsible rather than changing model settings blindly.
October 19 is an upcoming update, not the current exam today
Microsoft’s current certification page explicitly says the English version will update on October 19, 2026. The published upcoming guide keeps the same three weighted domains but includes minor objective changes, especially around query and analysis wording.
The certification page also states that role-based certifications renew annually through a free online assessment on Microsoft Learn. That renewal model reflects the pace of Fabric development: service capabilities, storage modes, workspace lifecycle, and governance features can change materially over a year. DP-600 preparation should therefore use current documentation rather than relying only on early Fabric launch material.
The security objectives are especially broad because Fabric combines several engines and asset types. Workspace roles control collaboration, item permissions control specific assets, row-level security filters records, column-level and object-level security limit model elements, and file-level controls govern underlying data. A strong candidate knows which control applies to which layer instead of expecting one role assignment to secure everything.
Endorsement and sensitivity labels also solve different governance problems. Endorsement helps users discover trusted or recommended content; sensitivity labels communicate classification and handling expectations. Neither one replaces authorization. The exam expects analytics engineers to understand trust, classification, and access as separate but cooperating controls.
Power BI Desktop projects (.pbip) are important because they make report and semantic-model assets more compatible with source-control workflows. Instead of treating a binary report file as the only artifact, teams can use project structures that are easier to compare, review, and integrate with Git. This objective signals that Fabric analytics engineering includes software-development discipline.
Impact analysis is another enterprise-scale objective. A lakehouse table, warehouse view, dataflow, semantic model, or shared dataset can have many downstream consumers. Before changing a column, relationship, or source, engineers should understand what depends on it. The cost of an analytics change is often measured in broken downstream reports rather than failed deployment itself.
OneLake catalog and Real-Time hub place discovery before ingestion. Analytics engineers need to know what data already exists, who owns it, and whether it should be accessed in place or copied. Reusing governed data can reduce duplication, but only if the source quality, freshness, permissions, and service expectations fit the use case.
Choosing among lakehouse, warehouse, Eventhouse, and other Fabric stores is also a workload decision. SQL-centric relational analytics, open lake formats, real-time/event analytics, and semantic-model consumption have different strengths. The largest exam domain tests whether candidates can prepare data in the engine that fits the workload rather than using one store for everything.
Star-schema design appears both in data preparation and semantic modeling because grain and dimensional structure should remain coherent across layers. A warehouse can expose a clean dimensional model that the semantic layer reuses, or the semantic model can add relationships and calculations on top of curated tables. Poor grain upstream creates complexity downstream.
DAX windowing and iterator functions, calculation groups, dynamic format strings, and field parameters push DP-600 beyond introductory Power BI. Candidates should understand when business logic belongs in reusable measures, how calculation patterns can be centralized, and how advanced model features affect maintainability and performance at enterprise scale.
When Microsoft switches the English exam to the October 19 objectives, candidates should use the version that matches their scheduled date. The currently published change log characterizes the changes as limited rather than a wholesale redesign, but a two-week difference around an exam update can still matter. Date-aware preparation is part of responsible certification planning.
Power BI template (.pbit) and data-source (.pbids) files are also in the lifecycle scope because enterprise analytics benefits from reusable starting points and consistent connection definitions. Reuse can reduce duplicated configuration, but templates should not become stale copies of business logic. Shared semantic models are often the stronger place for authoritative measures and security.
Workspace version control creates another responsibility: not every Fabric asset behaves like application source code. Teams should understand what can be synchronized, how deployment stages differ, how secrets or environment-specific settings are managed, and how to recover from an unintended change. The objective is controlled lifecycle, not simply “connect Git.”
SQL, KQL, and DAX should be compared by execution context. SQL can shape relational or warehouse data close to storage, KQL is optimized for event and telemetry-style analytics, and DAX operates over semantic models under filter context. Pushing logic into the wrong layer can create duplicated definitions or poor performance even when the result is technically correct.
Direct Lake fallback deserves particular attention because it changes how queries may be served when the ideal Direct Lake path cannot be used. Candidates should understand the conditions and performance implications at a conceptual level and know that storage mode is an operational behavior, not only a model property selected once during development.
Field parameters and dynamic format strings are examples of model features that improve report flexibility without duplicating entire report pages or measures. Calculation groups can centralize repeated calculation patterns. These tools are powerful in enterprise models, but they also increase model sophistication, so naming, documentation, and governance matter.
Incremental refresh connects semantic-model scale to data-change patterns. If only recent partitions change, reprocessing all historical data wastes time and capacity. The candidate should understand when incremental processing is appropriate and how the underlying data source and refresh policy support it.
Within the broader Microsoft certification ecosystem, the safest rule is date-aware preparation: use the live July 21 scope if your exam is before October 19 and switch to the upcoming objective list for exams on or after the update date.