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

Databricks Data Engineer Associate · free practice question

A data engineer wants an Auto Loader pipeline to run on a nightly schedule: each run should process every file accumulated since the previous run and then…

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 wants an Auto Loader pipeline to run on a nightly schedule: each run should process every file accumulated since the previous run and then stop, keeping compute cost low rather than staying always-on. Which trigger meets this requirement?

  1. ATrigger.Continuous, which keeps the stream running at very low latency and checkpoints frequently, then automatically pauses itself once the source directory is fully drained and resumes when new files later arrive.
  2. BTrigger.AvailableNow, which processes all currently available files across one or more rate-limited micro-batches and then stops the stream, so the job can be scheduled and compute shuts down between nightly runs.
  3. CTrigger.ProcessingTime set to a 24-hour interval, which wakes the always-on stream once each day to process new files while the underlying cluster stays provisioned continuously between the scheduled micro-batches.
  4. DTrigger.Once, the only trigger that stops after draining the source, which processes every file in a single micro-batch with no rate limiting and is therefore required here in place of the AvailableNow trigger.
  5. EThe default trigger with cloudFiles.maxFilesPerTrigger set to a high value, which processes all pending files in one pass and then terminates the query automatically as soon as that configured file count is reached.
Answer & explanation

Correct answer: B

WHY B: Trigger.AvailableNow processes all available files across multiple rate-limited micro-batches then stops, so scheduling it as a job lets compute terminate between runs — the cost-efficient batch pattern. WHY NOT A: Continuous stays always-on and does not pause when the directory drains, so compute keeps running. WHY NOT C: ProcessingTime is an always-on interval stream; the cluster stays provisioned, incurring continuous cost. WHY NOT D: Trigger.Once also stops, but it uses a single micro-batch with no rate limiting and is superseded by AvailableNow, so it is not required over it. WHY NOT E: maxFilesPerTrigger caps batch size but does not make a default stream stop; the query keeps running and waiting for new files.

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 →