Home / DE Associate practice test / Working with Lakeflow Jobs / Question

Databricks Data Engineer Associate · free practice question

A data engineer configures a Lakeflow Job with a file arrival trigger on an external location where an upstream system uploads a batch of many files over…

Exam-style question on Working with Lakeflow Jobs from the free DE Associate practice test, with the answer and a full explanation below.

Updated November 10, 2026

Working with Lakeflow Jobs

A data engineer configures a Lakeflow Job with a file arrival trigger on an external location where an upstream system uploads a batch of many files over several minutes. The engineer wants the job to run once per batch after uploads settle rather than once per file, and never to fire more often than every 10 minutes. Which configuration achieves this?

  1. ASwitch the job to a continuous trigger, because continuous mode inherently groups incoming files and starts exactly one run for each distinct upload batch while never firing more frequently than a ten-minute interval.
  2. BSet the cron schedule to fire every 10 minutes and remove the file arrival trigger, since a fixed time schedule is the only supported way to batch multiple arriving files and cap how often a file-driven job runs.
  3. CSet Wait after last change so the timer resets on each new file and the run begins only once uploads pause, and set Minimum time between triggers to 10 minutes to enforce a cooldown between two consecutive job runs.
  4. DEnable a table update trigger on the destination Delta table instead, because arrival-based batching can only be expressed by monitoring the target table for writes rather than by watching the source landing location.
  5. ESet Minimum time between triggers alone to 10 minutes, which both waits for the upload burst to finish and enforces the cooldown, because a single cooldown value already covers debouncing and rate limiting together.
Answer & explanation

Correct answer: C

WHY C: Wait after last change debounces the burst (the timer resets on each new file, so the run starts after uploads pause), and Minimum time between triggers enforces the 10-minute cooldown. WHY NOT A: A continuous trigger is an always-on run pattern, not a file-batch debouncer, and does not enforce a ten-minute cap on file-driven firing. WHY NOT B: A cron schedule is not a file arrival trigger; it fires on time regardless of whether a batch has actually landed or settled. WHY NOT E: Minimum time between triggers is only the cooldown; it does not debounce the burst, which is the separate Wait after last change setting. WHY NOT D: A table update trigger watches the destination table, not the source landing location, and does not batch source-file arrivals.

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 →