Snowflake ADA-C01 Exam - Topic 4 Question 39 Discussion

Actual exam question for Snowflake's ADA-C01 exam

Question #: 39
Topic #: 4

A user accidentally truncated the data from a frequently-modified table. The Administrator has reviewed the query history and found the truncate statement which was run on 2021-12-12 15:00 with query ID 8e5d0ca9-005e-44e6-b858-a8f5b37c5726. Which of the following statements would allow the Administrator to create a copy of the table as it was exactly before the truncated statement was executed, so it can be checked for integrity before being inserted into the main table?

ACREATE TABLE RESTORE_TABLE CLONE CURRENT_TABLE BEFORE (timestamp => '2021-12-12 00:00');

BSELECT * FROM CURRENT_TABLE before (statement => '8e5d0ca9-005e-44e6-b858-a8f5b37c5726');

CINSERT INTO CURRENT_TABLE SELECT * FROM CURRENT_TABLE before (statement => '8e5d0ca9-005e-44e6-b858-a8f5b37c5726');

DCREATE TABLE RESTORE_TABLE CLONE CURRENT_TABLE before (statement => '8e5d0ca9-005e-44e6-b858-a8f5b37c5726');

Show Suggested Answer

Suggested Answer: D

Scenario:

A TRUNCATE command was accidentally run on a frequently modified table.

Query ID and timestamp are known.

Goal: restore a copy of the table as it existed right before the problematic statement, without affecting the current table.

Why Option D is Correct:

sql

CopyEdit

CREATE TABLE RESTORE_TABLE CLONE CURRENT_TABLE

BEFORE (STATEMENT => '8e5d0ca9-005e-44e6-b858-a8f5b37c5726');

This uses Zero-Copy Cloning + Time Travel.

The BEFORE (STATEMENT => ...) clause restores the exact state of the table before the TRUNCATE ran.

Creating a clone ensures the original table remains untouched for integrity checks before merging data back.

Why Others Are Incorrect:

A . BEFORE (timestamp => '2021-12-12 00:00')

Wrong timestamp: that's 15 hours before the truncate happened. Too early; may lose needed updates.

B . SELECT * FROM CURRENT_TABLE before (statement => ...)

Syntax is invalid: SELECT can't use BEFORE (STATEMENT => ...) directly like this.

C . INSERT INTO CURRENT_TABLE SELECT * FROM CURRENT_TABLE before (statement => ...)

Same syntax issue. Also risky --- directly inserting into the original table without validating the data first.

SnowPro Administrator Reference:

Cloning with Time Travel

Time Travel with Statement ID

by Lavonne at Jul 08, 2025, 10:33 AM

Limited Time Offer

25%

Off

Get Premium ADA-C01 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Sherron

4 months ago

Wait, can you really clone a table like that? Sounds too easy.

upvoted 0 times

...

Selene

4 months ago

A is totally wrong, can't use a timestamp like that!

upvoted 0 times

...

Leslee

4 months ago

Option D seems right, it uses the statement ID.

upvoted 0 times

...

Jesus

4 months ago

I think B is better, it directly references the statement.

upvoted 0 times

...

Laurel

4 months ago

Not sure about D, I feel like it might miss some data nuances.

upvoted 0 times

...

Rasheeda

5 months ago

I’m leaning towards option D, but I’m not confident about the syntax. It’s tricky with all these variations!

upvoted 0 times

...

Nelida

5 months ago

I feel like option A might be incorrect because it uses "BEFORE" with a timestamp, which seems off to me.

upvoted 0 times

...

Theresia

5 months ago

I remember practicing a similar question where we had to restore data, but I can't recall if we used "CLONE" or "SELECT" for that.

upvoted 0 times

...

Jerrod

5 months ago

I think option D sounds familiar, but I'm not entirely sure if "before" is the right keyword to use there.

upvoted 0 times

...

Ronny

6 months ago

This is a good test of our database management skills. I'll need to think through the implications of each option carefully before making a decision.

upvoted 0 times

...

Lyndia

6 months ago

I'm feeling pretty confident about this one. I think option D is the way to go - it looks like the most straightforward way to create a clone of the table before the truncation.

upvoted 0 times

...

Suzi

6 months ago

Okay, I think I've got a strategy for this. The key is to find the query that truncated the table and use that to restore the data. Let me double-check the options.

upvoted 0 times

...

Gilma

6 months ago

Hmm, I'm a bit confused by the wording here. I'll need to make sure I understand exactly what the question is asking before I choose an answer.

upvoted 0 times

...

Anisha

6 months ago

This looks like a tricky one. I'll need to carefully read through the options and think about the best way to restore the table to its pre-truncated state.

upvoted 0 times

...