A complex batch ETL join stage spills over 40 GB of shuffle data to local disk on every nightly run. The query cannot be redesigned this quarter, so the team wants a compute-level change that reduces the spill without touching the code. Which change follows the documented guidance?
Reveal answer
Correct answer: Use instances with more memory, or fewer and larger workers, so more of the shuffle fits before spilling
Reference: https://docs.databricks.com/aws/en/optimizations/spark-ui-guide/
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): Use instances with more memory, or fewer and larger workers, so more of the shuffle fits before spilling
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.