Database DB1 has schema S1 which has one table, T1. DB1 --> S1 --> T1 The retention period of EG1 is set to 10 days. The retention period of s: is set to 20 days. The retention period of t: Is set to

The correct answer is C. 30 days. In Snowflake, Time Travel retention periods are set at three levels: database, schema, and table. When a database is dropped, Snowflake retains all of its objects in a dropped state, and each object keeps its own individually configured retention period - it does NOT inherit the

Snowflake Architecture

Question

Database DB1 has schema S1 which has one table, T1. DB1 --> S1 --> T1 The retention period of EG1 is set to 10 days. The retention period of s: is set to 20 days. The retention period of t: Is set to 30 days. The user runs the following command:

Drop Database DB1; What will the Time Travel retention period be for T1?

Options

A10 days
B20 days
C30 days
D37 days

How the community answered

(26 responses)

A
15% (4)
B
8% (2)
C
73% (19)
D
4% (1)

Explanation

In Snowflake, Time Travel retention periods are set at three levels: database, schema, and table. When a database is dropped, Snowflake retains all of its objects in a dropped state, and each object keeps its own individually configured retention period - it does NOT inherit the parent object's retention period at the time of the DROP. Since T1 has its own retention period explicitly set to 30 days, that is the period that governs how long T1 remains accessible via Time Travel after DB1 is dropped. The database-level 10 days and schema-level 20 days are irrelevant to T1's retention because T1 has an explicit override. This is an important Snowflake design principle: the most granular (lowest-level) setting takes precedence. Choice D (37 days) has no basis in Snowflake's retention logic.

Topics

#Snowflake Time Travel#Data Retention#Database Objects Hierarchy#DROP Command

Community Discussion

No community discussion yet for this question.

Full ARA-C01 Practice