SnowPro Advanced: Architect — Question 50

An Architect has been asked to clone schema STAGING as it looked one week ago, Tuesday June 1st at 8:00 AM, to recover some objects.
The STAGING schema has 50 days of retention.
The Architect runs the following statement:
CREATE SCHEMA STAGING_CLONE CLONE STAGING at (timestamp => '2021-06-01 08:00:00');
The Architect receives the following error: Time travel data is not available for schema STAGING. The requested time is either beyond the allowed time travel period or before the object creation time.
The Architect then checks the schema history and sees the following:

CREATED_ON|NAME|DROPPED_ON -
2021-06-02 23:00:00 | STAGING | NULL
2021-05-01 10:00:00 | STAGING | 2021-06-02 23:00:00
How can cloning the STAGING schema be achieved?

Answer options

• A. Undrop the STAGING schema and then rerun the CLONE statement.
• B. Modify the statement: CREATE SCHEMA STAGING_CLONE CLONE STAGING at (timestamp => '2021-05-01 10:00:00');
• C. Rename the STAGING schema and perform an UNDROP to retrieve the previous STAGING schema version, then run the CLONE statement.
• D. Cloning cannot be accomplished because the STAGING schema version was not active during the proposed Time Travel time period.

Correct answer: C

Explanation

The correct answer is C because it allows the Architect to restore the previous version of the STAGING schema before it was dropped, thus enabling a successful cloning operation. Option A does not address the time travel issue, while option B attempts to clone an inactive schema version. Option D incorrectly assumes that cloning is entirely impossible, when it can be achieved by restoring the schema first.