Home / DE Professional practice test / Cost & Performance Optimisation / Question

Databricks Data Engineer Professional · free practice question

A data engineering team enables change data feed on a Silver Delta table (`delta.enableChangeDataFeed = true`) to power a downstream audit pipeline. Six months…

Exam-style question on Cost & Performance Optimisation from the free DE Professional practice test, with the answer and a full explanation below.

Updated November 16, 2026

Cost & Performance Optimisation Hard

A data engineering team enables change data feed on a Silver Delta table (delta.enableChangeDataFeed = true) to power a downstream audit pipeline. Six months later, they attempt to read CDF changes starting from version 1 (the day CDF was enabled). The read fails with an error indicating the version is no longer available. Separately, after a DBA runs ALTER TABLE silver RENAME COLUMN amount TO total_amount, an ongoing CDF streaming read on the table also fails. Which explanation correctly identifies the root cause for BOTH failures?

  1. AFirst failure: change data feed records are transient and follow the table's retention policy; once version 1 has been removed by VACUUM, its change data is unreadable. Second failure: a column rename is a non-additive schema change under column mapping, and a CDF streaming read does not span a version range that contains one.
  2. BBoth failures come from change data feed needing to be re-enabled after a schema change. A column rename resets the CDF configuration, requiring ALTER TABLE ... SET TBLPROPERTIES (delta.enableChangeDataFeed = true) to be run again, and historical versions become inaccessible after re-enabling.
  3. CBoth failures come from insufficient permissions. Reading change data feed from specific historical versions, in batch or in a stream, requires the SELECT WITH HISTORY privilege, which is a separate grant from the standard SELECT on the current table version and is revoked by DDL changes.
  4. DFirst failure: CDF starts recording from the version after the table property is set, leaving no CDF records for version 1. Second failure: RENAME COLUMN creates a new table version, and CDF does not read across DDL-version boundaries, as Databricks excludes DDL transaction versions from CDF output.
  5. EBoth failures come from the table using Unity Catalog managed storage. CDF reads on managed tables go through the _change_data directory, which is controlled by the predictive optimization engine and is not accessible for historical queries beyond the last OPTIMIZE cycle.
Answer & explanation

Correct answer: A

WHY A: Two separate root causes are identified. (1) Version availability: CDF records are documented as TRANSIENT. They follow the table's retention policy, and VACUUM removes old table versions' files at regular intervals; once version 1 is beyond the retention window, its change data can no longer be read. The documentation states: 'When a version is removed, you can no longer read the change data feed for that version.' CDF is not a permanent audit log and records are eventually purged. (2) Column rename: Delta column mapping permits renaming columns without rewriting data files, but CDF has documented limitations after non-additive schema changes (renaming, dropping, or changing types of columns). In DBR 12.2 LTS and below, CDF streaming reads on column-mapped tables that experienced non-additive changes fail outright. In DBR 13.x+, schema tracking helps ongoing streams, but a streaming read still does not span a version range that contains a non-additive schema change.

WHY NOT B: Column renames do not reset CDF enablement. The delta.enableChangeDataFeed = true property persists across schema changes, so nothing needs to be re-enabled.

WHY NOT C: Permissions are not the issue: the failures come from data retention and schema evolution constraints, not access control. SELECT WITH HISTORY is not a Delta Lake or Unity Catalog privilege.

WHY NOT D: It is true that CDF records changes from the point it is enabled, but that is NOT why reading version 1 fails SIX MONTHS later: the version was readable at first and became unavailable after retention/VACUUM removed it. The rename failure comes from the non-additive schema change, not from DDL versions being excluded from CDF output.

WHY NOT E: CDF reads are not managed or blocked by predictive optimization. There is no _change_data access restriction tied to the OPTIMIZE cycle.

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 →