Snowflake COF-C03 - SnowPro Core Certification 2026 Exam

In a scenario where a Snowflake user queries only a small number of rows that require significant processing and the data in the table does not change frequently, the most effective way to optimize performance is by creating a materialized view based on the query. Materialized views store the result of the query and can significantly reduce the computation time for queries that are executed frequently over unchanged data.

Why Materialized Views:Materialized views precompute and store the result of the query. This is especially beneficial for queries that require heavy processing. Since the data does not change frequently, the materialized view will not need to be refreshed often, making it an ideal solution for this use case.

Implementation Steps:

To create a materialized view, use the following SQL command:

CREATEMATERIALIZEDVIEWmy_materialized_viewASSELECT...FROMmy_tableWHERE...;

When the query is run, Snowflake uses the precomputed results from the materialized view, thus skipping the need for recalculating the data and improving query performance.

The correct answer is C. GLOBALORGADMIN .

Corrected typos:

The original options contain typing errors:

A. ACCOUNT AUXIN should be ACCOUNTADMIN

B. SYSAEMIN should be SYSADMIN

C. CLOBALORGADMIN should be GLOBALORGADMIN

D. HECURITYADMIH should be SECURITYADMIN

Auto-fulfillment is an organization-level capability related to Snowflake Native Apps and listings across regions or accounts. Because refresh frequency for auto-fulfilled application packages is managed at the organization/global level, the required role is GLOBALORGADMIN.

Why C is correct:

GLOBALORGADMIN is the organization-level administrative role used for managing organization-wide features. Changing the refresh frequency for an auto-fulfilled application package requires this higher-level administrative authority.

Why the other options are incorrect:

A. ACCOUNTADMIN is the highest administrative role within a Snowflake account, but auto-fulfillment refresh frequency is an organization-level setting.

B. SYSADMIN manages account objects such as warehouses, databases, schemas, and tables, but it does not manage organization-level auto-fulfillment settings by default.

D. SECURITYADMIN manages users, roles, and grants, but it is not the default role for managing auto-fulfillment refresh frequency.

Official Snowflake documentation reference:

Snowflake documentation for auto-fulfillment and organization-level administration identifies GLOBALORGADMIN as the role used for managing organization-level Snowflake features.

The correct SQL statement to list the version of the JDBC (Java Database Connectivity) drivers currently being used is to executeSELECT CURRENT_JDBC_VERSION();from within SnowSQL or any client application that utilizes JDBC for connecting to Snowflake. Snowflake provides specific functions to query the version of the client drivers or connectors being used, such as JDBC, ODBC, and others. TheCURRENT_JDBC_VERSION()function is designed specifically to return the version of the JDBC driver in use.

It ' s important to note that Snowflake supports various types of drivers and connectors for connecting to different client applications, including ODBC, JDBC, Python, and others. Each of these connectors has its own method or function for querying the current version in use. For JDBC, the appropriate function isCURRENT_JDBC_VERSION(), reflecting the specificity required to obtain version information relevant to the JDBC driver specifically.

In Snowflake, tag inheritance is a feature that allows tags, which are key-value pairs assigned to objects for the purpose of data governance and metadata management, to be inherited within a hierarchy. The hierarchy in which tag inheritance is possible is from Schema to Table to Column. This means that a tag applied to a schema can be inherited by the tables within that schema, and a tag applied to a table can be inherited by the columns within that table.

Resource monitors in Snowflake can perform actions such as suspending a virtual warehouse when its credit usage reaches a defined limit and triggering a notification to account administrators when credit usage reaches a specified threshold. These actions help manage and control resource usage and costs within Snowflake.

Snowflake Documentation: Resource Monitors

The correct answer is D. The volume of the data .

The NULL_COUNT Data Metric Function returns the number of NULL values in a column. This type of metric is used to verify data quality by measuring the amount, or volume, of missing values.

Why D is correct:

NULL_COUNT counts how many rows contain NULL in a specified column. Since it produces a count, it is used to evaluate the volume of missing data.

Example concept:

SELECT SNOWFLAKE.CORE.NULL_COUNT(

SELECT column_name FROM my_table

);

This returns the number of NULL values found in the selected column.

Why the other options are incorrect:

A. Accuracy verifies whether data values are correct, but NULL_COUNT only counts missing values.

B. Uniqueness is verified with metrics that check duplicate or distinct values, not NULL_COUNT.

C. Freshness measures how current or recent the data is, not how many nulls exist.

Official Snowflake documentation reference:

Snowflake documentation describes NULL_COUNT as a system Data Metric Function that returns the number of NULL values in a column.

Snowflake allows users to write custom application logic in JavaScript for two types of objects: Stored Procedures and User-Defined Functions (UDFs).

Stored Procedures:Snowflake stored procedures can be written in JavaScript to encapsulate complex business logic and procedural operations.

CREATE OR REPLACE PROCEDURE my_procedure()

RETURNS STRING

LANGUAGE JAVASCRIPT

EXECUTE AS CALLER

AS

$$

// JavaScript logic here

$$;

User-Defined Functions (UDFs):Snowflake UDFs can be written in JavaScript to perform custom calculations or operations on data.

CREATE OR REPLACE FUNCTION my_function(x FLOAT)

RETURNS FLOAT

LANGUAGE JAVASCRIPT

AS

$$

return x * 2;

$$;

TheGET_PRESIGNED_URLfunction in Snowflake generates a pre-signed URL for a file in an internal stage. This URL can be shared with external tools or users who do not have direct access to Snowflake, allowing them to download the file.

Generate Pre-Signed URL:

SELECT GET_PRESIGNED_URL(@my_stage/file.txt);

Share the URL:The generated URL can be shared with external users or applications, enabling them to access the file directly.

The default authentication mechanism for Snowflake clients (including JDBC) is the snowflake method, which uses username and password authentication.

The fastest way to load a specific, discrete set of staged files is to explicitly list the file names using the FILES parameter in the COPY INTO < table > command.

Snowflake recommends using the FILES parameter when you already know the exact files that need to be loaded. This avoids the overhead of scanning and matching files using a regular expression pattern.

Why D is correct:

The FILES parameter lets you specify an exact list of staged files to load. Since Snowflake does not need to evaluate a pattern against all available staged files, this is the fastest method for loading a known, specific set of files.

Why the other options are incorrect:

A. PATTERN uses regular expression matching, which can be useful, but it is generally slower than listing specific files with FILES.

B. A path prefix can narrow the file location, but it does not explicitly identify a discrete set of files.

C. Wildcard characters are not the recommended fastest method for loading a known set of staged files in Snowflake.

Official Snowflake documentation reference:

Snowflake COPY INTO < table > documentation states that the FILES parameter is used to specify a list of one or more files to load, and Snowflake recommends using FILES instead of PATTERN for better performance when loading a specific list of files.

The STRIP_OUTER_ARRAY parameter in the COPY INTO < table > command is used when loading data from a JSON file into a table. This parameter removes the outer array structure from the JSON data and loads separate rows of data into the table.

Understanding the STRIP_OUTER_ARRAY Parameter:

JSON files often contain data in an array format where multiple records are nested within a single outer array.

The STRIP_OUTER_ARRAY parameter helps in simplifying the loading process by removing this outer array, allowing each element within the array to be loaded as a separate row in the target table.

How It Works:

When the STRIP_OUTER_ARRAY parameter is set to TRUE, Snowflake treats each item within the outer array as an individual record.

This eliminates the need for additional parsing or transformation steps that would otherwise be required to handle nested arrays.

Example Usage:

FROM @my_stage/file.json

FILE_FORMAT = (TYPE = ' JSON ' STRIP_OUTER_ARRAY = TRUE);

In this example, the JSON file containing an array of objects is loaded into the tablemy_table.

Each object within the array is loaded as a separate row, without the outer array structure.

Benefits:

Simplifies data loading: By removing the outer array, the data is directly loaded into the table without additional manipulation.

Enhances performance: Streamlines the loading process, reducing the complexity and potential errors in handling nested JSON structures.

Snowflake Documentation: COPY INTO < table >

Snowflake Documentation: JSON File Format Options

The correct answer is A. It controls how a client or user can access Snowflake .

An authentication policy controls authentication behavior for users or accounts. It determines which authentication methods are allowed and can be used to enforce security requirements for access to Snowflake.

Why A is correct:

Authentication policies control how users or clients authenticate to Snowflake. They can be used to allow or restrict authentication methods, helping organizations enforce secure access standards.

Why the other options are incorrect:

B. Restricting inbound access to Snowflake is handled by network policies, not authentication policies.

C. Restricting outbound traffic from Snowflake to external network destinations is handled by external access integrations and network rules, not authentication policies.

D. SSO can be part of an authentication strategy, but an authentication policy is broader than only enabling SSO.

Official Snowflake documentation reference:

Snowflake documentation describes authentication policies as security objects that control authentication methods for users in a Snowflake account.

The correct answer is D. The existing micro-partitions will not be changed or impacted .

Important correction:

The provided answer B is not correct.

Snowflake stores table data in immutable micro-partitions. Because micro-partitions are immutable, Snowflake does not physically rewrite all existing micro-partitions immediately when a column is dropped. Instead, metadata is updated so that the dropped column is no longer visible or accessible in the table definition.

Why D is correct:

Dropping a column is a metadata operation. The underlying existing micro-partitions are not immediately rewritten to remove the column data. Snowflake’s immutable micro-partition design avoids expensive full-table rewrites for this type of operation.

Why the other options are incorrect:

A. Snowflake does not immediately create new micro-partitions containing only the remaining columns.

B. Existing micro-partitions are immutable and are not updated in place.

C. Snowflake does not automatically create a new table and rewrite all remaining data when a column is dropped.

Official Snowflake documentation reference:

Snowflake documentation describes micro-partitions as immutable storage units. Table metadata operations, such as dropping columns, do not immediately rewrite existing micro-partitions.

In Snowflake, the default access level for any securable object (such as a table, view, or schema) is " No access " until explicit access is granted. This means that when an object is created, only the owner of the object and roles with the necessary privileges can access it. Other users or roles will not have any form of access to the object until it is explicitly granted.

This design adheres to the principle of least privilege, ensuring that access to data is tightly controlled and that users and roles only have the access necessary for their functions. To grant access, the owner of the object or a role with the GRANT option can use the GRANT statement to provide specific privileges to other users or roles.

For example, to grant SELECT access on a table to a specific role, you would use a command similar to:

GRANTSELECTONTABLEmy_tableTOROLE my_role;