0
0
Snowflakecloud~10 mins

Why Time Travel enables data recovery in Snowflake - Test Your Understanding

Choose your learning style9 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to query data as it existed 1 hour ago using Time Travel.

Snowflake
SELECT * FROM sales_data AT (OFFSET => [1]);
Drag options to blanks, or click blank then click option'
A60
B3600
C1800
D7200
Attempts:
3 left
💡 Hint
Common Mistakes
Using minutes instead of seconds for OFFSET.
Using a negative number for OFFSET.
2fill in blank
medium

Complete the code to restore a dropped table using Time Travel.

Snowflake
UNDROP TABLE [1];
Drag options to blanks, or click blank then click option'
Asales_data
Bcustomers
Corders
Dinventory
Attempts:
3 left
💡 Hint
Common Mistakes
Trying to undrop a table that was never dropped.
Using a wrong table name.
3fill in blank
hard

Fix the error in the query to select data from 2 hours ago using Time Travel.

Snowflake
SELECT * FROM orders AT (OFFSET => [1]);
Drag options to blanks, or click blank then click option'
A7200
B-7200
C120
D3600
Attempts:
3 left
💡 Hint
Common Mistakes
Using negative OFFSET value.
Using minutes instead of seconds.
4fill in blank
hard

Fill both blanks to query the 'customers' table as it was 30 minutes ago using Time Travel.

Snowflake
SELECT * FROM customers AT ([1] => [2]);
Drag options to blanks, or click blank then click option'
AOFFSET
BTIMESTAMP
C1800
D3600
Attempts:
3 left
💡 Hint
Common Mistakes
Using TIMESTAMP keyword with seconds value.
Using 3600 seconds for 30 minutes.
5fill in blank
hard

Fill all three blanks to restore the 'inventory' table dropped recently and query its state 15 minutes ago.

Snowflake
UNDROP TABLE [1]; SELECT * FROM [2] AT ([3] => 900);
Drag options to blanks, or click blank then click option'
Ainventory
Bsales_data
COFFSET
DTIMESTAMP
Attempts:
3 left
💡 Hint
Common Mistakes
Using different table names for undrop and select.
Using TIMESTAMP instead of OFFSET.