A developer dropped a permanent table by mistake roughly two hours ago, then noticed that another table with the same name was never created in its place. The table had default Time Travel retention. What is the simplest way to bring the dropped table back?
- ARecreate the table from its DDL and reload it from yesterday's external files, since a dropped permanent table cannot be brought back through any built-in Snowflake recovery command
- BOpen a Fail-safe support request with Snowflake to retrieve the dropped table, because dropping a permanent object moves its data straight into Fail-safe and bypasses Time Travel
- CClone the table from its pre-drop state with CREATE TABLE restored CLONE old_table, naming the dropped object as the clone source to rebuild it under a new table name
- DRun UNDROP TABLE on the dropped table, which restores it from Time Travel because the drop happened within the table's retention period and no new object reused the name Correct
Why A is wrong: Rebuilding from files is tempting when a table seems gone, but Snowflake can restore a recently dropped table directly, so this slower manual rebuild is unnecessary.
Why B is wrong: A drop within retention is recoverable through Time Travel, not Fail-safe; raising a support case is slower and unnecessary while UNDROP can still restore it.
Why C is wrong: Cloning needs an existing source object, but the table is dropped, so this CLONE statement cannot resolve its source and will fail rather than restore it.
Why D is correct: UNDROP restores a dropped object from Time Travel while it is in the retention window, and with the name still free the original table comes back intact.