QuestionQ48

Implement disaster recovery, perform backups, and replicate data

A Snowflake Administrator must configure Time Travel for a presentation area containing fact and dimension tables that receives substantial meaningless and erroneous IoT data. Time Travel is part of the company’s data-quality process, where the ingestion pipeline must revert to a known, high-quality data state if anomalies are found in the most recent load. Because of latencies in the data-acquisition process, data from the prior 30 days might need to be retrieved.

According to best practices, how should these requirements be satisfied?

Choose two
Explanation

Related fact and dimension tables need compatible Time Travel retention so that a common historical recovery point remains available for all of them, including the required 30-day period. Cloning the tables together at the same Time Travel point keeps the restored fact and dimension data temporally consistent and reduces referential-integrity problems. Snowflake permits DATA_RETENTION_TIME_IN_DAYS at account, database, schema, and table scopes; transient objects are limited to one day of retention.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!