A financial institution needs to maintain a record of all changes made to its customer data for regulatory compliance. They are using Snowflake and want to leverage Time Travel and Fail-safe for data

Question

Options

• ARely solely on Fail-safe for long-term data retention and recovery.
• BSet to the maximum allowed value (90 days for Business Critical or as configured) and regularly
• CSet to the maximum value for the account. Do nothing else as this will satisfy the audit
• DSet appropriately (e.g. 90 days) and regularly back up data to external storage and create granular
• ELeverage Time Travel within its configured retention period for recovering from user errors or data

• A
  6% (2)
• B
  64% (21)
• C
  18% (6)
• D
  12% (4)

Explanation

Option B provides a comprehensive solution by using Time Travel for the short term within a retention period. After the retention period expires, Fail-safe kicks in (handled by Snowflake). Fail- safe is not directly accessible to the user. A clone is created regularly for archival, providing a long-term record for compliance. Option E accurately describes Fail-safe as a disaster recovery measure rather than a tool for direct data recovery by the customer.

No community discussion yet for this question.