SnowPro Advanced: Security Engineer Question 166
Single answerDifferentiate between Time Travel and Fail-safe in context of security and complianceA financial services company stores regulated trading data in Snowflake. The security engineer is asked to meet two competing compliance requirements: (1) analysts must be able to quickly recover data if a table is accidentally dropped within a short retention window, and (2) auditors want assurance that Snowflake maintains a limited post-retention recovery mechanism for disaster recovery, but that mechanism must not be presented to internal users as a self-service restore feature. Which statement best explains how Time Travel and Fail-safe should be described in the company’s security and compliance documentation?
- A
Time Travel provides a user-accessible retention period for querying or restoring historical data within the configured window, while Fail-safe is a Snowflake-managed recovery period primarily for disaster recovery and is not intended for self-service access by users.
- B
Fail-safe should be used by analysts to restore dropped tables because it offers the same user-controlled recovery workflow as Time Travel, just with a longer retention period.
- C
Time Travel and Fail-safe both allow security administrators to directly query historical table versions, but Fail-safe requires the ACCOUNTADMIN role.
- D
Disabling Time Travel removes all retained copies immediately, so Fail-safe also becomes unavailable and Snowflake cannot recover the data afterward.
Show answer and explanation
Correct answer: A
Explanation
The key security and compliance distinction is that Time Travel is a configurable data retention feature that supports user-driven recovery and historical access within the allowed retention period, whereas Fail-safe is a separate 7-day, Snowflake-managed recovery mechanism intended for disaster recovery after Time Travel has expired. From a governance perspective, organizations should not describe Fail-safe as a normal restore feature available to analysts, developers, or even account administrators. Instead, it should be documented as a back-end safeguard with limited operational use and potential Snowflake intervention. This aligns with Snowflake documentation on data retention periods, object recovery, and the purpose of Fail-safe. For exam purposes, candidates should recognize that Time Travel supports operational recovery and auditing use cases, while Fail-safe supports platform resiliency and compliance discussions around recoverability but not self-service data access.
- A. Correct.
Correct. Time Travel is designed for user-accessible historical data recovery and querying within the defined retention period, such as restoring dropped objects or querying data at a previous point in time. Fail-safe begins after Time Travel ends and is maintained by Snowflake for a limited period to support disaster recovery. Customers cannot use Fail-safe as an on-demand, self-service recovery feature. This distinction is important in compliance documentation because Time Travel supports operational recovery, while Fail-safe is a platform-managed safeguard.
- B. Incorrect.
Incorrect. This reflects a common misconception that Fail-safe is simply an extended version of Time Travel for end users. In reality, Fail-safe is not intended for routine analyst-driven restoration and does not provide the same self-service functionality. Recovery from Fail-safe requires Snowflake involvement and is reserved for exceptional situations.
- C. Incorrect.
Incorrect. Time Travel supports querying historical data and restoring objects within retention limits, but Fail-safe does not provide direct query access to historical table versions by customers or administrators. There is no standard model where ACCOUNTADMIN can independently browse or query data in Fail-safe. The misconception here is confusing administrative privilege with platform-level recovery controls.
- D. Incorrect.
Incorrect. Reducing or minimizing Time Travel retention does not mean Fail-safe is eliminated for permanent table data that qualifies for Fail-safe protection. Fail-safe is a separate Snowflake-managed period that follows Time Travel for applicable permanent objects. The misconception is assuming Fail-safe depends on user access to Time Travel rather than understanding that they are sequential but distinct mechanisms.