Home / Data Analyst practice test / Managing Data / Question

Databricks Data Analyst Associate · free practice question

A data engineer wrote a notebook six months ago that reads from `gold.finance.revenue_summary` and writes to `gold.reporting.quarterly_kpis`. A colleague now…

Exam-style question on Managing Data from the free Data Analyst practice test, with the answer and a full explanation below.

Updated November 10, 2026

Managing Data

A data engineer wrote a notebook six months ago that reads from gold.finance.revenue_summary and writes to gold.reporting.quarterly_kpis. A colleague now opens the quarterly_kpis table in Catalog Explorer to trace where the data originally came from. They also want to understand whether column-level lineage is captured. Which combination of statements CORRECTLY describes Unity Catalog's lineage behavior for this scenario?

  1. AUnity Catalog captures lineage for tables that a workspace administrator has registered for lineage tracking with ALTER TABLE ... ENABLE LINEAGE, and tables created before that step have no retroactive history. If lineage was not enabled six months ago, the colleague will see no upstream table for quarterly_kpis. Column-level lineage is available for tables stored in the Iceberg format, while Delta tables get table-level lineage.
  2. BUnity Catalog retains lineage with no time-based expiration: the link between source and target stays in the metastore until an administrator runs ALTER TABLE quarterly_kpis DROP LINEAGE, so the colleague will see revenue_summary upstream. Column-level lineage is captured for each transformation type, including user-defined functions, path-based references such as select * from delta.'s3://...', and RDD-based operations.
  3. CUnity Catalog captures lineage for queries run from the Databricks SQL editor and AI/BI dashboards, while notebook queries using Python or Scala DataFrames are excluded: notebooks run in the classic compute plane, which is isolated from the lineage capture service in the serverless compute plane. The colleague will see quarterly_kpis as a lineage endpoint with no upstream connection from the notebook, at table level or at column level.
  4. DUnity Catalog aggregates lineage within a single workspace, so if the notebook ran in a different workspace from the one the colleague is using, the upstream table is not shown even when both workspaces share one metastore. Column-level lineage is captured, but a data steward first has to annotate the column-to-column mappings in the Catalog Explorer UI before the graph is populated; it is not inferred from the queries themselves.
  5. EUnity Catalog captures runtime lineage for queries on tables registered in the metastore with no configuration, across Python, SQL, Scala and R through Spark DataFrame or Databricks SQL interfaces. The colleague opens quarterly_kpis in Catalog Explorer, selects the Lineage tab and clicks 'See Lineage Graph' to find revenue_summary upstream. Column-level lineage is captured too, and lineage is retained for one year, so a run from six months ago still appears.
Answer & explanation

Correct answer: E

WHY E: Unity Catalog lineage needs no opt-in or configuration: it is captured at runtime whenever queries run on Databricks against Unity Catalog-registered tables through Spark DataFrame or Databricks SQL interfaces. The documentation says lineage is 'supported for all languages' and captured 'down to the column level', and clicking a column in the graph shows the upstream columns it was derived from. Opening the table in Catalog Explorer, choosing the Lineage tab and 'See Lineage Graph' is the documented procedure. Lineage data is retained for a rolling one-year window, so the link between revenue_summary and quarterly_kpis from a run six months ago is still visible.

WHY NOT A: Unity Catalog does not require lineage enrollment with ALTER TABLE ... ENABLE LINEAGE; capture happens for all qualified workloads without setup. Column-level lineage is supported for Delta tables and has no format-based restriction to Iceberg.

WHY NOT C: The documentation states lineage is 'supported for all languages' and captured via 'Spark DataFrame (for example, Spark SQL functions that return a DataFrame) or Databricks SQL interfaces such as notebooks or the SQL query editor'. Notebooks using DataFrames or Spark SQL are covered; the classic versus serverless compute distinction does not exclude notebook lineage.

WHY NOT D: Lineage is 'aggregated across all workspaces attached to a Unity Catalog metastore', so a run from another workspace on the same metastore shows up in the colleague's view. Column-level lineage is inferred from query plans and needs no manual annotation by a data steward.

WHY NOT B: Lineage data is retained for one year (a rolling window), not indefinitely, and there is no ALTER TABLE ... DROP LINEAGE command. The documentation also lists cases where column-level lineage is not captured: UDFs (which can obscure column mapping), path-based table references such as select * from delta.'s3://...', RDD-based operations, global temp views, and checkpointed datasets.

Take the full Data Analyst practice test free →

Would you pass today?

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

Start the free test →