You are the owner of a Unity Catalog-enabled Lakeflow Spark Declarative Pipeline and want to query its event log directly in SQL without publishing the event log table name. Which query pattern is supported by default?
Answer & explanation
Correct answer: A
WHY A: Databricks documents a function-style access pattern to query the hidden event log table as the pipeline owner: SELECT * FROM event_log(<pipelineId>). By default the underlying hidden table name is formatted like event_log_{pipeline_id}.
WHY NOT B: The event log is not queried via the system catalog in that way; it is associated with the pipeline's own event log table/function.
WHY NOT C: pipeline_event_log is not a documented function; the table-valued function is named event_log.
WHY NOT D: live was the legacy keyword for referencing datasets inside pipeline source code; it is not a schema that exposes an event log function, so this is not a documented query interface.