Home / DE Associate practice test / Data Ingestion and Loading / Question

Databricks Data Engineer Associate · free practice question

A data engineer sets up an Auto Loader stream with spark.readStream.format('cloudFiles') to ingest JSON files as they land in cloud storage. Which…

Exam-style question on Data Ingestion and Loading from the free DE Associate practice test, with the answer and a full explanation below.

Updated November 10, 2026

Data Ingestion and Loading

A data engineer sets up an Auto Loader stream with spark.readStream.format('cloudFiles') to ingest JSON files as they land in cloud storage. Which configuration lets Auto Loader process each incoming file exactly once, even across stream restarts?

  1. AProvide a checkpoint location and set cloudFiles.format to json; Auto Loader records ingested files in that checkpoint and skips them on later runs.
  2. BSet cloudFiles.format to json and enable force = true; Auto Loader compares file checksums on each micro-batch and reloads files whose bytes changed.
  3. CProvide the cloudFiles.format value alone; Auto Loader stores its list of processed files in the target Delta table's transaction log by default.
  4. DSet the trigger to Trigger.AvailableNow, which grants exactly-once processing across restarts; other triggers re-ingest each incoming file.
  5. EEnable cloudFiles.inferColumnTypes with a schema location; these options keep the processed-file registry, and the checkpoint stores schema history.
Answer & explanation

Correct answer: A

WHY A: Auto Loader is built on Structured Streaming and requires a checkpoint location plus a source format; it tracks processed files in that checkpoint (RocksDB), giving exactly-once ingestion across restarts.

WHY NOT B: There is no force option in Auto Loader (that belongs to COPY INTO), and exactly-once comes from file tracking, not checksum comparison.

WHY NOT C: File state lives in the checkpoint location you supply, not in the target table's transaction log.

WHY NOT D: AvailableNow controls when processing stops, not the exactly-once guarantee, which comes from checkpointing under any trigger.

WHY NOT E: inferColumnTypes and the schema location handle schema, not the processed-file registry, which is the checkpoint's job.

Take the full DE Associate practice test free →

Would you pass today?

This question is one of 45 in the free, timed Databricks Data Engineer Associate practice test. Take it and get a section-by-section score.

Start the free test →