Microsoft Fabric Data Engineer Associate
225 practice questions
Last reviewed: April 2026
Personal notes and resource links for your study journey
Filter by Certification
DP-700 is Microsoft's associate-level credential for data engineers building production analytics pipelines on Microsoft Fabric. It validates the ability to implement and manage analytics solutions, ingest and transform data at scale, and monitor and optimize Fabric workloads. The audience is working data engineers expanding from Synapse / Databricks / Data Factory experience onto the unified Fabric platform. Compared to DP-600, DP-700 leans heavier on engineering depth — pipelines, streaming, performance, and operations — and lighter on semantic modeling. Expect 40–60 questions in 120 minutes including code-completion drag-and-drops (PySpark, T-SQL, KQL), scenario items, and at least one case study. DP-700 went GA in September 2024; prep material continues to mature.
About 32%. Workspace and capacity management, deployment pipelines and Git integration, security (RLS / OLS, sensitivity labels, workspace roles), Fabric domains, and lifecycle management for engineering items.
Largest domain at 34%. Pipelines, dataflows Gen2, notebooks (PySpark / T-SQL / KQL), Eventstreams for streaming, shortcuts, mirroring, medallion architecture, incremental loads, and CDC patterns.
About 34%. Monitoring hub, Spark UI, query insights, capacity throttling and bursting, performance tuning across lakehouse / warehouse / KQL DB, and cost / capacity governance.
Services you'll encounter on the exam and why each one matters.
Unified SaaS analytics platform combining ingestion, data engineering, warehousing, real-time analytics, and BI on a single capacity-based pricing model.
Why it's on the exam: The umbrella service for every DP-700 question — Domain 1 (Implement and Manage an Analytics Solution) tests capacity sizing, workspace setup, and item type selection.
Single SaaS-managed data lake automatically provisioned per tenant, storing all Fabric items in open Delta-Parquet format with shortcut-based cross-workspace access.
Why it's on the exam: Domain 1 + Domain 2 tests OneLake as the storage substrate every Fabric workload reads from — expect questions on shortcuts, file vs. table semantics, and one-copy reuse.
Fabric item combining a Delta Lake table store with an unmanaged Files area, queryable via Spark, T-SQL (SQL analytics endpoint), or Direct Lake from Power BI.
Why it's on the exam: Domain 2 (Ingest and Transform Data) repeatedly tests when to land data in a Lakehouse versus a Warehouse — file/table layout, schemas, and read patterns.
Fabric T-SQL data warehouse with full ACID transactions, multi-table writes, and a separated storage/compute architecture writing Parquet to OneLake.
Why it's on the exam: Domain 1 tests Warehouse-vs-Lakehouse selection — pick Warehouse when the workload needs full T-SQL DML, multi-statement transactions, or BI-team familiarity.
Fabric ingestion workload offering Dataflows Gen2 (low-code Power Query at scale) and Pipelines (orchestrator with 200+ connectors and copy/transform activities).
Why it's on the exam: Domain 2 is dominated by Data Factory — expect questions on Dataflow Gen2 staging, pipeline activities, parameterization, and connector choice.
Workflow orchestrator within Fabric Data Factory chaining Copy, Dataflow, Notebook, Stored Procedure, and control-flow activities with scheduling and triggers.
Why it's on the exam: Domain 2 tests Pipelines as the canonical way to operationalize multi-step ingestion + transformation across Lakehouse and Warehouse targets.
Fabric workload providing managed Apache Spark notebooks, Spark Job Definitions, and Livy endpoints for large-scale data engineering against the Lakehouse.
Why it's on the exam: Domain 2 names Spark notebooks as the answer when the transformation needs Python/Scala/SQL/R code beyond what Dataflow Gen2 can express.
Fabric workload built on the Kusto engine — Eventhouse / KQL Database for storage, Eventstreams for ingestion, and Real-Time Dashboards for visualization.
Why it's on the exam: Domain 2 + Domain 3 cover streaming ingestion and sub-second querying as a first-class scenario; Real-Time Intelligence is the named Fabric answer.
Fabric-managed Spark runtime with starter pools, custom pools, native execution engine acceleration, and library management at workspace or session scope.
Why it's on the exam: Domain 3 (Monitor and Optimize) tests Spark pool sizing, session vs. high-concurrency mode, and tuning levers like the native execution engine.
Read-only query language for time-series and log data — the analytical surface of Fabric Real-Time Intelligence, Azure Data Explorer, and Azure Monitor Logs.
Why it's on the exam: Domain 2 + Domain 3 expect KQL fluency for querying Eventhouse data and writing update policies, materialized views, and continuous exports.
Open-source ACID storage layer on Parquet — the underlying table format for Fabric Lakehouse tables, Warehouse, and OneLake shortcuts.
Why it's on the exam: Domain 2 + Domain 3 reference Delta features (V-Order, Z-Ordering, OPTIMIZE, VACUUM, time travel) as the optimization knobs available to the data engineer.
Power BI semantic-model storage mode reading Delta-Parquet files directly from OneLake — no import refresh, no DirectQuery latency.
Why it's on the exam: Domain 1 questions on semantic-model design test when Direct Lake is preferable to Import or DirectQuery for Lakehouse/Warehouse-backed reporting.
Drag-and-drop streaming ingestion item that captures real-time events from Event Hubs, IoT Hub, Kafka, CDC sources and routes them to Eventhouse, Lakehouse, or custom sinks.
Why it's on the exam: Domain 2 tests Eventstream as the canonical low-code path for streaming ingestion into Fabric — contrast with custom Spark Structured Streaming code.
OneLake references to data living in ADLS Gen2, Amazon S3, Google Cloud Storage, Dataverse, or another OneLake — zero-copy access from any Fabric workload.
Why it's on the exam: Domain 1 + Domain 2 favor Shortcuts in "ingest without copying" scenarios; expect questions distinguishing shortcuts from Copy pipelines.
Centralized observability surface for pipelines, dataflows, notebooks, semantic models, and Eventstreams — recent runs, errors, durations, and re-run actions.
Why it's on the exam: Domain 3 leads with the Monitoring Hub as the first-line investigation tool when a question asks "where do you check why the run failed."
Compute purchasing unit (F2 → F2048 / P-SKUs) measured in Capacity Units that governs concurrent workload throughput, smoothing, and bursting across Fabric items.
Why it's on the exam: Domain 3 tests capacity sizing, throttling, smoothing windows, and the bursting/overload behaviour the data engineer must plan for.
Cloud identity provider authenticating Fabric users, service principals, and managed identities used by pipelines, notebooks, and Eventstream connectors.
Why it's on the exam: Domain 1 tests Entra-driven workspace roles, item-level permissions, and OAuth/service-principal auth on external connectors.
Logical container hierarchy: Domains group related Workspaces, which hold Fabric items with role assignments (Admin/Member/Contributor/Viewer) and capacity binding.
Why it's on the exam: Domain 1 expects Workspace + Domain as the access-control and organizational primitives for separating dev/test/prod and data-product ownership.
Data governance service auto-scanning Fabric workspaces for catalog metadata, lineage tracking across items, and sensitivity-label propagation.
Why it's on the exam: Domain 1 + Domain 3 cite Purview when a scenario needs end-to-end lineage from source through pipeline to Power BI report, or label-based access policies.
Managed secrets, keys, and certificate store referenced by Fabric connection credentials, customer-managed encryption keys, and notebook secrets.
Why it's on the exam: Domain 2 expects Key Vault as the answer when a question asks how to store and rotate database/Service-Principal credentials used by Fabric pipelines.
$110k–$150k–$210k USD annual
Range covers US-based mid-to-senior data engineers; Fabric-specific salary data remains sparse given the September 2024 GA, so figures lean on adjacent Azure / Databricks data-engineer roles. Senior data engineers at FAANG / fintech / large Microsoft-partner consultancies often clear $230k TC.
Source: levels.fyi 2025 data engineer / data platform engineer roles, U.S. BLS OEWS May 2024 (15-1242 database administrators, 15-1252 software developers), Glassdoor 2025. Figures are approximate; actual compensation depends on role, region, and experience.
DP-700 is the engineering-track companion to DP-600 and arrived as Microsoft Fabric adoption accelerated through late 2024 into 2026. Recruiters at Microsoft-partner consultancies, large data-platform organizations, and enterprises consolidating Synapse / Databricks investments onto Fabric have begun listing DP-700 as a preferred credential. It pairs naturally with DP-600 for engineers who span engineering and analytics work, with DP-203 (still active during the Fabric transition) for hybrid Synapse / Fabric estates, and with DP-300 for engineers crossing into DBA territory. Caveat: as a brand-new credential, JD-frequency and salary data are still maturing — expect demand to firm further through 2026.
There are no formal prerequisites. Microsoft recommends practitioner-level data-engineering experience with Synapse, Databricks, or Data Factory, plus working fluency in at least one of PySpark, T-SQL, or KQL — DP-700 is not an entry-level exam. Candidates coming from DP-203 (Azure Data Engineer Associate, still active) typically find the ingest / transform domain natural. DP-900 is a useful conceptual on-ramp for candidates new to Azure data services; DP-600 is highly complementary for engineers who want both engineering and analytics-engineer credentials.
The official Microsoft Learn path covers all three domains in roughly 35–45 hours. Hands-on time in a Fabric trial capacity (60-day free trial) is essentially required — DP-700 questions reward candidates who have actually built medallion pipelines, configured Eventstreams, and tuned Spark notebooks. Third-party material is still sparse; lean primarily on Microsoft Learn and the official practice assessment.
DP-700 sits in the Associate tier and is broadly considered one of the more challenging associate exams given the breadth of Fabric engineering surface area. Plan on 80–120 hours of study over 8–12 weeks with prior data-engineering experience; substantially longer if Spark / SQL data engineering is new. The exam runs 120 minutes — longer than most associate exams — with 40–60 questions in multiple-choice, multiple-response, drag-and-drop (including code-completion across PySpark, T-SQL, and KQL), hot-area, and case-study formats.
The most common stumbling block is the breadth across compute engines — Spark notebooks, T-SQL warehouses, KQL Eventhouses, and Eventstreams each have distinct optimization and operational considerations, and the exam expects fluency across all of them. Capacity management (CU consumption, throttling, bursting, smoothing) and the lakehouse-vs-warehouse decision are common trap areas. As a recently launched exam, third-party material varies in quality; Microsoft Learn remains the most reliable source.
Initial general availability. Beta exam ran July–September 2024 with discounted pricing. Microsoft has signaled that DP-700 will see frequent outline refreshes given the rapid pace of Microsoft Fabric feature releases.
DP-700 (Microsoft Fabric Data Engineer Associate) is a a moderately difficult exam expecting practical hands-on experience plus solid understanding of best practices Associate-level exam. Most candidates need 80–150 hours of study spread over 6–12 weeks for associate-level exams. Most candidates who score consistently above the passing threshold on practice exams pass on their first attempt.
Most candidates need 80–150 hours of study spread over 6–12 weeks for associate-level exams. Time-to-pass varies widely by prior experience. Engineers with hands-on production experience in the underlying technology typically need less; candidates new to the platform should plan toward the upper end of that range.
DP-700 is a recognized credential in the Azure ecosystem and signals validated knowledge to employers, recruiters, and clients. Whether it is worth the time and fee for you depends on your role and goals — it tends to pay off most for cloud engineers, architects, and consultants who work with Azure day-to-day or want to move into roles that do.
The passing score for DP-700 is 700 / 1000. The exam contains 50 questions and lasts 2 hr.
The DP-700 exam fee is $165 USD. Fees are set by Azure and may vary by region; always confirm the current price on the official Azure certification page before booking.
Microsoft role-based certifications expire after 1 year but can be renewed for free via an unproctored online assessment on Microsoft Learn, starting 6 months before expiration.
Yes. You can take the exam online (proctored via the provider's secure browser, available 24/7 in most regions) or at an in-person Pearson VUE test center during business hours. Both formats use the same questions, time limit, and passing score.
CertLabPro provides 15 study modes across the practice question bank for DP-700. The exam-simulation mode mirrors the real exam: 50 questions in 2 hr, with the same passing threshold of 700 / 1000. Browse mode lets you read every Q&A statically.