A team must load JSON booking updates from a Unity Catalog volume with COPY INTO. The producer occasionally adds new fields, so the files do not all share the same schema, and the team wants new fields to appear in the target table automatically instead of causing failures. The target table has not been created yet. Which approach meets these requirements?
Reveal answer
Correct answer: Create an empty table without declaring columns, then run COPY INTO with 'mergeSchema' = 'true' in FORMAT_OPTIONS and COPY_OPTIONS
Reference: https://docs.databricks.com/aws/en/ingestion/cloud-object-storage/copy-into
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): Create an empty table without declaring columns, then run COPY INTO with 'mergeSchema' = 'true' in FORMAT_OPTIONS and COPY_OPTIONS
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.