Question 650
During an analytics reporting escalation at Stonehaven Logistics, the data engineering team identifies a Databricks issue: Several production jobs refer to different notebook revisions because each job was manually configured in the UI. The team reports that the correction is complete. Which result BEST verifies that the specific issue was resolved?
Explanation
Correct Answer
A deployment inventory shows consistent task definitions and an identified source version for each job. The observation provides evidence that the proposed fix (Define job configurations as version-controlled deployment resources using the supported workflow.) addressed the reported issue (Several production jobs refer to different notebook revisions because each job was manually configured in the UI.) for Stonehaven Logistics and its warehouse scheduling and shipping records. It verifies an observable outcome instead of relying only on a completed task ticket.
Incorrect Answers
The job executes from its configured run definition and produces the expected target table. This is suitable evidence for another condition (An engineer runs a production ingestion notebook manually each morning and no scheduled Lakeflow Job exists.) after a different response (Create a Lakeflow Job with the notebook task, appropriate compute, identity, and documented inputs.). For Stonehaven Logistics, it does not prove the required result: A deployment inventory shows consistent task definitions and an identified source version for each job.
A seeded task failure sends an actionable notification containing the job and run identity. This is suitable evidence for another condition (Operators discover failed nightly jobs only after downstream users complain because no failure notifications are configured.) after a different response (Configure Lakeflow Job notifications or alert delivery to the designated operations channel.). For Stonehaven Logistics, it does not prove the required result: A deployment inventory shows consistent task definitions and an identified source version for each job.
A simulated hang terminates within the approved time limit and surfaces its cause for response. This is suitable evidence for another condition (A task routinely hangs after an upstream API stops responding and the job occupies capacity indefinitely.) after a different response (Set a reasonable task timeout and failure path with controlled retry behavior.). For Stonehaven Logistics, it does not prove the required result: A deployment inventory shows consistent task definitions and an identified source version for each job.