An Auto Loader stream ingests JSON with an inferred schema. Upstream begins adding a new field. The team wants the pipeline to automatically pick up the new column rather than silently dropping it, accepting that the stream will restart once to apply the change. Which cloudFiles.schemaEvolutionMode should be configured?
Answer & explanation
Correct answer: C
WHY C: addNewColumns (the default when no explicit schema is provided) fails the stream once with UnknownFieldException on a new column, records it in the schema location, and resumes with the column included on the next start — exactly the 'auto pick up, one restart' behavior. WHY NOT A: rescue never evolves the schema; the new field would only ever live in _rescued_data, not as a real column. WHY NOT B: none silently drops new columns and never evolves — the opposite of the requirement. WHY NOT E: failOnNewColumns halts and requires manual schema intervention; it does not auto-add the column. WHY NOT D: strict is not a valid schemaEvolutionMode value.