Home / DE Associate practice test / Working with Lakeflow Jobs / Question

Databricks Data Engineer Associate · free practice question

A data engineer schedules a Lakeflow Job to run every 15 minutes. Occasionally a run takes longer than 15 minutes. The engineer notices that the next scheduled…

Exam-style question on Working with Lakeflow Jobs from the free DE Associate practice test, with the answer and a full explanation below.

Updated November 10, 2026

Working with Lakeflow Jobs

A data engineer schedules a Lakeflow Job to run every 15 minutes. Occasionally a run takes longer than 15 minutes. The engineer notices that the next scheduled run does not start while the previous run is still in progress, and wants to understand this behavior and change it if necessary. Which statement is correct?

  1. AJobs always queue every skipped scheduled trigger and replay them back to back once the current run ends, so no scheduled interval is ever missed no matter how long any individual run happens to take to finish.
  2. BA job permits unlimited concurrent runs by default, so the observed serialization must come from the cluster being too small; adding more workers to the job cluster is the only way to let two runs proceed at once.
  3. CScheduled triggers that fire during an active run always cancel the currently running job and restart it, because the newest scheduled trigger is given priority over any run that is still in the middle of executing.
  4. DThe single-active-run limit is fixed and cannot be changed, so to overlap runs the engineer must clone the job definition so that each separate copy contributes its own independent single active run on the same schedule.
  5. EBy default a job allows only a single active run at a time, so a scheduled trigger is skipped while a prior run is in progress; raising the maximum concurrent runs setting lets overlapping runs execute at the same time.
Answer & explanation

Correct answer: E

WHY E: A job runs a single active run at a time by default, so an overlapping schedule tick is skipped; increasing the maximum concurrent runs setting allows overlapping runs. WHY NOT A: Skipped triggers are not all queued and replayed; the default behavior is to skip while a run is active, not guarantee every interval. WHY NOT B: The default is a single active run, not unlimited; the serialization is by design and cluster size is not the cause. WHY NOT C: An in-progress run is not cancelled and restarted by a new schedule tick; the running job continues and the tick is skipped. WHY NOT D: The concurrency limit is configurable, so cloning the job is unnecessary to allow overlapping runs.

Take the full DE Associate practice test free →

Would you pass today?

This question is one of 45 in the free, timed Databricks Data Engineer Associate practice test. Take it and get a section-by-section score.

Start the free test →