Home / DE Professional practice test / Data Ingestion & Acquisition / Question

Databricks Data Engineer Professional · free practice question

A downstream pipeline needs to process incremental changes from an upstream Delta table. The upstream table is NOT append-only: it can receive `UPDATE`…

Exam-style question on Data Ingestion & Acquisition from the free DE Professional practice test, with the answer and a full explanation below.

Updated November 16, 2026

Data Ingestion & Acquisition Easy

A downstream pipeline needs to process incremental changes from an upstream Delta table. The upstream table is NOT append-only: it can receive UPDATE, MERGE, and DELETE operations. The downstream requirement is to capture inserts, updates, and deletes reliably without full reprocessing. Which approach is the most robust?

  1. AEnable Delta change data feed (CDF) on the upstream table and stream from the change feed to process insert, update and delete events.
  2. BStream directly from the upstream Delta table using spark.readStream.table(...); Delta ACID commits propagate updates and deletes downstream.
  3. CStream from the upstream Delta table and set skipChangeCommits=true; this propagates updates and deletes while keeping the stream stable.
  4. DStream from the upstream Delta table and set ignoreDeletes=true; this propagates updates and deletes and ignores partition drops.
Answer & explanation

Correct answer: A

WHY A: When the source Delta table includes updates and deletes, streaming from the Change Data Feed is the robust pattern because it represents changes explicitly and supports downstream processing of each change type (insert, update, delete).

WHY NOT B: Streaming from a Delta table itself is recommended when the source is append-only; updates and deletes cause exceptions or require special handling, and ACID commits do not make the stream propagate them.

WHY NOT C: skipChangeCommits ignores commits that modify or delete existing records; it does not propagate those changes downstream.

WHY NOT D: ignoreDeletes is a legacy option that handles one specific pattern (full partition drops) and does not provide reliable propagation of update/delete semantics.

Take the full DE Professional practice test free →

Would you pass today?

This question is one of 60 in the free, timed Databricks Data Engineer Professional practice test. Take it and get a section-by-section score.

Start the free test →