Question 35
Domain 9: Debugging and DeployingA multi-task workflow failed in a downstream transform after upstream ingestion tasks had already succeeded. What is the most efficient next step?
Correct answer: C
Explanation
Job repairs are the stated remediation for failed runs: the guide says to “remediate the failed job runs with job repairs and parameter overrides.” Repair run is efficient because it reruns only “failed and skipped tasks where appropriate,” instead of re-executing the successful upstream ingestion tasks.
Why each option is right or wrong
A. Delete the job and recreate it from scratch
Jobs are repaired, not deleted and rebuilt, when only part of a workflow fails.
B. Always rerun the full workflow from the beginning
Job repairs rerun failed and skipped tasks where appropriate, not every task from the start.
C. Use Repair run to rerun only failed and skipped tasks where appropriate
Databricks Jobs documentation states that a repair run reruns only the failed and skipped tasks in a multi-task workflow, which is the most efficient remediation after a downstream task failure when upstream ingestion has already succeeded. That avoids re-executing Task A and any other successful tasks, and aligns with the Jobs/Workflows repair mechanism referenced in the exam guide’s troubleshooting objective.
D. Convert the workflow into a dashboard query
Dashboard queries are for analysis and monitoring, not for rerunning failed workflow tasks.