A compliance feed must land in a table whose schema has to stay strictly stable — no automatic column additions. At the same time, the team cannot tolerate ingestion outages when the feed occasionally sends unexpected extra fields, and it wants those values preserved for later inspection. Which cloudFiles.schemaEvolutionMode setting satisfies all three requirements?

1. A. addNewColumns — new fields are merged into the table schema and the stream resumes automatically 💬 A
2. B. rescue — the schema never evolves, the stream never fails due to schema changes, and unexpected fields are recorded in the rescued data column ✓ B
3. C. failOnNewColumns — the stream stops whenever a new field appears and stays down until someone updates the schema or removes the file 💬 C
4. D. addNewColumnsWithTypeWidening — new fields are merged and compatible type changes are widened automatically 💬 D

Reveal answer

Correct answer: rescue — the schema never evolves, the stream never fails due to schema changes, and unexpected fields are recorded in the rescued data column

Reference: https://docs.databricks.com/aws/en/ingestion/cloud-object-storage/auto-loader/