Free Practice Questions for Snowflake COF-C02 Exam

An explain plan is beneficial because it allows for the evaluation of how a query will be processed without the need to actually execute the query. This can help in understanding the query’s performance implications and potential bottlenecks without consuming resources that would be used if the query were run

The ResultSet cache is leveraged to quickly return results for repeated queries. Actions that prevent leveraging this cache include stopping the virtual warehouse that the query is running against (B) and executing the RESULTS_SCAN() table function (D). Stopping the warehouse clears the local diskcache, including the ResultSet cache1. The RESULTS_SCAN() function is used to retrieve the result of a previously executed query, which bypasses the need for the ResultSet cache.

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

 When the retention period for an object ends in Snowflake, Time Travel on the historical data is dropped ©. This means that the ability to access historical data via Time Travel is no longer available once the retention period has expired2.

The SQL statement SHOW GRANTS TO ROLE MY_ROLE is used to determine which users and roles have access to a role called MY_ROLE. This statement lists all the privileges granted to the role, including which roles and users can assume MY_ROLE. References: [COF-C02] SnowPro Core Certification Exam Study Guide

 The billable compute time includes the time the warehouse is running queries plus the auto-suspend time after the last query if the warehouse is not manually suspended. In this scenario, the warehouse runs for 3 minutes, suspends after 10 minutes of inactivity, resumes for a 10-second query, and then is manually suspended. The total billable time is the sum of the initial 3 minutes, the 10 minutes of auto-suspend time, and the brief period for the 10-second query, which is rounded up to the next full minute due to Snowflake’s billing practices. References: [COF-C02] SnowPro Core Certification Exam Study Guide

The Snowflake Enterprise edition includes database replication and failoverfor business continuity and disaster recovery, as well as extended time travel capabilities for longer data retention periods1.

The features associated with Continuous Data Protection (CDP) that require additional Snowflake-provided data storage are Time Travel and Fail-safe. Time Travel allows users to access historical data within a defined period, while Fail-safe provides an additional layer of data protection beyond the Time Travel period. References: [COF-C02] SnowPro Core Certification Exam Study Guide

The correct answer is B. Add more clusters to the warehouse .

Queued queries on a multi-cluster warehouse usually indicate a concurrency problem. Multiple analysts are submitting queries at the same time, and the warehouse does not have enough active cluster capacity to process them concurrently.

Why B is correct:

Adding more clusters to a multi-cluster warehouse increases concurrency capacity. In Auto-scale mode, Snowflake can start additional clusters as needed, up to the configured maximum, to reduce queuing.

Why the other options are incorrect:

A. Scheduling or limiting reports may reduce concurrency, but it adds operational overhead and does not use Snowflake’s built-in multi-cluster scaling capability.

C. Increasing warehouse size can make individual queries faster, but it does not directly improve concurrency as effectively as adding clusters.

D. A Snowpark-optimized warehouse is intended for memory-intensive Snowpark workloads, not for reducing query queues from many concurrent BI/ad hoc users.

Official Snowflake documentation reference:

Snowflake documentation explains that multi-cluster warehouses are designed to handle concurrency by automatically scaling out with additional clusters.

The correct answer is D. Directory tables can be joined with other tables in Snowflake .

A directory table stores file-level metadata for files in a stage. This metadata can be queried using SQL, which means it can also be filtered, selected from, and joined with other Snowflake tables.

Why D is correct:

Because directory table metadata can be queried like table data, users can join that metadata with other Snowflake tables. This is useful for workflows where file metadata needs to be compared with control tables, audit tables, or processing logs.

Example concept:

SELECT d.relative_path, l.load_status

FROM DIRECTORY(@my_stage) d

LEFT JOIN load_log l

ON d.relative_path = l.file_name;

Why the other options are incorrect:

A. Directory tables store file-level metadata, but not in a temporary table. They are associated with stages.

B. Directory tables do not have their own independent privilege model. Access is controlled through privileges on the associated stage.

C. Any user cannot configure directory table privileges independently.

Official Snowflake documentation reference:

Snowflake documentation explains that directory tables store file-level metadata about staged files and that users can query this metadata with SQL, enabling joins with other tables.

In Snowflake, aShareis the object that contains all the information required to share a database with other Snowflake accounts. Shares are used to securely share data stored in Snowflake tables and views, enabling data providers to grant data consumers access to their datasets without duplicating data. When a database is shared, it can include one or more schemas, and each schema can contain tables, views, or both.

TheLOGIN_HISTORYview inSNOWFLAKE.ACCOUNT_USAGEshows from which IP address a user connected to Snowflake. This view is particularly useful for auditing and monitoring purposes, as it helps administrators track login attempts, successful logins, and the geographical location of users based on their IP addresses.

Reference to Snowflake documentation on LOGIN_HISTORY:

Monitoring Login Attempts

Reader accounts are created by data providers for consumers who do not have their own Snowflake accounts. This allows providers to share data without requiring the consumer to create or pay for their own Snowflake account.

While a consumer can access multiple shares via a single reader account , administrative functions (like resource monitors) are managed by the provider.

The correct answer is A. ALTER SHARE .

To provide a consumer account with access to an existing share, the provider adds the consumer account to the share. This is done using the ALTER SHARE command with the ADD ACCOUNTS clause.

Example:

ALTER SHARE my_share

ADD ACCOUNTS = consumer_org.consumer_account;

Why A is correct:

ALTER SHARE modifies an existing share. Adding consumer accounts to a share gives those accounts access to the share.

Why the other options are incorrect:

B. CREATE SHARE creates a new share object, but it does not by itself add a consumer account to an existing share.

C. DESCRIBE SHARE displays metadata about a share; it does not grant access.

D. GRANT < privilege > ... TO SHARE grants database object privileges to the share, such as usage on a database or select on a table. It does not add a consumer account to the share.

Official Snowflake documentation reference:

Snowflake documentation explains that ALTER SHARE ... ADD ACCOUNTS is used to add consumer accounts to a share. Object privileges are granted separately to the share using GRANT ... TO SHARE.