Databricks-DE-Assoc Data Ingestion and Loading Practice Question
A data engineer is using Databricks Auto Loader to ingest JSON files from a directory. The stream is configured with `cloudFiles.schemaLocation` set to a specific path. The engineer notices that the stream fails when a new file contains an additional column. What is the most likely reason for the failure?
⚠ Common exam trap
The trap here is assuming that schema location issues or inference options cause failures on new columns, when the mode explicitly controls this behavior.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The `cloudFiles.schemaEvolutionMode` is set to `failOnNewColumns`.
Auto Loader's `schemaEvolutionMode` controls how new columns are handled. Setting it to `failOnNewColumns` causes the stream to fail when a new column is encountered, requiring manual intervention. To allow automatic schema evolution, the mode should be set to `addNewColumns`.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The `cloudFiles.inferColumnTypes` option is set to `false`, causing schema inference to fail.
Why it's wrong here
`inferColumnTypes` controls whether Auto Loader infers column types or treats all as strings. Setting it to `false` does not cause failures on new columns; it only affects type inference. The stream would still process new columns as strings, not fail.
- ✗
The `cloudFiles.useNotifications` option is disabled, so new files are not detected.
Why it's wrong here
`useNotifications` determines whether file notifications are used for discovery. If disabled, Auto Loader falls back to directory listing, which still detects new files. It does not cause schema-related failures. The issue is clearly about schema evolution.
- ✗
The schema location is not writable, so Auto Loader cannot update the schema.
Why it's wrong here
If the schema location is not writable, Auto Loader would fail to initialize or update the schema, but the error would occur immediately, not only when a new column appears. The described failure is specifically triggered by a new column, indicating a schema evolution issue.
- ✓
The `cloudFiles.schemaEvolutionMode` is set to `failOnNewColumns`.
Why this is correct
When `schemaEvolutionMode` is set to `failOnNewColumns`, Auto Loader will fail the stream if a new column is detected. This is a strict mode that requires manual schema updates. The engineer likely needs to change it to `addNewColumns` to allow automatic evolution.
About these practice questions
Courseiva writes every Databricks-DE-Assoc question from scratch — 276 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Databricks exam blueprint
This Databricks-DE-Assoc practice question is part of Courseiva's free Databricks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the Databricks-DE-Assoc exam.