Answer-first summary for fast verification
Answer: It serves as a globally unique identifier for that specific execution instance of the job.
The `run_id` is the canonical, globally unique identifier for a specific execution of a Databricks job. * **Why A is correct**: When you execute a command like `databricks jobs run-now --job-id 123`, the system returns a `run_id` (e.g., `456`). This ID is unique to that specific run and is used in subsequent API or CLI calls to monitor status, retrieve logs, or cancel the execution. * **Why others are incorrect**: The `run_id` is not a counter, nor is it derived from the `job_id` via concatenation. Furthermore, it is distinct from the `job_id`, which refers to the static configuration/definition of the job rather than a specific instance of its execution.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
After initiating a job using the Databricks CLI and receiving a JSON response containing a run_id, what does this specific identifier represent?
A
It serves as a globally unique identifier for that specific execution instance of the job.
B
It is a concatenation of the job_id and the number of times the job has been triggered.
C
It represents the total execution count of all jobs within the workspace at that moment.
D
It is an alias for the job_id that refers back to the job's definition.