Your team wants a lightweight script in CI that checks whether a specific Lakeflow Job run failed overnight and posts a summary to Slack. Which statement best describes how the Databricks CLI relates to the REST APIs for this use case?
Answer & explanation
Correct answer: D
WHY D: Databricks documents that the CLI wraps the REST API and exposes commands that correspond to API operations (for example databricks jobs get-run maps to the Jobs API runs/get endpoint). That makes it suitable for automation, including monitoring and inspection flows such as checking an overnight Lakeflow Job run from CI, without requiring UI interaction.
WHY NOT A: This confuses the CLI with dbutils, the notebook utility library. The CLI is a local tool that calls the workspace over HTTPS; it is not restricted to running inside notebooks and needs no attached cluster.
WHY NOT B: This confuses the CLI with Databricks Connect, which runs Spark code remotely over Spark Connect (gRPC). The CLI does not bypass the REST APIs; it is built on them, so UI scraping or another protocol is unnecessary for programmatic workflows.
WHY NOT C: The CLI is not limited to workspace files and repos. The Jobs API and Pipelines API are part of the workspace REST API surface and can be used programmatically either directly or via the CLI's jobs and pipelines command groups.