Answer-first summary for fast verification
Answer: It is a globally unique identifier for that specific instance of the job run.
In Databricks, when a job is initiated (for instance, via the command `databricks jobs run-now --job-id 123`), the system returns a `run_id`. This value is the **canonical, globally unique identifier** for that specific execution instance. ### Key Concepts: - **`run_id` vs `job_id`**: The `job_id` refers to the job's configuration/definition, while the `run_id` refers to a unique execution of that definition. - **Functionality**: The `run_id` is used in subsequent API or CLI calls to monitor status, retrieve output, or cancel that specific execution. ### Why other options are incorrect: - **A & D**: The `run_id` is distinct from the `job_id` and is not a result of string concatenation or encoding schemes. - **C**: While Databricks tracks execution history, the `run_id` itself is a unique key, not a cumulative counter.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
After triggering a job using the Databricks CLI and receiving a JSON response containing a run_id, what does this specific value represent?
A
It serves as the job_id associated with the job definition.
B
It is a globally unique identifier for that specific instance of the job run.
C
It is a counter indicating how many times the job definition has been executed in the workspace.
D
It is a composite value created by concatenating the job_id with the current execution count.
No comments yet.