Answer-first summary for fast verification
Answer: The job run history is retained for 60 days, during which time you can export notebook run results as HTML.
Databricks retains a rolling history of all job runs for **up to 60 days**. Within this period, users can view completed runs in the Jobs UI, retrieve logs via the Jobs API, or export notebook run results as HTML. **Why other options are incorrect:** * **30 days** is an incorrect timeframe; the actual limit is 60 days. * Databricks does **not** keep history indefinitely; it is purged after the 60-day window. * Databricks does **not** automatically archive logs; they are permanently removed unless the user has proactively exported them or configured cluster log delivery to an external location (like S3, ADLS, or DBFS).
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
In Databricks, what is the default retention period for job run history, and what actions can be taken before the records expire?
A
The job run history is retained for 30 days, during which you can configure automated migration of logs to DBFS or S3.
B
The job run history is kept for 60 days, after which the logs are automatically archived to long-term cloud storage.
C
The job run history is kept until the user manually exports or deletes the logs from the workspace.
D
The job run history is retained for 60 days, during which time you can export notebook run results as HTML.
No comments yet.