SnowPro Advanced: Security Engineer Question 164
Single answerUnderstand the differences and use cases for Time Travel and Fail-safeA security engineer is investigating a data exposure incident in Snowflake. During remediation, an analyst accidentally runs a DELETE statement against a critical permanent table containing audit records. The team needs the fastest way to restore the deleted data themselves if it is still within the retention window. They also want to understand what recovery path remains if that window has already passed. Which statement best describes the correct use of Time Travel and Fail-safe in this situation?
- A
If the table is still within its Time Travel retention period, the team can restore it directly using Snowflake SQL features such as UNDROP or cloning/queries at a previous point in time; after Time Travel expires, Fail-safe is a Snowflake-managed recovery mechanism and is not intended for customer self-service queries or restores.
- B
Fail-safe should be used first because it provides the fastest self-service recovery for recently deleted rows, while Time Travel is primarily for Snowflake internal disaster recovery.
- C
Time Travel and Fail-safe both allow the security team to run SELECT statements against historical table versions, but Fail-safe keeps the data immutable for seven days after that.
- D
Once rows are deleted from a permanent table, they cannot be recovered unless database replication was configured before the incident.
Show answer and explanation
Correct answer: A
Explanation
The key distinction is that Time Travel is a customer-facing data protection feature for recovering or accessing previous versions of data within the configured retention period, while Fail-safe is a separate 7-day, Snowflake-managed recovery period for permanent objects after Time Travel has ended. In a real incident, such as accidental DELETEs on a permanent audit table, the security engineer should first determine whether the object is still within Time Travel retention because that enables the fastest self-service recovery using SQL features like AT | BEFORE, CLONE, or UNDROP where applicable. If the Time Travel window has expired, the remaining path is Fail-safe, but customers cannot directly query or restore from Fail-safe themselves. This distinction is important for security operations, incident response planning, and setting realistic recovery expectations. Snowflake documentation on Time Travel and Fail-safe emphasizes that Fail-safe is intended only as a last-resort recovery mechanism managed by Snowflake and should not be treated as an operational backup strategy.
- A. Correct.
Correct. Time Travel is designed for customer-accessible recovery of historical data for supported objects within the configured retention period, including querying, cloning, and UNDROP for dropped objects. For a permanent table, if the data loss is still within Time Travel retention, the team can use those self-service capabilities. After Time Travel ends, Fail-safe provides an additional 7-day period for permanent objects, but it is a Snowflake-managed recovery option intended for exceptional recovery scenarios and not for direct customer querying or routine self-service restoration.
- B. Incorrect.
Incorrect. This reverses the roles of the two features. Time Travel is the primary and fastest self-service mechanism for recovering recent changes or accidental deletes within retention. Fail-safe is not a first-line, customer-operated recovery tool and is not used through normal SQL time-based access patterns.
- C. Incorrect.
Incorrect. Only Time Travel supports customer-accessible historical queries and other self-service recovery operations. Fail-safe does not let customers issue SELECT statements against historical data or directly restore objects on demand. A common misconception is to treat Fail-safe as an extended Time Travel window, but it is operationally different and more limited.
- D. Incorrect.
Incorrect. Permanent tables can often be recovered after accidental deletion or modification without replication, provided the recovery request falls within Time Travel retention. Even after Time Travel expires, Fail-safe may still provide a Snowflake-assisted recovery path for permanent objects. Replication can improve resilience, but it is not the only recovery method in this scenario.