Skip to content

Building a pipeline with Lakeflow Spark Declarative Pipelines

Lakeflow Spark Declarative Pipelines (formerly Delta Live Tables/DLT) let you define ETL logic declaratively using SQL or PySpark, and the pipeline engine handles orchestration, dependency resolution, cluster management, and execution. You define datasets as streaming tables or materialized views and Databricks automatically infers the DAG, manages incremental processing, and tracks lineage.

1 · Learn the must-know

  • Pipelines are defined using SQL CREATE STREAMING TABLE / CREATE MATERIALIZED VIEW syntax or the equivalent @dlt.table / @dlt.view decorators in PySpark, with the pipeline engine inferring the dependency DAG from query references rather than requiring manual orchestration code.
  • A pipeline is created and configured (source notebooks/files, target catalog and schema, compute settings, and Triggered vs Continuous mode) either through the Databricks UI Pipelines editor, Databricks Asset Bundles, or the REST API/CLI, not by directly running notebooks interactively.
  • Triggered pipelines run once and stop (suitable for scheduled batch-like execution via a Databricks Job), while Continuous pipelines keep running to process new data with low latency; choosing the right mode is a common exam distinction.
  • Expectations (constraints defined with EXPECT/EXPECT OR DROP/EXPECT OR FAIL in SQL, or expect_all/expect_all_or_drop/expect_all_or_fail decorators in Python) enforce data quality and are evaluated per pipeline run, with violation metrics surfaced in the pipeline event log.
  • The pipeline's target catalog and schema settings determine where streaming tables and materialized views are published as Unity Catalog objects, so incorrect target configuration is a common source of failures or misplaced tables.
  • Pipeline execution details, data quality metrics, and lineage are all visible in the pipeline's event log and graph view in the Pipelines UI, which is the primary tool for monitoring and troubleshooting pipeline runs.

2 · Check your understanding

Check this objectiveFree · always available

A data engineer is building a Lakeflow Declarative Pipeline that ingests JSON files landing continuously in a cloud storage location. The engineer wants each file to be read exactly once and processed incrementally as new files arrive, without recomputing results from files already ingested. Which dataset type should the engineer declare for this ingestion step?

Your objective map0 tried · 0 answered correctly · 77 untouched

What you have tried across DP-750's objectives, not a readiness score.

Set up and configure an Azure Databricks environment15-20% of the exam0 of 13 tried
Secure and govern Unity Catalog objects15-20% of the exam0 of 12 tried
Prepare and process data30-35% of the exam0 of 28 tried
Deploy and maintain data pipelines and workloads30-35% of the exam0 of 24 tried

3 · Keep going