Finance auditors need to see which jobs and upstream tables feed the published parking-revenue gold table. Where should they look in Azure Databricks?

Catalog Explorer lineage showing owners, history, dependencies, and lineage for the parking-revenue gold table is where finance auditors should look in Azure Databricks. Unity Catalog lineage ties published gold objects to upstream tables and producing jobs so municipal finance can see which pipelines and silver or bronze inputs feed parking-revenue reporting without reconstructing tribal knowledge.

Relying only on Delta table file metadata showing files, sizes, versions, and lineage for the gold table fails by concept because it shows the gold table's own storage files, sizes and versions, not the upstream jobs and tables that feed it. Unity Catalog audit logs showing principals, queries, sources, and destinations for the gold table are raw event history requiring manual reconstruction, not queryable lineage that directly tracks current job and table dependencies. Workflow job configuration showing tasks, clusters, schedules, and dependencies for the gold table describes a single job's setup and schedule but does not answer which upstream tables and producing jobs feed the published gold table.

Exam caveat: Lineage visibility depends on workloads writing through instrumented, UC-governed paths; external dumps and unmanaged files may leave gaps. Owner and history metadata complement lineage but answer different questions—who owns or changed an object versus which upstream dependencies feed it. Lineage is for impact analysis and audit, not a replacement for forensic review of audit logs on the revenue tables themselves.

Operational check: Open the parking-revenue gold table in Catalog Explorer, inspect lineage and dependencies for upstream tables and jobs, confirm owners and recent history align with the finance publishing process, and trace one known silver feeder to verify the diagram matches the municipal ETL design.