Reviewed by Aditya Kumar · Last reviewed 2026-03-24
**Architectural Logic**: Time Travel enables historical query and recovery—retention affects cost. **Mechanism**: Query at point: `AT(OFFSET => -3600)` or `AT(TIMESTAMP => '...')`. Restore: `UNDROP TABLE`. Clone: `CREATE TABLE t_clone CLONE t AT(OFFSET => -86400)`....
Architectural Logic: Time Travel enables historical query and recovery—retention affects cost. Mechanism: Query at point: AT(OFFSET => -3600) or AT(TIMESTAMP => '...'). Restore: UNDROP TABLE. Clone: CREATE TABLE t_clone CLONE t AT(OFFSET => -86400). Retention: 1 day default; up to 90 days for enterprise. Use: Debugging; recovery; historical analysis. Scalability: Retention period limits. Cost: Storage for historical data; longer retention = more cost. Best Practice: Use for accidental delete recovery; clone before major changes; document retention policy.
Red Flag: Relying on Time Travel for backup—supplement with external backup. Pro-Move: Mention retention tiers; clone before risky operations; FAILSAFE for extended recovery; document policy per table.
According to DataEngPrep.tech, this is one of the most frequently asked SQL interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.