Question
You have an Azure Databricks workspace that is enabled for Unity Catalog.
You need to ensure that data lineage is captured and can be reviewed for tables accessed by Databricks notebooks and jobs. The solution must minimize administrative effort.
Which compute configuration should you use to capture the data lineage and what should you use to review the data lineage? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Explanation
Capture: Unity Catalog records lineage automatically for queries against tables registered in the metastore, so what matters is that the compute works with Unity Catalog, and no separate lineage setup is needed. A single-user or interactive cluster describes how compute is used or shared, not whether it is governed by Unity Catalog, so those labels alone do not guarantee capture.
Review: Catalog Explorer has a Lineage tab on each table, with an interactive lineage graph and links to the related notebooks and jobs. Log Analytics and Azure Data Explorer are not where Unity Catalog lineage is presented, and a DAG only describes the task order inside a job or pipeline.
