Snowflake Storage and Protection: 15%

A year old database has DATA_RETENTION_TIME_IN_DAYS set to 90 days. The

DATA_RETENTION_TIME_IN_DAYS is reset to 30 days. What happens to the data stored in time travel
older than 30 days for this database?

MC

• Reducing the number of days in DATA_RETENTION_TIME_IN_DAYS on a database is not allowed.

• All data in time travel for this database will be deleted and new changes to the database will be
kept for 30 days in time travel

• All current time travel data for this database will be kept for 90 days but new database changes
will be kept for 30 days.

• All data in time travel older than 30 days for this database will be deleted.

For active data modified after the retention period is reduced, the new shorter period applies.

For data that is currently in Time Travel:If the data is still within the new shorter period, it remains in
Time Travel.If the data is outside the new period, it moves into Fail-safe.For example, if you have a table
with a 10-day retention period and you decrease the period to 1-day, data from days 2 to 10 will be
moved into Fail-safe, leaving only the data from day 1 accessible through Time Travel.

When a database or schema is cloned. What object is not cloned?

MC

• External Stages

• Stored Procedures

• Pipes

• Internal Stages

• Sequences

Currently, when a database or schema that contains source tables and streams
is cloned, any unconsumed records in the streams (in the clone) are
inaccessible. This behavior is consistent with Time Travel for tables. If a table is
cloned, historical data for the table clone begins at the time/point when the clone
was created.
Which is the correct syntax to disable fail safe on a table?

MC

• By default, fail safe is disabled on a table.

• ALTER TABLE DROP FAILSAFE;

• Fail safe can not be disabled on a table.

• ALTER TABLE SET ENABLE_FAILSAFE = FALSE;

• ALTER TABLE SET FAILSAFE_DAYS = 0;

A DBA accidentally RUNS a CREATE OR REPLACE TABLE XYZ… which drops the XYZ table and recreates
it.The DBA makes a clone of the XYZ table called XYZ_Cloned with a BEFORE command retrieving the
original data before the CREATE OR REPLACE was run.The DBA drops the accidentally created new XYZ
and renames the XYZ_CLONED to XYZ. Later, another DBA tries to run a SELECT using the AT command
on the XYZ table to retrieve the data from last week and gets an error message that the data from last
week is gone. Why?

MC

• When the DBA made the clone from the original data, it deleted the time travel information
since it wasn’t needed any longer.

• Since the table was cloned, the second DBA doesn’t have access to the time travel data.

• The CLONE operation created a new table from the original data and the new table only has
time travel since the new table was created.

• The TABLE RENAME command drops all time travel information for the table