Databricks-DE-Assoc Data Ingestion and Loading Practice Question
A data engineer is using Auto Loader to ingest data from a Kafka topic into a Delta table. The engineer wants to ensure that the ingestion handles late-arriving data and provides exactly-once semantics. Which combination of features should the engineer use?
⚠ Common exam trap
The trap here is mixing Auto Loader or COPY INTO with Kafka, as those are for file-based sources, and overlooking the need for watermarking to handle late data.
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
✓
Structured Streaming with Kafka source, watermarking, and checkpointing
For Kafka ingestion with exactly-once semantics and late data handling, Structured Streaming with the Kafka source, watermarking, and checkpointing is the correct approach. Checkpointing ensures exactly-once by tracking offsets, and watermarking allows processing of late-arriving data up to a specified threshold.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Auto Loader with cloudFiles.useNotifications = true and checkpointing
Why it's wrong here
Auto Loader's file notification mode is designed for file-based sources like cloud storage, not for Kafka. Kafka ingestion is typically handled by Structured Streaming's Kafka connector. Using Auto Loader with Kafka is not supported. Therefore, this combination does not work for Kafka ingestion.
- ✓
Structured Streaming with Kafka source, watermarking, and checkpointing
Why this is correct
Structured Streaming provides a Kafka connector that supports exactly-once semantics via checkpointing and offset management. Watermarking allows handling late-arriving data by specifying a threshold for how late data can arrive. This combination is the correct approach for ingesting from Kafka with exactly-once and late data handling.
- ✗
COPY INTO with Kafka connector and FORCE = true
Why it's wrong here
COPY INTO does not support Kafka as a source. It is designed for file-based ingestion from cloud storage. The FORCE option is irrelevant here. Therefore, this option is invalid for Kafka ingestion and does not provide the required semantics.
- ✗
Delta Live Tables with Kafka source and APPLY CHANGES
Why it's wrong here
Delta Live Tables can ingest from Kafka using the Kafka connector, and APPLY CHANGES is used for change data capture. However, APPLY CHANGES is not directly related to handling late-arriving data or exactly-once semantics; those are handled by Structured Streaming checkpointing and watermarking. While DLT simplifies pipeline management, the core features for late data and exactly-once are still watermarking and checkpointing, which are not explicitly mentioned here.
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.