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

Databricks Data Engineer Associate · free practice question

In a Lakeflow Job, a notification task must run after three upstream tasks regardless of whether they succeed or fail, so alerts are always sent. Which…

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

In a Lakeflow Job, a notification task must run after three upstream tasks regardless of whether they succeed or fail, so alerts are always sent. Which task-level condition implements 'run once all upstream tasks reach a terminal state, success or failure'?

  1. ASet the task's run-if condition to ALL_SUCCESS, the default, which is documented to also run the task when an upstream dependency fails, so notifications are still sent even on an upstream failure.
  2. BSet the task's run-if condition to NONE_FAILED, which runs the notification task only when at least one of the three upstream dependencies has actually failed during the current run of the job.
  3. CRemove all dependencies from the notification task and give it its own separate schedule ten minutes later, which reliably runs it after the three upstream tasks have finished all of their work.
  4. DConfigure the run-if condition as AT_LEAST_ONE_SUCCESS, which runs the notification task whether the upstream tasks ultimately succeed or fail so that alerts are always delivered to the team on time.
  5. ESet the task's run-if condition to ALL_DONE, so it runs once every upstream dependency has reached a terminal state — success, failure, or skipped — which is exactly the always-run alert behavior.
Answer & explanation

Correct answer: E

WHY E: ALL_DONE runs the task once all dependencies have reached a terminal state — success, failure, or skipped — which is exactly 'always run' behavior. WHY NOT A: ALL_SUCCESS (the default) runs only if all upstream tasks succeed, so it is skipped on failure. WHY NOT B: NONE_FAILED runs only when nothing failed — the opposite of covering failures. WHY NOT C: A time-offset schedule is unreliable (durations vary) and decouples the task from its dependencies. WHY NOT D: AT_LEAST_ONE_SUCCESS requires a success and would be skipped if all upstream tasks fail.

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 →