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

DP-700 exam topics

The DP-700 exam (Microsoft Certified: Fabric Data Engineer Associate) covers 3 domains and 23 topics. This page lists all of them with the weight of each domain, so you can see what the exam tests and where most of the marks are.

Domains and weights

DomainWeightTopics
Domain 1: Implement and manage an analytics solution30–35%7
Domain 2: Ingest and transform data30–35%8
Domain 3: Monitor and optimize an analytics solution30–35%8

Domain 1: Implement and manage an analytics solution · 30–35%

  • Configure Fabric Workspace Settings

    Workspace settings decide how every Spark job, domain assignment, shortcut read and Airflow job in a workspace behaves. You need the workspace Admin role to change the Spark settings. The exam tests which setting solves which problem.

  • Configure Version Control with Git Integration

    Fabric Git integration works at workspace level. You connect one workspace to one branch and one folder of a repository. Every supported item in the workspace is then saved to Git as source files, and the workspace's folder structure is kept.

  • Database Projects and Deployment Pipelines

    Two lifecycle tools appear in this skill. Database projects treat a warehouse schema as code that you can build and validate. Deployment pipelines move items from Development to Test to Production inside Fabric.

  • Workspace-Level and Item-Level Access Controls

    Fabric security has two planes. The control plane decides what you can do with items (workspace roles and item permissions). The data plane decides which data you can see (OneLake security roles and SQL permissions, covered in lesson 1.5). Least-privilege questions usually come down to picking the smallest grant that meets the requirement.

  • Row, Column, Object and File-Level Security, and Dynamic Data Masking

    Once someone can reach an item, these controls decide which data they see. The method depends on the engine: T-SQL security inside a warehouse or SQL analytics endpoint, or OneLake security roles for lakehouse data that every engine reads.

  • Apply Sensitivity Labels and Endorse Items

    Labels and endorsement are both governance metadata on Fabric items. They answer different questions. A sensitivity label says how confidential the content is and can protect it. An endorsement says how trustworthy it is.

  • Orchestrate Processes with Pipelines and Notebooks

    Orchestration decides what runs, in which order, when, and what happens on failure. Fabric gives you two orchestrators: pipelines (low-code control flow across many item types) and notebooks (code-first orchestration of other notebooks).

Domain 2: Ingest and transform data · 30–35%

  • Design and Implement Full and Incremental Loads

    A full load copies everything every time. An incremental load copies only what changed since the last successful run. Incremental loading is cheaper and faster, and it puts less load on the source. Full loads still make sense for small tables, or when the source can't tell you what changed.

  • Prepare Data for a Dimensional Model

    A star schema splits data into fact tables (measurable events such as sales or clicks, at one grain) and dimension tables (descriptive context such as product, customer and date). Preparing data for it means reshaping source rows, assigning keys and managing history.

  • Choose a Data Store and a Transformation Tool

    Many DP-700 questions start with a team's skills, data shape and access pattern, then ask where to store the data or what to transform it with. Every Fabric store keeps its data in OneLake. Eventhouse data is the exception: it reaches OneLake only if you turn on OneLake availability.

  • Create Shortcuts and Implement Mirroring

    Shortcuts and mirroring both bring outside data into OneLake without building an ETL process. A shortcut references data where it already lives, so nothing is copied. Mirroring continuously replicates a database into OneLake as Delta tables.

  • Ingest Data by Using Pipelines

    The pipeline Copy activity is Fabric's workhorse for moving data. It connects to dozens of sources, copies at scale, converts file formats and needs no code. Pipelines wrap it in loops, conditions, retries and alerts.

  • Transform Data with PySpark, SQL and KQL

    The exam expects you to read transformation code in three languages and choose the line that does the job. The same five tasks come up again and again: denormalize, aggregate, remove duplicates, handle missing values, handle late-arriving data.

  • Streaming Loads, Engines and Eventstreams

    Streaming data arrives continuously and has to be processed within seconds or minutes, not in nightly batches. Fabric has three streaming engines. They often work together: an eventstream ingests and routes the events, then an eventhouse (KQL) or Spark Structured Streaming processes them.

  • Spark Structured Streaming, KQL and Windowing Functions

    This skill is code-level streaming. You process a stream with Spark Structured Streaming into Delta tables, process it with KQL in an eventhouse, and group events into time windows.

Domain 3: Monitor and optimize an analytics solution · 30–35%

  • Monitor Ingestion, Transformation and Semantic Model Refresh

    Fabric offers several monitoring tools. Each answers a different question, and exam questions usually describe the question rather than name the tool.

  • Configure Alerts

    Monitoring tells you what happened when you look. Alerts tell you without being asked. Fabric has several ways to alert, from a free failure email to rules that act on live data.

  • Identify and Resolve Pipeline, Dataflow and Notebook Errors

    Troubleshooting questions describe a symptom and ask for the most likely cause or the best fix. Work through it in order: where did it fail (which activity, query or cell), what does the error say, is it transient, and is it about permission, connection, data or code?

  • Identify and Resolve Eventhouse, Eventstream and T-SQL Errors

    Real-time and SQL items fail differently from batch jobs. A stream can keep running while it silently drops events, and a T-SQL statement can fail because of a concurrency rule that doesn't exist in Spark.

  • Optimize a Lakehouse Table

    Delta tables slow down as they collect many small files, deleted rows that are still stored and old file versions. Table maintenance keeps reads fast and storage lean. Each command fixes a different problem.

  • Optimize a Pipeline and a Data Warehouse

    Pipeline tuning is mostly about parallelism and how data moves. Warehouse tuning is mostly about data types, file layout and how data is loaded.

  • Optimize Eventstreams and Eventhouses

    Real-time performance has two halves. Getting events in quickly enough is about eventstream throughput and ingestion settings. Querying them quickly enough is about eventhouse policies and KQL habits.

  • Optimize Spark and Query Performance

    Spark tuning on the exam has two parts. One is choosing the right compute and engine settings. The other is writing code that avoids the classic Spark bottlenecks: shuffles, skew, small files and bringing data to the driver.

DP-700 exam facts

QuestionsAbout 40–60
Time limit100 minutes
Passing score700 on a scale of 1–1,000
Exam fee$165 USD (varies by country)
Certification valid for12 months, renewable free online
DeliveryPearson VUE, online proctored or at a test centre. Microsoft Learn is open during the exam
RetakesAfter 24 hours the first time; longer waits for later retakes

Study these topics

Skillmarked is independent and not affiliated with Microsoft. The topic list follows the public exam outline; check the official exam page for the current version before you book.