A Lakeflow Job normally finishes in about twenty five minutes and feeds a report published at 07:00. Reviewing the run history, a team finds several runs in recent weeks that took over an hour but still succeeded, and nobody was told until the report was late. The team wants to be notified while a run is still going once it passes forty minutes, and it does not want a slow run cancelled, because a late report is preferable to no report. Which configuration meets the requirement?
- ASet a timeout of forty minutes on the job and send a notification when it is exceeded, so the team learns about the slow run as soon as the threshold is passed.
- BSet a duration warning threshold of forty minutes on the job and send a notification when it is exceeded, leaving the run to continue to completion. Correct
- CAdd a notification on run failure to the job, so that any run departing from its usual duration is reported to the team while it is still executing.
- DAdd a retry policy of two attempts to the job, so that a slow attempt is abandoned and a fresh attempt of the usual duration produces the report on time.
Why A is wrong: A timeout does notify at the threshold, which makes it look like the same control, but it also cancels the run, so the report the team wanted late would never be produced.
Why B is correct: A warning threshold raises a notification while the run continues, which is exactly the split the team asked for between being told early and letting the slow run finish.
Why C is wrong: Failure notifications are already common practice and cost nothing to add, but these runs succeed, so the condition never fires and the long runs stay invisible.
Why D is wrong: Retries do help a run that fails on a transient fault, but they are not triggered by duration, and abandoning work in progress would push the report later rather than earlier.