Databricks-DE-Assoc Working with Lakeflow Jobs Practice Question
A data engineer is setting up a Lakeflow Job that runs a notebook task. The engineer needs the task to always execute even if the upstream task in the workflow fails. Which configuration should be applied to the dependent task's condition?
⚠ Common exam trap
The trap here is assuming that "At least one succeeded" guarantees execution even when all upstream tasks fail, but it does not run if no upstream task succeeds.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Set the task's "Run if" condition to "All done".
In Lakeflow Jobs, task dependencies use "Run if" conditions to control execution based on upstream task states. "All done" ensures the task runs after all dependencies finish, regardless of success or failure. This is the only condition that satisfies the requirement to always execute, making it suitable for tasks that must run unconditionally, such as cleanup or alerting steps.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Set the task's "Run if" condition to "All done".
Why this is correct
"All done" causes the task to execute after all upstream dependencies have reached a terminal state, whether they succeeded or failed. This guarantees the task runs regardless of upstream outcomes, which directly fulfills the requirement to always execute even when a preceding task fails. It is the correct choice for cleanup or notification tasks that must run unconditionally.
- ✗
Set the task's "Run if" condition to "All succeeded".
Why it's wrong here
Selecting "All succeeded" means the task runs only when every upstream dependency completed without error. If any upstream task fails, this condition evaluates to false and the dependent task is skipped. This is the default behavior for dependent tasks and does not satisfy the requirement to run regardless of upstream failure.
- ✗
Set the task's "Run if" condition to "At least one failed".
Why it's wrong here
"At least one failed" runs the task only when one or more upstream dependencies fail. While it ensures execution after a failure, it does not run the task when all upstream tasks succeed. The scenario requires the task to always execute, so this condition is too narrow and would skip the task in successful runs.
- ✗
Set the task's "Run if" condition to "At least one succeeded".
Why it's wrong here
"At least one succeeded" triggers the task when one or more upstream dependencies complete successfully, even if others fail. However, if all upstream tasks fail, the condition is not met and the task will not run. The requirement is to run the task unconditionally, so this condition still leaves a failure scenario where the task is skipped.
About these practice questions
One of 276 original Databricks-DE-Assoc practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Databricks exam blueprint
This Databricks-DE-Assoc practice question is part of Courseiva's free Databricks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the Databricks-DE-Assoc exam.