SnowPro Core (COF-C03) · Free practice question 5 of 15
Recovering a truncated table with Time Travel
Your team accidentally ran TRUNCATE TABLE on a production table at 14:32. The table is in a standard (not transient) database and the account's DATA_RETENTION_TIME_IN_DAYS is 1. At 14:50 the same day, what is the fastest way to restore the data?
- A.Restore from an off-platform backup using SnowSQL.
- B.Issue `UNDROP TABLE` on the truncated table.
- C.Use `CREATE TABLE … AS SELECT … FROM <table> AT(OFFSET => -1080)` (1,080 seconds back) and swap the new table in.
- D.Open a Fail-Safe restore ticket with Snowflake Support.
Show answer and explanation
Correct answer: C. Use `CREATE TABLE … AS SELECT … FROM <table> AT(OFFSET => -1080)` (1,080 seconds back) and swap the new table in.
Why: Time Travel lets you query historical data within the retention window (1 day here). `AT(OFFSET => -seconds)` reads the table as of a point in time; CTAS into a replacement and swap. `UNDROP` is for dropped objects, not truncated ones. Fail-Safe is a Snowflake-administered 7-day recovery period accessed via support — slow, and only after Time Travel expires.
More free SnowPro Core (COF-C03) questions
- Micro-partition immutability
- SECURITYADMIN for user and role management
- Multi-cluster warehouses for concurrency
- Snowflake edition for extended Time Travel
- Types of internal stages
- File sizing for COPY INTO
- Query result cache
- Reader accounts for non-Snowflake consumers
- LATERAL FLATTEN on VARIANT arrays
- Streams and tasks for change data capture
- Clustering keys for partition pruning
- Network policies for IP allowlisting
- Zero-copy cloning for QA environments
- Snowpipe auto-ingest for low latency