Explanation:
Databricks maintains a rolling history of all job runs for up to 60 days. During this 60-day window, users have the ability to:
Why the other options are incorrect:
Reference: Azure Databricks Jobs monitoring documentation states that Databricks maintains job run history for up to 60 days and recommends exporting results if long-term preservation is required.
Ultimate access to all questions.
A data engineer needs to review the history of a specific job. What is the standard retention period for job run history in Databricks, and what capabilities are available during this timeframe?
A
The job run history is maintained indefinitely until the user manually deletes the records or exports them to an external location.
B
The job run history is retained for 30 days, during which time logs can be moved to DBFS or Amazon S3 via the workspace configuration.
C
The job run history is kept for 60 days, during which users can view completed runs in the UI or export notebook run results to HTML.
D
The job run history is retained for 60 days, after which logs are automatically moved to a managed archive within the control plane.
No comments yet.