A compliance team asks a data engineer to keep a record of every run of a nightly job for the past six months, so run durations can later be compared against older baselines. What should the engineer do?
Choose an answer to check it. Afterward, select any option to review its explanation.
Tempting because the Runs tab is where history is browsed, but it does not keep runs forever: the history window is 60 days, so most of a six-month record would be lost.
Maximum concurrent runs controls how many runs of the job may execute at the same time (a Queued-phase cause), not how long finished runs are retained.
Filtering by Run ID helps find a specific run that is still retained, such as a one-time runs/submit run, but it cannot bring back runs that have aged out of history.
Databricks keeps job run history for up to 60 days, so a six-month baseline only exists if results are exported before older runs expire. Exporting is the documented way to persist runs.
id q5b9510ed2f