Pass the Snowflake SnowPro Core Certification COF-C03 Questions and answers with Dumpstech

The most effective way for a data provider to validate secure view configurations is to create a data share for a test data consumer account. This method allows the provider to review and confirm that only the intended data is accessible in the secure view. Secure views are designed to mask or restrict data visibility, so creating a test share replicates the consumer ' s experience and ensures data security before sharing with actual consumers.

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 answer is B. A string value should be specified to represent NULL values using the NULL_IF option .

When unloading data from Snowflake into files using the COPY INTO < location > command, Snowflake needs a textual representation for SQL NULL values in the unloaded files. This can be controlled by the NULL_IF file format option.

Why B is correct:

The NULL_IF option specifies one or more string values that represent SQL NULL values. During unloading, Snowflake uses this option to determine how NULL values should appear in the output files.

For example, a file format could specify:

NULL_IF = ( ' NULL ' )

This means SQL NULL values can be written using the string NULL in the unloaded file.

Why the other options are incorrect:

A. Snowflake does not always automatically convert NULL values to empty strings in all unload scenarios. The representation depends on file format settings.

C. NULL values do not cause the unload process to stop with an error by default.

D. NULL values are not automatically skipped during unloading. They are included in the output using the configured representation.

Official Snowflake documentation reference:

Snowflake documentation for file format options explains that NULL_IF specifies the string used to represent SQL NULL values when loading or unloading data.

The correct function to find the query ID of the second query executed in the current session isSELECT LAST_QUERY_ID(-2). TheLAST_QUERY_IDfunction returns the query ID for the most recent query executed in the session when called with no arguments. When used with an argument, it can retrieve the ID of previous queries within the same session, where-2would reference the second most recent query executed.

In Snowflake, Secure User-Defined Functions (UDFs) can be shared with other accounts using Snowflake ' s data sharing feature. This allows different Snowflake accounts to securely execute the UDFs without having direct access to the underlying data the functions operate on, ensuring privacy and security. The sharing is facilitated through shares created in Snowflake, which can contain Secure UDFs along with other database objects like tables and views.

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.

The correct answer is C. To track how data has been transformed among columns .

Snowflake’s data lineage capability is used to understand how data flows and changes across objects. It helps users see relationships between source and target objects and understand how data is transformed, especially at the column level.

Corrected wording:

The original option said “records,” but Snowflake data lineage is more accurately described as tracking how data is transformed among columns, not individual row-level record transformations.

Why C is correct:

Data lineage helps track how data moves from source columns to target columns through operations such as views, CTAS statements, INSERT statements, and other transformations. This is useful for governance, impact analysis, auditing, and understanding downstream dependencies.

Why the other options are incorrect:

A. Tracking how records are read by a user is more closely related to access history or query history, not data lineage.

B. Tracking dependencies at the object level is related to object dependencies. Data lineage is more specific because it can show how data flows between columns and objects.

D. Snowflake data lineage is not primarily a row-level feature for tracking the impact of transformations on individual records.

Official Snowflake documentation reference:

Snowflake documentation describes data lineage as a governance capability that helps track how data moves and transforms across Snowflake objects, including column-level relationships.

Session policies allow account administrators to define rules such as session timeout , requiring users to re-authenticate after inactivity . This is different from password or network policies, which manage login credentials and IP filtering.

The primary factor that determines the cost of using a virtual warehouse in Snowflake isD. The length of time the compute resources in each cluster run. Snowflake ' s pricing model for compute usage is based on the concept of Snowflake credits, which are consumed based on the time virtual warehouses are running and the size of the warehouses. The more compute resources are utilized and the longer they run, the more credits are consumed, which directly impacts the cost.

The correct answer is C. Row access policy .

A row access policy is used to implement row-level security in Snowflake. It controls whether a row is visible in query results based on conditions such as the current role, current user, or values in a mapping table.

Why C is correct:

The question asks which feature controls visibility of particular records, meaning rows. Row access policies are designed exactly for that purpose.

Example concept:

CREATE ROW ACCESS POLICY region_policy

AS (region STRING) RETURNS BOOLEAN - >

region IN (

SELECT allowed_region

FROM role_region_mapping

WHERE role_name = CURRENT_ROLE()

);

This policy can allow users with different roles to see only the rows assigned to their region.

Why the other options are incorrect:

A. Dynamic Data Masking controls how column values are displayed. It masks data in columns but does not filter entire rows.

B. Secure Data Sharing allows data to be shared between accounts, but it is not the row-level filtering feature itself.

D. Object tagging classifies or labels objects for governance, but it does not directly control row visibility.

Official Snowflake documentation reference:

Snowflake documentation describes row access policies as schema-level objects that determine whether a row is visible in query results.

A join operator producing dramatically more rows than its input tables usually indicates a join explosion, commonly caused by a missing, incomplete, or incorrect join condition. This can result in a Cartesian product where rows from one table are matched with many unrelated rows from another table.

In Snowflake,SAMPLE (5 ROWS)ensures an exact count of 5 rows is returned from MY_TABLE, regardless of table size. This is different from SAMPLE SYSTEM or SAMPLE BERNOULLI, which use percentage-based sampling, potentially returning varying row counts based on probabilistic methods.

The ROWS option is deterministic and does not depend on percentage, making it ideal when an exact row count is required.