Snowflake COF-C03 Practice Exam Questions & Answers

For minimizing the cost of large tables that are used to store transitory data, which does not need to be protected against failures because it can be reconstructed outside of Snowflake, the best table type to use isTransient. Transient tables in Snowflake are designed for temporary or transitory data storage and offer reduced storage costs compared to permanent tables. However, unlike temporary tables, they persist across sessions until explicitly dropped.

Why Transient Tables:Transient tables provide a cost-effective solution for storing data that is temporary but needs to be available longer than a single session. They have lower data storage costs because Snowflake does not maintain historical data (Time Travel) for as long as it does for permanent tables.

Creating a Transient Table:

To create a transient table, use theTRANSIENTkeyword in the CREATE TABLE statement:

CREATETRANSIENTTABLEmy_transient_table (...);

Use Case Considerations:Transient tables are ideal for scenarios where the data is not critical, can be easily recreated, and where cost optimization is a priority. They are suitable for development, testing, or staging environments where data longevity is not a concern.

The correct answer is A. Snowflake will start all available clusters.

A multi-cluster warehouse can run in Auto-scale mode or Maximized mode. When MIN_CLUSTER_COUNT and MAX_CLUSTER_COUNT are set to the same value greater than 1, the warehouse runs in Maximized mode.

Why A is correct:

In Maximized mode, Snowflake starts all configured clusters when the warehouse starts. For example, if both MIN_CLUSTER_COUNT and MAX_CLUSTER_COUNT are set to 3, Snowflake starts 3 clusters when the warehouse starts.

Clarification:

''Available clusters'' here means all clusters configured for that warehouse, not every cluster in the Snowflake account.

Why the other options are incorrect:

B . Starting enough clusters based on workload describes Auto-scale behavior, not Maximized mode.

C . This describes a queued-query scaling behavior but does not apply when minimum and maximum cluster counts are equal.

D . This describes the Economy scaling policy behavior in Auto-scale mode, not Maximized mode.

Official Snowflake documentation reference:

Snowflake documentation explains that when the minimum and maximum number of clusters are the same, a multi-cluster warehouse runs in Maximized mode and starts all clusters when the warehouse starts.

==

The pre-signed URL type allows users or applications to download or access files directly from a Snowflake stage without authentication. This URL type is open and can be used without needing to authenticate into Snowflake or pass an authorization token.

Stored procedures in Snowflake can be created with either 'owner's rights' or 'caller's rights'. A stored procedure created with caller's rights executes with the privileges of the role that calls the procedure, not the privileges of the role that owns the procedure. This is particularly useful in scenarios where the procedure needs to perform operations that depend on the caller's access permissions, ensuring that the procedure can only access objects that the caller is authorized to access.

In owner's rights stored procedures, certain commands are restricted to maintain security and integrity. The SHOW and DESCRIBE commands are limited because they can reveal metadata and structure information that may not be intended for all roles.

In Snowflake, reader accounts are special types of accounts that allow data sharing with external consumers without them having their own Snowflake account. The creation and management of reader accounts can be performed by users with the ACCOUNTADMIN role or the ORGADMIN role. The ACCOUNTADMIN role has comprehensive administrative privileges within a Snowflake account, including managing other accounts and roles. The ORGADMIN role, which is higher in hierarchy, oversees multiple accounts within an organization and can manage reader accounts across those accounts.

:

Snowflake Documentation: Creating and Managing Reader Accounts

The correct answer is D. Create a secure view.

A secure view is the recommended and efficient way to share a filtered subset of data with a consumer account using Snowflake Secure Data Sharing. The provider can define the rows and columns that should be visible, then share the secure view instead of sharing the full base table.

Why D is correct:

A secure view protects the view definition from unauthorized users and can be used to expose only selected rows or columns from an underlying table.

Example concept:

CREATE SECURE VIEW shared_sales_west AS

SELECT order_id, customer_id, amount, region

FROM sales

WHERE region = 'WEST';

The provider can then include this secure view in a share, allowing the consumer to query only the approved subset of data.

Why the other options are incorrect:

A . A secure UDF can protect function logic, but it is not the most efficient method for sharing a subset of table data.

B . A dynamic table materializes transformation results, but it is not the standard method for secure data sharing with filtered access.

C . An external table allows querying data in external cloud storage. It is not the best method for sharing a subset of Snowflake table data.

Official Snowflake documentation reference:

Snowflake documentation explains that secure views are used with Secure Data Sharing when a provider wants to share filtered or restricted data while protecting the underlying query definition.

==