A data analyst attempts to run SELECT * FROM orders TIMESTAMP AS OF '2025-10-01' in January 2026, targeting a version from roughly 90 days ago, and receives an error. What is the most likely cause?
Answer & explanation
Correct answer: D
WHY D: VACUUM deletes data files that are no longer referenced by the current table version and are older than the deletedFileRetentionDuration threshold (default 7 days). Once those files are gone, time travel to any version that required them fails. With a 90-day-old target and default settings, VACUUM would have long since removed those files.
WHY NOT A: Schema evolution does not block time travel to versions from before the change; Delta Lake keeps schema history alongside data history.
WHY NOT C: Transaction log retention is governed by logRetentionDuration (default 30 days), not by a fixed count of 30 entries. Even so, 90 days still exceeds the 30-day default.
WHY NOT B: Unity Catalog has no privilege expiration mechanism tied to logRetentionDuration; SELECT on a table does not lapse for older versions.
WHY NOT E: TIMESTAMP AS OF accepts date strings like '2025-10-01', and the @ syntax also supports date string forms, so VERSION AS OF is not required.