Home / DE Professional practice test / Data Ingestion & Acquisition / Question

Databricks Data Engineer Professional · free practice question

A Structured Streaming job reads from Kafka using `.option('startingOffsets', 'latest')` and writes to a Delta sink with a checkpoint. After an incident, the…

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

Updated November 16, 2026

Data Ingestion & Acquisition

A Structured Streaming job reads from Kafka using .option('startingOffsets', 'latest') and writes to a Delta sink with a checkpoint. After an incident, the job is redeployed and unexpectedly reprocesses old Kafka data from the beginning. Holding the Kafka topic and code constant, which change most directly prevents this behavior in the future?

  1. AKeep startingOffsets='latest' and add endingOffsets='latest'; each run of the streaming query then reads the newest Kafka data and stops.
  2. BSet failOnDataLoss to false; the query then continues past missing offsets and skips reprocessing of older Kafka data after a redeployment.
  3. CSet kafka.group.id to a fixed value; Kafka then stores the committed offsets for the stream, and a redeployed query resumes from that group.
  4. DReuse the same persistent checkpointLocation across restarts; startingOffsets applies to a new query, and a restart resumes from the checkpoint.
Answer & explanation

Correct answer: D

WHY D: For Kafka Structured Streaming, the checkpoint is the durable source of truth for progress. startingOffsets is only used when starting a brand-new query; if the checkpoint is changed or deleted, the stream can start from the configured starting offsets (or earliest, depending on config) and reprocess old data. Keeping a stable checkpoint location is the direct fix.

WHY NOT A: endingOffsets is for batch reads, not a typical streaming configuration, and does not solve checkpoint loss.

WHY NOT C: Structured Streaming does not resume from Kafka consumer-group offsets. Setting kafka.group.id can cause interference between concurrently running queries using the same group ID and is recommended only with extreme caution; it is not a substitute for Structured Streaming checkpoints.

WHY NOT B: failOnDataLoss=false allows a query to continue despite missing Kafka data; it does not prevent replaying old offsets when checkpoint state is lost.

Take the full DE Professional practice test free →

Would you pass today?

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

Start the free test →