The data retention period for tables in a secondary database begins when the secondary database is refreshed with the DML operations written to tables in the primary database.

Master the SnowPro Advanced Architect Test with flashcards, multiple-choice questions, and detailed explanations. Prepare thoroughly for your certification!

Multiple Choice

The data retention period for tables in a secondary database begins when the secondary database is refreshed with the DML operations written to tables in the primary database.

Explanation:
In Snowflake replication, the second copy becomes a usable mirror only after the refresh brings in the primary’s DML changes. The retention window for Time Travel and related recovery features on those replicated tables starts from that refresh moment. Until the refresh occurs, there isn’t a current, consistent state in the secondary to apply a retention period to. Once refreshed, the data on the secondary is the point from which you can travel back in time within the configured retention. So the statement is true.

In Snowflake replication, the second copy becomes a usable mirror only after the refresh brings in the primary’s DML changes. The retention window for Time Travel and related recovery features on those replicated tables starts from that refresh moment. Until the refresh occurs, there isn’t a current, consistent state in the secondary to apply a retention period to. Once refreshed, the data on the secondary is the point from which you can travel back in time within the configured retention. So the statement is true.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy