
Explanation:
Correct. In Databricks, if a task fails, there is no automatic rollback of completed operations. Any writes or changes made before the failure remain intact. Dependent tasks may or may not run, depending on the job's configuration, but the scenario specifies they still needed to be run, implying they would proceed if possible.
Ultimate access to all questions.
No comments yet.
In a Databricks job, the task clean_data failed, but tasks dependent on clean_data still needed to be executed. What is the correct outcome in this scenario?
A
All tasks preceding clean_data will be rolled back due to its failure.
B
Only the successful operations of the failed clean_data task will be rolled back.
C
No rollback occurs; any completed operations, such as writes to disk or Delta table before clean_data failed, remain unchanged.
D
Every task that depends on clean_data will fail.
E
Tasks dependent on clean_data will proceed according to the execution plan.