Answer-first summary for fast verification
Answer: Job run history is maintained for 60 days, during which notebook run results can be exported to HTML for permanent storage.
Databricks maintains job run metadata and output history for a maximum of 60 days. Within this window, users can access the **Runs** tab to view completed tasks and use the **Export to HTML** feature to save a copy of the notebook output. **Analysis of incorrect options:** * **30 days:** This timeframe is common for Delta Lake's default log retention (`logRetentionDuration`), but does not apply to job runs. * **Indefinite/Archive:** Records are automatically and permanently deleted after 60 days; Databricks does not offer an automated internal archive for these logs. * **90 days/Run ID reuse:** Databricks does not use a 90-day window, and Run IDs are unique identifiers that are not reused to reset retention periods.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
Which of the following statements correctly identifies the Databricks retention policy for job run history?
A
Job run history is stored indefinitely until the user manually deletes the records or exports the logs.
B
Job run history is maintained for 60 days, during which notebook run results can be exported to HTML for permanent storage.
C
Job run history is kept for 30 days, aligning with the default retention period for Delta Lake transaction logs.
D
Job run history is retained for 60 days, after which metadata and logs are automatically transitioned to a long-term archive.
E
Job run history is retained for 90 days or until the specific Run ID is recycled by the system.
No comments yet.