- (Topic 6)
What do temporary and transient tables have m common in Snowflake? (Select TWO).

1. A. Both tables have no Fail-safe period.
2. B. Both tables have data retention period maximums of one day.
3. C. Both tables are visible only to a single user session.
4. D. For both tables the retention period ends when the tables are dropped.
5. E. For both tables, the retention period does not end when the session ends

Correct Answer: AD
Temporary and transient tables in Snowflake share several characteristics, notably, neither table type has a Fail-safe period. Fail-safe is a feature that provides additional data protection beyond the Time Travel period. However, this feature does not apply to temporary or transient tables. Additionally, for both types of tables, the data retention period effectively ends when the tables are dropped. This means that once these tables are deleted, their data is not recoverable, distinguishing them from permanent tables, which benefit from Snowflake's Time Travel and Fail-safe features.References:Snowflake Documentation on Table Types

- (Topic 3)
Which statement MOST accurately describes clustering in Snowflake?

1. A. The database ACCOUNTADMIN must define the clustering methodology for each Snowflake table.
2. B. Clustering is the way data is grouped together and stored within Snowflake micro- partitions.
3. C. The clustering key must be included in the COPY command when loading data into Snowflake.
4. D. Clustering can be disabled within a Snowflake account.

Correct Answer: B
Clustering in Snowflake refers to the organization of data within micro- partitions, which are contiguous units of storage within Snowflake tables. Clustering keys can be defined to co-locate similar rows in the same micro-partitions, improving scan efficiency and query performance12.
References: [COF-C02] SnowPro Core Certification Exam Study Guide

- (Topic 6)
A clustering key was defined on a table, but It is no longer needed. How can the key be removed?

1. A. ALTER TABLE <TABLE NAME> PURGE CLUSTERING KEY
2. B. ALTER TABLE <TABLE NAME> DELETE CLUSTERING KEY
3. C. ALTER TABLE <TABLE NAME> DROP CLUSTERING KEY
4. D. ALTER TABLE <TABLE NAME> REMOVE CLUSTERING KEY

Correct Answer: C
To remove a clustering key that was previously defined on a table in Snowflake, the correct SQL command isALTER TABLE <TABLE NAME> DROP CLUSTERING KEY. This command removes the existing clustering key from the table, after which Snowflake will no longer re-cluster data based on that key during maintenance operations or after data loading operations.
Reference: Snowflake Documentation on altering tables, specifically the section on
modifying clustering keys: https://docs.snowflake.com/en/sql-reference/sql/alter- table.html#modifying-clustering-keys

- (Topic 2)
What is the maximum Time Travel retention period for a temporary Snowflake table?

1. A. 90 days
2. B. 1 day
3. C. 7 days
4. D. 45 days

Correct Answer: B
The maximum Time Travel retention period for a temporary Snowflake table is 1 day. This is the standard retention period for temporary tables, which allows for accessing historical data within a 24-hour window

- (Topic 6)
Which function returns the URL of a stage using the stage name as the input?

1. A. BUILD_STAGE_FILE_URL
2. B. BUILD_SCOPED_FILE_URL
3. C. GET_PRESIGNED_URL
4. D. GET STAGE LOCATION

Correct Answer: C
The function in Snowflake that returns the URL of a stage using the stage name as the input isC. GET_PRESIGNED_URL. This function generates a pre-signed URL for a specific file in a stage, enabling secure, temporary access to that file without requiring Snowflake credentials. While the function is primarily used for accessing files in external stages, such as Amazon S3 buckets, it is instrumental in scenarios requiring direct, secure file access for a limited time.
It's important to note that as of my last update, Snowflake's documentation does not specifically list a function namedGET_PRESIGNED_URLfor directly obtaining a stage's URL by its name. The description aligns closely with functionality available in cloud storage services (e.g., AWS S3's presigned URLs) which can be used in conjunction with Snowflake stages for secure, temporary access to files. For direct interaction with stages and their files, Snowflake offers various functions and commands, but the exact match for generating a presigned URL through a simple function call may vary or require leveraging external cloud services APIs in addition to Snowflake's capabilities.
References:
✑ Snowflake Documentation and cloud services (AWS, Azure, GCP) documentation on presigned URLs and stage interactions.