A data engineer needs a Delta table to support time travel queries going back 60 days. The default VACUUM retention is 7 days. Which combination of table property settings guarantees that both data files and transaction logs are retained long enough to satisfy this requirement?
Answer & explanation
Correct answer: C
WHY C: Two independent settings control time travel retention. delta.deletedFileRetentionDuration sets the minimum age before VACUUM removes data files, so it has to be at least 60 days to keep the files that older versions need. delta.logRetentionDuration controls how long transaction log entries are kept (30 days by default) and also has to be extended to at least 60 days. Both are required.
WHY NOT A: logRetentionDuration controls the transaction log, not the underlying data files; without extending deletedFileRetentionDuration, VACUUM still removes data files after 7 days.
WHY NOT B: Disabling the retention check and passing RETAIN is risky and per-session: nothing is persisted on the table, it does not protect against a later VACUUM run with the default threshold, and it does not extend log retention.
WHY NOT D: The transaction log is not retained indefinitely by default; its default retention is 30 days through logRetentionDuration, which has to be extended for 60-day time travel.
WHY NOT E: delta.timeTravel.maxVersionAge is not a real Delta Lake table property; retention is controlled through deletedFileRetentionDuration and logRetentionDuration.