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