A Lakeflow Job has six tasks — notebooks, one Python script, and one SQL file — that all live in the same GitHub repository on the release branch. Setting the repository and branch on every task is repetitive, and last month two tasks were accidentally pointed at different branches. How should the job's source be configured?
Reveal answer
Correct answer: Configure the repository and branch once as the job's Git source, and have tasks reference only paths relative to the repository root
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 (A): Configure the repository and branch once as the job's Git source, and have tasks reference only paths relative to the repository root
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.