The production version of an ETL notebook lives on the release branch of the team's GitHub repository. Today, a team member copies the notebook into the workspace by hand before each release, and last week's job ran a stale copy that missed two reviewed fixes. The next release must run exactly the reviewed code, with no manual steps. How should the notebook task be configured?
Reveal answer
Correct answer: Set the task's Source to the Git provider and point it at the notebook on the release branch
Reference: https://docs.databricks.com/aws/en/jobs/tasks/notebook
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 (C): Set the task's Source to the Git provider and point it at the notebook on the release branch
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.