Databricks Data Engineer Associate · Free practice question 6 of 12
Job maximum concurrent runs
A job at Keswick Media is scheduled every 10 minutes, and occasionally a run takes longer than 10 minutes. The team wants to prevent a new run from starting while the previous run is still executing. Which job setting controls this?
- A.Task retry count, set to 0
- B.Run if condition, set to All succeeded
- C.Maximum concurrent runs, set to 1
- D.Auto termination, set to 10 minutes
Show answer and explanation
Correct answer: C. Maximum concurrent runs, set to 1
Why: The maximum concurrent runs setting limits how many runs of a job can be active at the same time; with a value of 1, a new run does not start while one is already in progress; it is skipped, or queued if queueing is enabled on the job. Retries control reruns of failed tasks, Run if conditions depend on upstream task results, and auto termination applies to idle clusters.
More free Databricks Data Engineer Associate questions
- Delta shallow vs deep clone
- Auto Loader schema hints
- Reading notebook task parameters
- collect_set vs collect_list aggregation
- Triggered vs continuous pipeline mode
- Job task timeout setting
- SHOW GRANTS on Unity Catalog objects
- Transferring object ownership
- Compute policies for cluster governance
- ALTER TABLE ADD COLUMNS on Delta
- Spark lazy evaluation transformations vs actions