Microsoft DP-700 Fabric Data Engineer Practice Exam
Prepare for the Microsoft Certified: Fabric Data Engineer Associate exam (DP-700) across all three domains — implementing and managing analytics solutions, ingesting and transforming data, and monitoring and optimizing on Microsoft Fabric. Objective-mapped questions, instant feedback in Learn mode, and a full timed simulation in Exam mode, each answer linked to Microsoft Learn. Start with a 24-hour free trial.
Start 24-hour free trial →DP-700 exam at a glance
- Vendor
- Microsoft
- Exam code
- DP-700
- Certification
- Microsoft Certified: Fabric Data Engineer Associate
- Level
- Associate
- Questions
- Approximately 40–60 (multiple choice, drag-and-drop, case studies, interactive)
- Duration
- 100 minutes
- Passing score
- 700 of 1000 (scaled, not a raw percentage)
- Cost
- $165 USD (varies by region)
- Validity
- 1 year; free online renewal on Microsoft Learn
- Prerequisites
- None formally; DP-900 concepts recommended
Sources: Microsoft — Fabric Data Engineer Associate · DP-700 study guide. Note: Microsoft is updating the English version of DP-700 on July 21, 2026 — review the study guide for the latest skills before scheduling.
About the DP-700 Fabric Data Engineer certification
DP-700 earns the Microsoft Certified: Fabric Data Engineer Associate credential. It validates that you can design, implement, secure, monitor, and optimize data engineering solutions on Microsoft Fabric — the unified platform that brings data engineering, warehousing, and real-time analytics together on OneLake. You’re expected to move fluently between a Lakehouse and a Warehouse, build batch and streaming pipelines, and transform data with SQL, PySpark, and KQL. It is the Fabric-era successor to the retired DP-203 (Azure Data Engineer Associate); if you’re coming from Synapse or Databricks, budget time for Fabric-specific capabilities like OneLake Shortcuts, Mirroring, and Direct Lake.
The exam is scenario-driven rather than definition-driven: you choose the best architecture, the right ingestion tool, or the correct fix for a failing pipeline. PowerKram maps every practice question to one of Microsoft’s three current domains and links each explanation to the exact Microsoft Learn page it derives from, so a wrong answer becomes a specific page to read. For how Fabric and Azure data roles connect, see our AI & machine learning guide.
DP-700 exam domains and weights
Microsoft’s current study guide (skills measured 2026) organizes DP-700 into three domains, each carrying roughly equal weight at about 30–35%. That even split means no domain can be safely neglected. Confirm the current weights on Microsoft’s study guide, especially around the July 21, 2026 update.
Workspace configuration and capacity, security and governance (OneLake security, RLS/CLS/OLS, sensitivity labels), lifecycle and version control (deployment pipelines, Git integration), and orchestration.
Full, incremental, and streaming loading patterns; choosing among Copy Activity/Copy Job, Dataflows Gen2, and Notebooks; shortcuts and mirroring; medallion architecture; and transforming with T-SQL, PySpark, and KQL.
Monitoring Hub, Capacity Metrics App, Query Insights, DMVs, and the Spark UI; troubleshooting pipelines, dataflows, and notebooks; and performance tuning (OPTIMIZE, VACUUM, V-Order, statistics).
Source: Microsoft — DP-700 study guide (skills measured). The three domains are weighted roughly equally at 30–35% each.
Who the DP-700 exam is for
This is a hands-on associate credential for data engineers building analytics solutions on Microsoft Fabric:
- Data engineers designing and running batch and streaming pipelines on Fabric and OneLake.
- Azure Synapse and Databricks practitioners moving their skills into the Fabric platform.
- Analytics engineers and BI developers extending into ingestion, transformation, and warehouse modeling.
- Cloud and data-platform professionals adding a current, in-demand Microsoft data credential.
Within Microsoft’s data family, natural companions include DP-600 Fabric Analytics Engineer (the sibling Fabric exam), DP-900 Azure Data Fundamentals (the recommended foundation), and DP-100 Azure Data Scientist. For the roles this credential supports, see the data engineer career guide in our Career Hub.
What this DP-700 practice exam delivers
Score by domain
Every question is tagged to one of Microsoft’s three domains. Because they’re equally weighted, your report tells you exactly which third — manage, ingest, or monitor — needs the most work.
Learn mode
Immediate feedback after each question with a full explanation of why the right answer is right and the others wrong — built for the architecture and troubleshooting decisions DP-700 rewards.
Exam mode
A timed run that mirrors the 100-minute format and the 700/1000 scaled bar, so pacing across case studies and interactive items feels familiar on test day.
Source-linked explanations
Every answer links to the exact Microsoft Learn page it derives from, so you learn Delta maintenance, pipelines, and Eventstream from the docs, not just a memorized letter.
Sample DP-700 practice questions
Ten free scenario questions across the three domains, each with a full explanation and a source link to Microsoft Learn. The complete bank is available with the 24-hour trial.
A data engineering team sets up a new Fabric Lakehouse to store IoT sensor readings. Analysts will query mostly by event_date over time ranges, and the team must choose a table format and partitioning strategy.
Which table format and partitioning strategy should the team use?
- CSV files partitioned into folders by device_id
- Delta tables partitioned by event_date to enable time-range predicate pushdown
- Parquet files with no partitioning in a single flat directory
- JSON files organized into folders by hour
Show answer & explanation
Correct: B — Delta partitioned by event_date. Delta tables give ACID transactions, time travel, and efficient predicate pushdown; partitioning by event_date matches the time-range query pattern while keeping partition counts manageable.
Why not the others: CSV (A) has no columnar optimization or transactions; unpartitioned Parquet (C) forces full scans for time filters; JSON (D) is row-oriented and inefficient for columnar analytics at IoT scale.
Source: Microsoft Learn — Lakehouse and Delta tables → Further reading: PowerKram — DP-600 Fabric Analytics →A team needs to query data that lives in an external Azure Data Lake Storage Gen2 account from their Fabric Lakehouse, without physically copying the files into OneLake.
Which Fabric capability lets them access the external data in place?
- A OneLake shortcut referencing the external ADLS Gen2 location
- A scheduled Copy Activity duplicating all files into OneLake nightly
- A Power BI import model loading the files into memory
- Manually downloading and re-uploading the files each day
Show answer & explanation
Correct: A — a OneLake shortcut. Shortcuts reference data in place (in ADLS Gen2, S3, or another Lakehouse) so it appears in OneLake without being copied, avoiding duplication and keeping a single source of truth.
Why not the others: a nightly Copy Activity (B) and manual re-upload (D) both duplicate the data unnecessarily; a Power BI import model (C) loads into a semantic model, not the Lakehouse, and still copies the data.
Source: Microsoft Learn — OneLake shortcuts →Over months, a Delta table accumulates thousands of small files from frequent micro-batch ingestion, and read queries are slowing down.
Which maintenance operation should the data engineer run?
- Run OPTIMIZE to compact small files, then VACUUM to remove stale, unreferenced versions
- Delete the entire table and recreate it from source with fresh ingestion
- Convert the table from Delta to plain Parquet to drop transaction-log overhead
- Increase the Spark cluster size to brute-force the small-file reads
Show answer & explanation
Correct: A — OPTIMIZE then VACUUM. OPTIMIZE compacts many small files into fewer larger ones, and VACUUM removes files no longer referenced by the Delta log — directly addressing the small-file problem.
Why not the others: delete-and-recreate (B) loses time-travel history; converting to Parquet (C) forfeits ACID, time travel, and schema evolution; a bigger cluster (D) doesn’t fix the underlying I/O overhead.
Source: Microsoft Learn — Lakehouse table maintenance →A retailer stores three years of order history in a Delta table. A developer accidentally updates 100,000 rows with incorrect values.
How should the data engineer revert the accidental update most efficiently?
- Use Delta time travel to RESTORE the table to the version immediately before the update
- Delete the table and reimport all three years of order data from source
- Restore from a nightly backup snapshot taken twelve hours before the incident
- Manually correct each of the 100,000 rows with individual UPDATE statements
Show answer & explanation
Correct: A — Delta time travel RESTORE. Delta lets you restore to a prior version instantly, reverting the bad update without losing legitimate changes made since the last backup.
Why not the others: a twelve-hour-old backup (C) loses valid changes since the snapshot; manual correction (D) is slow and error-prone; a full reimport (B) wastes processing and may miss incremental data.
Source: Microsoft Learn — Delta history & RESTORE →A healthcare deployment must ensure only the clinical team can read patient tables while finance accesses only billing tables.
Which approach best enforces per-team data isolation in Fabric?
- Post a written policy asking users to query only their department’s tables
- Separate the data into distinct Lakehouses/workspaces governed by workspace role assignments
- Grant broad OneLake shortcut access so both teams can read all tables
- Encrypt patient tables with a clinical-only key and email the decryption key
Show answer & explanation
Correct: B. Isolating data into separate Lakehouses/workspaces with workspace roles (backed by OneLake security and item permissions) makes membership control who can read, write, or manage each set of tables.
Why not the others: broad shortcut access (C) removes isolation; emailing keys (D) isn’t a Fabric access control and is a security risk; written policy (A) is unenforceable without technical controls.
Source: Microsoft Learn — Lakehouse overview & security → Further reading: PowerKram — DP-900 Data Fundamentals →A financial reporting team builds a Fabric Data Warehouse that must track customer addresses over time with full change history for point-in-time reporting.
Which slowly changing dimension approach should the engineer implement?
- Store only the latest address and discard historical versions
- Implement SCD Type 2 with effective_date, end_date, and is_current columns to preserve history
- Keep a timestamp-only log table with no link to the customer dimension
- Overwrite the address row on each change (Type 1), losing prior values
Show answer & explanation
Correct: B — SCD Type 2. Effective/end dates plus a current flag preserve complete address history and enable point-in-time reporting at any date.
Why not the others: overwriting (D) and discarding history (A) are Type 1 behaviours that lose the past; a disconnected log table (C) breaks the star-schema reporting pattern.
Source: Microsoft Learn — Dimension tables (dimensional modeling) → Further reading: PowerKram — PL-300 Power BI Analyst →A Fabric Data Warehouse query joining a 2-billion-row fact table with a 50,000-row dimension runs slowly.
Which optimization should the engineer apply first?
- Permanently raise the warehouse capacity units to the maximum tier
- Ensure statistics exist on the join columns and review the query execution plan
- Convert the entire Data Warehouse to a Lakehouse to change the engine
- Export all data to Excel and perform the join in a pivot table
Show answer & explanation
Correct: B. Statistics help the engine pick efficient join strategies, and the execution plan reveals unnecessary scans or suboptimal join types — the right first, low-cost step.
Why not the others: maxing capacity (A) adds cost without fixing the query design; converting platforms (C) changes the engine but not the query; Excel (D) can’t handle 2 billion rows.
Source: Microsoft Learn — Statistics in Fabric Warehouse →A media company receives hourly CSV files via SFTP from an advertising partner. Files need schema validation and error handling before landing in the Lakehouse.
Which Fabric component should orchestrate this batch ingestion?
- Manual hourly file upload through the Lakehouse file-upload interface
- Power BI scheduled refresh pulling the CSVs into a semantic model
- A Data Pipeline with a Copy Activity over SFTP, followed by a validation Notebook
- Fabric Eventstream configured to capture events from the SFTP server
Show answer & explanation
Correct: C. A Data Pipeline schedules a Copy Activity from SFTP, and a downstream Notebook validates schema and handles errors programmatically — the right batch-orchestration pattern.
Why not the others: manual upload (A) doesn’t scale; Power BI refresh (B) loads a semantic model, not Lakehouse tables; Eventstream (D) is for real-time streams, not scheduled batch files.
Source: Microsoft Learn — Data Factory activities (Copy) → Further reading: PowerKram — DP-100 Azure Data Scientist →A bank must stream real-time transaction events from Azure Event Hubs into a Fabric Lakehouse for fraud detection within seconds.
Which Fabric component fits this real-time ingestion?
- A scheduled Dataflow Gen2 polling the Event Hub every minute
- A Notebook running a continuous polling loop against Event Hubs
- Power Automate with a premium Event Hubs connector, one flow per transaction
- Fabric Eventstream connected to Event Hubs with a Lakehouse destination
Show answer & explanation
Correct: D — Fabric Eventstream. Eventstream natively connects to Event Hubs and continuously streams events into a Lakehouse destination with low latency — the right tool for seconds-level fraud detection.
Why not the others: minute-interval Dataflow (A) is too slow; polling Notebooks (B) waste compute; Power Automate (C) isn’t built for high-throughput, low-latency streams.
Source: Microsoft Learn — Eventstream: add Event Hubs source →Nightly Spark jobs in Fabric take progressively longer each week, and the team needs to find the bottleneck.
Which monitoring approach should the team use?
- Review the Spark monitoring UI for stage-level metrics, shuffle sizes, and skew
- Ask users to reduce the number and frequency of their scheduled queries
- Check the Azure billing dashboard for unexpected cost increases
- Restart the Fabric capacity and see whether performance improves
Show answer & explanation
Correct: A. The Spark monitoring UI surfaces stage durations, shuffle read/write volumes, and task distribution — revealing skew, inefficient joins, or excessive shuffling behind progressive slowdowns.
Why not the others: billing dashboards (C) show cost, not pipeline diagnostics; restarting capacity (D) doesn’t fix design issues; reducing queries (B) masks the cause rather than finding it.
Source: Microsoft Learn — Spark monitoring overview → Further reading: PowerKram — DP-600 Fabric Analytics →Keep going: study guides and career paths
Microsoft Fabric is the center of gravity for the modern Microsoft data stack, and DP-700 is its flagship data-engineering credential. Two PowerKram hubs back this exam.
Deep dive: exam format, the July 2026 update, and a study plan
Format and how it’s scored
DP-700 is roughly 40–60 questions in 100 minutes, including multiple choice, drag-and-drop, case studies, and interactive scenarios. Scoring is scaled: you need 700 of 1000, not a fixed percentage, so broad coverage across all three domains beats trying to hit a raw question count. It costs $165, is proctored (online or test center), and, like other role-based exams, gives you limited split-screen access to Microsoft Learn during the test — use it sparingly. The credential is valid for one year and renews free via an online assessment on Microsoft Learn. Read the certifications guide →
The July 21, 2026 update
Microsoft is refreshing the English version of DP-700 on July 21, 2026. The overall three-domain structure is stable, but Microsoft flags updates across workspace settings, security and governance, batch and streaming ingestion/transformation, error resolution, and performance optimization. If you’re scheduling around that date, read the study guide’s “skills measured as of” line and the change table before you sit, and treat Microsoft’s page as the single source of truth for the current outline.
The DP-203 succession and what’s new
DP-700 replaced the retired DP-203 in 2025 and is built entirely around Fabric rather than Synapse. If you’re coming from a Synapse or Databricks background, the new surface area is OneLake (Shortcuts, Mirroring, Direct Lake), Fabric’s pipelines and Dataflows Gen2, Eventstream and KQL for real-time, and Fabric’s deployment pipelines and Git integration for ALM. KQL in particular is the topic most often underestimated by engineers arriving from traditional SQL backgrounds.
Realistic study plan
Read the DP-700 study guide fully and use the skills-measured list as a checklist. Build a Fabric trial workspace and create a Lakehouse, then practice each ingestion path — Copy Activity, Dataflow Gen2, and Notebooks — landing data through bronze/silver/gold. Drill Delta maintenance (OPTIMIZE, VACUUM, V-Order, time travel), warehouse modeling and statistics, and Eventstream/KQL for real-time. Use PowerKram Learn mode with the sourced links to close gaps, then finish in Exam mode across all three domains under the 100-minute clock. Data-engineering career paths →
Frequently asked questions about the DP-700 exam
What certification does DP-700 lead to?
What is the exam format and passing score?
What are the exam domains and weights?
Is DP-700 changing in 2026?
How long is the certification valid, and how do I renew?
Start your free 24-hour DP-700 practice trial
Full access to the question bank across all three domains, both study modes, and source-linked explanations. No credit card required.
Start free trial →