Fail-safe is a non-configurable feature in Snowflake that provides an additional layer of data protection beyond Time Travel. Time Travel allows users to access historical data within a configurable period (up to 90 days), while Fail-safe provides an additional 7-day period during which Snowflake retains historical data to recover from significant data loss or corruption incidents. This period is not accessible by users but can be used by Snowflake support to assist in data recovery efforts.References: Snowflake Documentation on Fail-safe and Time Travel

To use key pair authentication in Snowflake, you need to set the public key for the user. This allows the user to authenticate using their private key.
* Generate Key Pair:Generate a public and private key pair.
* Set Public Key:
ALTER USER jsmith SET RSA_PUBLIC_KEY='MIIBIjANBgkqh...';
* Authentication:The user can now authenticate by signing requests with the corresponding private key.
References:
* Snowflake Documentation: Key Pair Authentication & Key Rotation
* Snowflake Documentation: ALTER USER

When cloning a database in Snowflake, the clone includes all privileges on the database as well as existing child objects within the database, such as schemas, tables, views, etc. However, it does not include future child objects or privileges on schemas within the database2.
Reference = [COF-C02] SnowPro Core Certification Exam Study Guide, Snowflake Documentation

When cloning a database in Snowflake, the clone includes all privileges on the database as well as existing child objects within the database, such as schemas, tables, views, etc. However, it does not include future child objects or privileges on schemas within the database2.
References = [COF-C02] SnowPro Core Certification Exam Study Guide, Snowflake Documentation