Microsoft DP-750 Practice Exam Questions & Answers
Microsoft DP-750 Exam Details
Key details for this exam, checked against the published exam outline
- Exam Code
- DP-750
- Full Name
- Implementing Data Engineering Solutions Using Azure Databricks
- Issuing Body
- Microsoft
- Question Format (Our Bank)
- Multiple Choice, Hotspot, Drag & Drop, Case Studies
- Delivery
- Online proctored or at a Pearson VUE test centre
- Eligibility
- No prerequisites. Candidates should have subject matter expertise in integrating and modeling data, building and deploying optimized pipelines, and troubleshooting and maintaining workloads in Azure Databricks, plus experience with SQL, Python, Git, Micro
- Full Question Set
- 103 questions Get All Questions
Free DP-750 Practice Questions
Each question shows the correct answer and an explanation of why it is right
Question 1 Domain 3 Prepare and process data
You have a Lakeflow Spark Declarative Pipelines {SDP) pipeline in Azure Databricks. The pipeline ingests transaction data into a table named Table1.
You need to ensure that in the event of an invalid record, the pipeline continues to run. The solution must meet the following requirements:
* Invalid records must NOT be written to Table 1.
* Invalid records must be preserved for review.
* Minimize development effort
What should you do?
The correct answer is B --- define a pipeline expectation.
SDP expectations with @dlt.expect_or_drop are built precisely for this scenario: the pipeline keeps running, bad records are excluded from Table1, and those records are automatically captured in the pipeline's event log as expectation violations --- available for review without any extra code.
Option A (custom quarantine logic) would work but requires writing and maintaining additional pipeline tables and routing logic. The whole point of SDP expectations is to handle this pattern declaratively, with far less code.
Option C (WHERE clauses in downstream queries) is a read-time filter, not a write-time guard. Invalid records would still land in Table1 and would simply be hidden from downstream views --- they're not preserved for review in any structured way. Option D (check constraint on Table1) would throw an exception on write and halt the pipeline, violating the 'pipeline continues to run' requirement.
Question 2 Domain 2 Secure and govern Unity Catalog objects
You have an Azure Databricks workspace that is enabled for Unity Catalog and contains two Delta tables named Table1 and Table2 of the same data type.
Table1 contains a column named Columnl. Table2 contains a column named Column2. You run the following query.
SELECT Column1
FROM Table1
GROUP BY Column1
HAVING COUNT(") > 1
INTERSECT
SELECT C0lumn2
FROM Table2
GROUP BY Column2
HAVING COUNT(') > 1;
What occurs when you run the query?
The correct answer is B --- values appear in both tables more than once.
Reading the query from the inside out: each subquery identifies values that appear more than once within their own table. The first subquery returns Column1 values that are duplicated in Table1. The second returns Column2 values that are duplicated in Table2. INTERSECT then returns only the values that appear in both result sets --- meaning values that are duplicated in Table1 AND also duplicated in Table2.
Option A describes a UNION result (values in either table), not INTERSECT. Option C only considers duplicates in Table1, ignoring the Table2 condition --- that would be the first subquery in isolation. Option D describes values exclusive to Table2 (EXCEPT or MINUS), the opposite of INTERSECT's requirement that values appear in both sets.
INTERSECT always requires membership in both operands --- that's its fundamental definition in standard SQL.
Question 3 Domain 4 Deploy and maintain data pipelines and workloads
You have an Azure Databricks workspace that is enabled for Unity Catalog.
You need to implement a daily batch data process that requires complex and highly customized Python transformations. The solution must minimize additional complexity.
What should you include in the solution?
A Databricks notebook provides the flexibility required to implement complex, highly customized Python and PySpark transformations. Scheduling that notebook as a Lakeflow Jobs task supplies native daily orchestration, monitoring, retries, and compute management without introducing another service. Azure Data Factory data flows are oriented toward visually designed transformations and would add external orchestration complexity for logic already implemented most naturally in Python. A continuous job is inappropriate because the workload runs once per day rather than continuously. Spark Declarative Pipelines is effective for declarative batch and streaming ETL, but it is less direct when the core requirement emphasizes highly customized procedural Python transformations. A notebook task therefore provides the necessary programming freedom while keeping scheduling and operation inside Azure Databricks.
Get the complete DP-750 question set
$20$40
Question 4 Domain 1 Set up and configure an Azure Databricks environment
You have an Azure Databricks workspace
You are creating a Lakeflow Spark Declarative Pipelines (SDP) pipeline that scales automatically. You need to configure compute for the pipeline. The solution must minimize operational costs and effort. What should you use?
The correct answer is C --- a job cluster that uses autoscaling.
Job clusters (also called pipeline clusters in the SDP context) are created exclusively for a pipeline run and terminated when the pipeline stops. You pay only for what the pipeline uses, and there's no idle cost between runs. Autoscaling on a job cluster lets the pipeline expand during heavy processing and contract during lighter stages --- the combination of on-demand lifecycle and elastic scaling gives the lowest operational cost.
Option A (all-purpose cluster) runs at a higher DBU rate and persists beyond the pipeline's lifecycle, meaning you're paying for it even when the pipeline isn't running. Option B (SQL warehouse) is optimised for interactive BI and ad-hoc queries, not for the batch/streaming workloads SDP pipelines run. Option D (single-node all-purpose) has no scaling, runs at the all-purpose DBU rate, and is capped at one node --- unsuitable for any production pipeline.
Question 5 Domain 4 Deploy and maintain data pipelines and workloads
You need to develop the task logic for a new job in Lakeflow Jobs that processes telemetry data.
Each task must contain only the appropriate logic for its step in the pipeline. The solution must support the planned changes and meet the data ingestion and processing requirements.
What should you do?
The correct answer is D. Breaking the pipeline into separate tasks for ingestion, cleansing, and curation is the foundation of well-designed Lakeflow Jobs pipelines. Each task should own one responsibility --- when a task does too much, debugging a failure becomes a hunt through unrelated code, and retry logic becomes expensive because you re-execute work that already succeeded.
Contoso's planned changes explicitly call for 'a clear execution order and dependencies' and 'orchestrate multi-step ingestion and transformation workflows.' Separate tasks map directly to those goals: Lakeflow Jobs tracks each task's status independently, so if cleansing fails, ingestion doesn't re-run.
Option A bundles everything into one notebook, which means a curation bug forces a full re-ingestion. Option B copies logic three times --- any future change must be applied in triplicate, which is a maintenance hazard. Option C forces everything through SQL MERGE, which is the wrong tool for raw-event ingestion and doesn't address cleansing or schema drift.
Question 6 Domain 4 Deploy and maintain data pipelines and workloads
You have an Azure Databricks workspace that is enabled for Unity Catalog.
You need to profile a table to meet the following requirements:
The count of null values per column must be evaluated repeatedly as new records are added to the table.
Changes in the count of null values must be observable over the progression of the dataset.
Which type of profile should you create?
A time series profile repeatedly calculates data-quality metrics as a table changes and preserves those measurements over time. This makes it possible to observe whether the number of null values in each column is increasing, decreasing, or remaining stable as new records are added. A snapshot profile evaluates the table at a particular point in time and is therefore insufficient when the requirement is to analyze metric progression across multiple updates. Inference is associated with deriving information such as a schema or statistical characteristics; it is not the profile type used to maintain a historical sequence of monitoring measurements. Because the question requires repeated evaluation and the ability to observe changes throughout the dataset's progression, the time series profile satisfies both requirements.
Question 7 Domain 4 Deploy and maintain data pipelines and workloads
You have an Azure Databricks workspace that is attached to a Unity Catalog metastore named metastore1. Metastore1 contains a catalog named catalog 1.
You need to create a new schema named schema2 that meets the following requirements:
* Is contained in catalog1
* Uses abfss://containergstorageaccount.dfs.core.windows.net/data as the Managed location
Which SQL statement should you execute?
The correct answer is A. The Unity Catalog DDL for creating a schema inside a specific catalog and setting a custom managed storage path uses the three-part name (catalog.schema) and the MANAGED LOCATION clause:
CREATE SCHEMA catalog1.schema2 MANAGED LOCATION 'abfss://...';
The three-part name explicitly places the schema inside catalog1. MANAGED LOCATION tells Unity Catalog where to store managed tables and volumes created under this schema --- any managed table without its own explicit location will inherit this path.
Option B uses CREATE CATALOG, which creates an entirely new catalog rather than a schema. Option C uses the LOCATION keyword without MANAGED --- that syntax is for external locations, not for overriding the managed storage path of a schema. Option D uses WITH DBPROPERTIES, which stores arbitrary key-value metadata but has no effect on where Unity Catalog physically stores data.
What the Microsoft DP-750 Exam Covers
Exam domains verified against the Official Microsoft DP-750 exam guide, last checked November 2026.
Domain 1 Set up and configure an Azure Databricks environment
15% - 20%Choose appropriate compute types including job compute, serverless, warehouse, classic compute, and shared compute. Configure compute performance and features including CPU, node count, autoscaling, Photon acceleration, and runtime versions. Create and organize Unity Catalog objects through naming conventions, catalogs, schemas, volumes, tables, views, and materialized views. Implement foreign catalogs and DDL operations.
Sample question from this domain above Q4
Domain 2 Secure and govern Unity Catalog objects
15% - 20%Grant privileges to principals for Unity Catalog objects and implement table, column, and row-level access control. Access Azure Key Vault secrets and authenticate using service principals and managed identities. Create descriptions for data discovery, configure attribute-based access control using tags and policies, apply row filters and column masks, manage data retention, set up lineage tracking, and configure audit logging.
Sample question from this domain above Q2
Domain 3 Prepare and process data
30% - 35%Design data modeling including ingestion logic, extraction types, and file formats. Choose ingestion tools like Lakeflow Connect, notebooks, and Azure Data Factory, plus loading methods and table formats like Parquet, Delta, CSV, JSON, or Iceberg. Design partitioning schemes, SCD types, and clustering strategies. Ingest data using Lakeflow Connect, notebooks, SQL methods, CDC feeds, and Spark Structured Streaming from Event Hubs. Cleanse and transform data through profiling, type selection, handling duplicates and nulls, and using joins and aggregations. Implement data quality validation including nullability, cardinality, range checks, and schema enforcement.
Sample question from this domain above Q1
Domain 4 Deploy and maintain data pipelines and workloads
30% - 35%Design pipeline order of operations and choose between notebooks and Lakeflow Spark Declarative Pipelines. Create jobs with setup, configuration, triggers, schedules, and alerts. Implement error handling and automatic restarts. Apply Git version control with branching and pull requests. Implement testing strategies including unit, integration, end-to-end, and UAT tests. Configure and deploy Databricks Asset Bundles using CLI and REST APIs. Monitor cluster consumption, troubleshoot Lakeflow Jobs and Spark jobs, investigate caching and shuffle issues using Spark UI, optimize Delta tables with OPTIMIZE and VACUUM, and configure logging and alerts in Azure Monitor.
DP-750 Exam FAQ
Common questions about the exam itself
What background and experience do I need before taking DP-750?
How long should I prepare for the DP-750 exam?
What makes the DP-750 exam difficult and what should I focus on?
How much does the DP-750 exam cost?
How long is the DP-750 exam and what format are the questions?
What happens if I fail the DP-750 exam and want to retake it?
How long is the DP-750 certification valid and how do I renew it?
What job role does the DP-750 certification align with?
How does DP-750 fit into the Microsoft data engineering certification path?
What is the difference between DP-750 and DP-700 certifications?
Other Microsoft Exams
Free practice questions for more Microsoft certification exams
