Home / Data Analyst practice test / Executing queries using Databricks SQL and Databricks SQL Warehouses / Question

Databricks Data Analyst Associate · free practice question

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…

Exam-style question on Executing queries using Databricks SQL and Databricks SQL Warehouses from the free Data Analyst practice test, with the answer and a full explanation below.

Updated November 10, 2026

Executing queries using Databricks SQL and Databricks SQL Warehouses

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?

  1. AThe table schema was altered after October 2025, and Delta Lake schema evolution drops backward compatibility with earlier versions, which blocks time travel to any version that predates the schema change
  2. BUnity Catalog expires the SELECT privilege on historical versions once they fall outside the logRetentionDuration window, and the analyst's access to versions older than 30 days has lapsed for this table
  3. CTime travel in Databricks SQL is limited to the last 30 transaction log entries, and more than 30 writes have occurred on the table after October 2025, leaving the log without the version for that timestamp
  4. DThe data files for the October 2025 version were removed by VACUUM; with the default deletedFileRetentionDuration of 7 days, versions whose files are older than that threshold become unreadable once VACUUM has run
  5. EThe TIMESTAMP AS OF clause rejects date string literals such as '2025-10-01'; the query needs VERSION AS OF followed by the integer transaction log version number that corresponds to the target date
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.

Take the full Data Analyst practice test free →

Would you pass today?

This question is one of 45 in the free, timed Databricks Data Analyst Associate practice test. Take it and get a section-by-section score.

Start the free test →