Home / DE Associate practice test / Data Transformation and Modeling / Question

Databricks Data Engineer Associate · free practice question

A data engineer needs downstream consumers to read row-level inserts, updates, and deletes from a Delta table incrementally, without scanning the full table on…

Exam-style question on Data Transformation and Modeling from the free DE Associate practice test, with the answer and a full explanation below.

Updated November 10, 2026

Data Transformation and Modeling

A data engineer needs downstream consumers to read row-level inserts, updates, and deletes from a Delta table incrementally, without scanning the full table on every run. Which combination correctly enables and then reads that change data?

  1. ASet delta.enableChangeDataFeed = true on the table, then query it with time travel using VERSION AS OF, which surfaces a per-row _change_type value for the insert, update, and delete events between two versions.
  2. BSet delta.enableChangeDataFeed = true on the table, then read the changes using the readChangeFeed option or the table_changes() function, which return the _change_type, _commit_version, and _commit_timestamp columns.
  3. CSet spark.databricks.delta.changeDataFeed = true at the cluster level, then read the _delta_log JSON files directly and parse the add and remove actions to rebuild the insert, update, and delete rows for each version.
  4. DSet delta.enableChangeDataFeed = true on the table, then read with the readChangeFeed option, which returns the final post-image of each changed row and leaves update pre-images and deleted rows out of the feed.
  5. ESkip the table property, as change data feed is on by default for Delta tables in Unity Catalog, then add the table_changes() function to a query to receive the _change_type and _commit_version columns.
Answer & explanation

Correct answer: B

WHY B: You enable CDF with delta.enableChangeDataFeed = true, then read it via the readChangeFeed option or table_changes(), which expose _change_type, _commit_version, and _commit_timestamp.

WHY NOT A: Time travel with VERSION AS OF returns table snapshots, not row-level _change_type records.

WHY NOT C: CDF is a table property, not a cluster flag, and you should not hand-parse _delta_log files to rebuild row changes.

WHY NOT D: The feed includes insert, update_preimage, update_postimage, and delete rows, not just post-images.

WHY NOT E: CDF is off by default and has to be enabled per table before table_changes() will work.

Take the full DE Associate practice test free →

Would you pass today?

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

Start the free test →