# Databricks Certified Data Engineer Pro (DCDEP) practice exams

> Databricks Certified Data Engineer Pro practice exams: 290 questions in 5 timed tests, every answer explained.

Page: https://devopscodelab.com/exams/databricks-data-engineer-pro/

290 questions in 5 timed practice tests. Each test has about 61 questions and a 120-minute limit. The pass mark is 70%. Results are split across the 9 exam domains.

## Exam at a glance

| Setting | Value |
| --- | --- |
| Practice tests | 5 |
| Questions in total | 290 |
| Questions per test | About 61 |
| Time limit per test | 120 minutes |
| Pass mark | 70% |
| Question types | Single answer and multiple answer (25 multiple-answer questions) |
| Level | Professional |
| Category | Data & Analytics |

These are the settings of our practice tests. Check the official Databricks exam page for the current format before you book.

## Domains and weights

| Domain | Weight | Questions in our bank |
| --- | --- | --- |
| Developing Code for Data Processing using Python and SQL | 23% | 67 |
| Data Ingestion & Acquisition | 12% | 35 |
| Data Manipulation | 12% | 35 |
| Monitoring and Alerting | 10% | 29 |
| Cost & Performance Optimization | 15% | 43 |
| Ensuring Data Security and Compliance | 8% | 23 |
| Data Governance | 5% | 14 |
| Debugging and Deploying | 10% | 29 |
| Data Modeling | 5% | 15 |

## Price and access

- DCDEP practice exams: $14.99 for 12 months of access.
- Free mini exam: 15 questions with explanations (free account): https://devopscodelab.com/app/exams/databricks-data-engineer-pro/mini/
- All-Access subscription includes every exam: https://devopscodelab.com/pricing/
- 10 free questions with answers: https://devopscodelab.com/exams/databricks-data-engineer-pro/free-practice-questions/

## Sample questions

### Question 1 of 3

In a Lakeflow Pipeline, a gold dataset joins a slowly changing product dimension to sales facts and computes revenue per category. Product attributes are corrected retroactively several times a week, and the result must always reflect those corrections. Dashboards read the dataset every hour. Which dataset type should the engineer use?

- A. A materialized view, because its refreshed result always matches the query, including corrected dimension rows
- B. A streaming table, because it reads each new sales row once and therefore keeps the per-category revenue current at the lowest compute cost
- C. A streaming table with a stream-static join, because the static product side is re-read on every micro-batch and updates past aggregates
- D. A temporary view, because it is evaluated at query time by every dashboard and therefore never needs a pipeline refresh to stay accurate

**Answer:** A

**Explanation:** A materialized view's result always matches its defining query, including changes to rows that were already processed, which is what retroactive dimension corrections require. A streaming table processes appended input once and does not revisit earlier output when dimension rows change. A temporary view exists only within the pipeline and is not published for dashboards. In a stream-static join the latest static data is used only for new stream rows; previously emitted aggregates are not recalculated.

### Question 2 of 3

A team compares hand-written Spark Structured Streaming with Lakeflow Pipelines for a new bronze-silver-gold ETL. Requirements are automatic dependency ordering between tables, built-in data quality rules with metrics, and managed retries and autoscaling, with as little orchestration code as possible. Which option fits best?

- A. Lakeflow Pipelines in development mode only, because production mode disables expectations and requires manual table ordering
- B. Lakeflow Pipelines, because dependencies, expectations, retries and compute are managed declaratively from the dataset definitions
- C. Structured Streaming in notebooks chained with Lakeflow Jobs tasks, because job retries and task dependencies cover the same requirements
- D. Structured Streaming with foreachBatch per table, because each batch function can log quality metrics and manage its own retries

**Answer:** B

**Explanation:** Lakeflow Pipelines infer the dependency graph from dataset definitions, record expectation metrics in the event log, and manage retries and autoscaling of compute, minimising orchestration code. Chaining notebooks with job tasks gives retries but requires you to code and order each stream and build quality checks yourself. foreachBatch per table puts quality logging and retry logic in custom code. Production mode does not disable expectations; it differs in retry behaviour and cluster reuse.

### Question 3 of 3

A data provider on Databricks wants to share a curated orders table and its ongoing changes with a partner who also uses Databricks in a different account and cloud region. The partner must be able to read the table incrementally as a stream. Which setup should the provider use?

- A. Lakehouse Federation: create a connection in the partner's workspace to the provider's SQL warehouse and expose the table as a foreign catalog
- B. Clean Rooms: add the orders table to a clean room and let the partner run approved notebooks against it to produce output tables
- C. Databricks-to-Databricks sharing: add the table to a share WITH HISTORY for a recipient keyed on the partner's sharing identifier
- D. Open sharing: add the table to a share without history and send the partner a bearer-token credential file to download for their client

**Answer:** C

**Explanation:** Databricks-to-Databricks sharing uses the recipient's metastore sharing identifier, and sharing a table WITH HISTORY enables the recipient to read it as a stream and use time travel. A share without history cannot be streamed, and token-based open sharing is meant for non-Databricks clients. Lakehouse Federation gives query-time access through a connection but does not deliver the table's change history for streaming reads. Clean Rooms is for joint analysis without exposing raw data, not for giving a partner a readable replica.


## Study plans

### Two weeks

1. Day 1: take practice test 1 in exam mode to get a baseline.
2. Days 2 to 5: domain mode on Developing Code for Data Processing using Python and SQL and Cost & Performance Optimization, the two most heavily weighted domains.
3. Day 6: practice test 2 in exam mode, then the mistakes quiz.
4. Days 7 to 12: practice tests 3 to 5, one every other day, each followed by its mistakes quiz.
5. Days 13 and 14: final mode. Book the exam when your readiness stays above the pass mark.

### Four weeks

1. Week 1: one practice test in practice mode, reading every explanation. Note your two lowest domains.
2. Week 2: domain mode on those two domains, then a second practice test in exam mode.
3. Week 3: practice tests 3 and 4 in exam mode, with the mistakes and flagged quizzes after each.
4. Week 4: practice test 5 and final mode until your readiness holds above the pass mark.

## Questions about the DCDEP practice exams

**Are these real DCDEP exam questions?**

No. We write every question ourselves and map it to the published DCDEP exam objectives. We do not use leaked or recalled questions.

**Do the time limit and pass mark match the official exam?**

They match the settings of our practice tests. Exam providers change their format from time to time, so check the official exam page before you book.

**Can I try it before I pay?**

Yes. The free mini exam has 15 questions with full explanations and needs no account.

**How long do I keep access?**

A single-exam purchase gives you 12 months of access. All-Access includes this exam for as long as your subscription runs.

**What happens after I finish a test?**

You get a score, a pass or fail against the pass mark, a score per domain and every answer with its explanation.

Last updated November 2026.

DevOpsCode Lab is not affiliated with Databricks. DCDEP and related names are trademarks of their owners. We write every question ourselves; these are not real exam questions.
