A task in a production Lakeflow Job got stuck in an infinite loop over the weekend. Nobody was watching, and the job stayed in the running state for three days, holding compute and blocking downstream pipelines. The team wants a stuck run like this to be stopped and marked as failed automatically. What should they configure?
Reveal answer
Correct answer: A Timeout setting on the job or the task, so that exceeding the limit stops the run with a Timed Out status
Reference: https://docs.databricks.com/aws/en/jobs/configure-job
Noos Visual & Functional Recognition
The “Sphere Embrace”: how Noos embraces top contributors without a childish mascot.
In neurobiology, glial cells wrap axons in myelin sheaths to accelerate neural impulses. On Noos, as your explanations earn accelerations and enter the Wiki Synthesis, the Noos Sphere wraps your Identicon with Keplerian orbits and two quantum nodes on its shoulders.
Pure 5×5 geometric Identicon (no personal photo, zero tracking). 1px frame.
Single dashed orbit with 1 bright polar node at the apex. Highlights those who passed the exam.
Two coaxial ellipses (±35°) wrap the avatar with two lateral nodes.
The Sphere Embrace: The Noos Sphere hood wraps the top of the Identicon and rests two luminous nodes on its shoulders.
02 — The Myelin Layer · Canonical Discussion
Where the exam tries to trick you — and how those who passed solved it.
contributed to this question
No community synthesis consolidated for this question yet. Below is the verifiable official starting point — if you passed the exam, open the option dissection.
Official Answer (D): A Timeout setting on the job or the task, so that exceeding the limit stops the run with a Timed Out status
Contribute to this Question
✦ I PASSED!Peer contributions
No public contribution yet. Be the first who passed to explain why the distractors trick candidates — your contribution builds your Orbital Sheath.