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?
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.