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

Databricks Data Engineer Associate · free practice question

A downstream reporting job must run only after new files actually arrive in a landing zone, which happens irregularly — sometimes several times an hour…

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 downstream reporting job must run only after new files actually arrive in a landing zone, which happens irregularly — sometimes several times an hour, sometimes not for a day. The team wants to avoid running (and paying for) the job on a fixed cadence when there is no new data. Which Lakeflow Jobs trigger best meets this requirement?

  1. AA scheduled cron trigger set to fire every five minutes, with logic inside the job that checks the landing zone and exits early on runs where no new files are present, so the empty batches finish quickly and cheaply.
  2. BA file arrival trigger, which starts the job only when new files land in the monitored storage location, so the job runs solely when there is genuinely fresh new data to process and never on an empty fixed cadence.
  3. CA continuous trigger, which keeps a cluster running around the clock polling the landing zone so that any file is picked up the instant it lands, regardless of how irregular the actual arrival pattern happens to be.
  4. DA manual, on-demand trigger, where an on-call engineer watches the landing zone and starts the job by hand each time a new batch of files shows up, ensuring the job runs only when data is actually present.
  5. EA table update trigger bound to an unrelated dimension table that happens to change on roughly the same irregular cadence, using its updates as a stand-in signal that new files have probably arrived in the zone.
Answer & explanation

Correct answer: B

WHY B: A file arrival trigger fires the job when new files appear in the monitored location — data-driven execution that avoids empty scheduled runs and matches the irregular arrival pattern exactly. WHY NOT A: A five-minute cron still launches and bills constantly regardless of data; filtering inside wastes compute on empty runs. WHY NOT C: A continuous trigger keeps compute running 24/7 — the costly outcome the team wants to avoid. WHY NOT D: Manual triggering is not viable for irregular, frequent arrivals and depends on a human being available. WHY NOT E: A table update trigger on an unrelated table is an unreliable proxy for actual file arrival.

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 →