DATABRICKS-DEP Question 56

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose A0

  - Correct answer : A — Run `SELECT * FROM event_log('<pipeline_id>')` in a notebook attached to a cluster or SQL warehouse, reading the pipeline's hidden Delta event log table directly by ID. A . The `event_log()` table-valued function reads the pipeline's default hidden event log table by pipeline ID with no advance setup, which matches the no-configuration-change requirement. B . Publishing the event log to a visible catalog table is an optional convenience for governed access, not a prerequisite for querying it, so this adds an unnecessary configuration step. C . `system.lakeflow.pipelines` holds pipeline-level metadata for billing and auditing rather than per-flow progress or expectation metrics, so it cannot answer this event-level question. D . The Jobs API reports task and run status for jobs, not the flow-level `data_quality` metrics that only appear inside the pipeline event log's `flow_progress` events.