ARA-C01 · Question #7
A company has a table with that has corrupted data, named Data. The company wants to recover the data as it was 5 minutes ago using cloning and Time Travel. What command will accomplish this?
The correct answer is C. CREATE TABLE Recover_Data CLONE Data AT(OFFSET => -60*5);. The correct Snowflake syntax for cloning a table to a historical point in time is: CREATE TABLE <new_name> CLONE <source> AT(OFFSET => <seconds>). In option C, OFFSET => -605 evaluates to -300 seconds (5 minutes), which is correct. The CLONE keyword comes after the new table name
Question
A company has a table with that has corrupted data, named Data. The company wants to recover the data as it was 5 minutes ago using cloning and Time Travel. What command will accomplish this?
Options
- ACREATE CLONE TABLE Recover_Data FROM Data AT(OFFSET => -60*5);
- BCREATE CLONE Recover_Data FROM Data AT(OFFSET => -60*5);
- CCREATE TABLE Recover_Data CLONE Data AT(OFFSET => -60*5);
- DCREATE TABLE Recover Data CLONE Data AT(TIME => -60*5);
How the community answered
(29 responses)- A3% (1)
- B3% (1)
- C93% (27)
Explanation
The correct Snowflake syntax for cloning a table to a historical point in time is: CREATE TABLE <new_name> CLONE <source> AT(OFFSET => <seconds>). In option C, OFFSET => -605 evaluates to -300 seconds (5 minutes), which is correct. The CLONE keyword comes after the new table name, and AT() with OFFSET uses negative seconds relative to the current time. Option A uses CREATE CLONE TABLE, which is not valid syntax. Option B uses CREATE CLONE, which is also invalid - the correct keyword order requires TABLE between CREATE and the table name. Option D has a space in the table name (Recover Data) which makes it invalid SQL, and uses TIME => instead of OFFSET => - OFFSET takes seconds, while TIMESTAMP would use a timestamp literal, not an arithmetic expression like -605.
Topics
Community Discussion
No community discussion yet for this question.