Free SnowPro Core Certification Exam Practice Questions

In the execution time summary of a Query Profile in Snowflake, the categories included provide insights into various aspects of query execution. " Pruning " refers to the process by which Snowflake reduces the amount of data scanned by eliminating partitions of data that are not relevant to the query, thus improving performance. " Initialization " represents the time taken for query planning and setup before actual execution begins. These metrics are crucial for understanding and optimizing query performance.

The correct answers are

A.  

Memory spilling occurs when a query requires more memory than is available in the virtual warehouse. Snowflake may spill intermediate data to local or remote storage, which can slow query performance.

Why A is correct:

Increasing the warehouse size provides more compute and memory resources. This can reduce or eliminate spilling for memory-intensive queries.

Why B is correct:

Rewriting queries to process data in smaller batches reduces the amount of intermediate data held in memory at one time. This can reduce spilling and improve performance.

Important note about option C:

Option C is misleading because a virtual warehouse cluster’s size is changed by increasing the warehouse size . Since option A already says this correctly, option C is not the best answer.

Why the other options are incorrect:

C.  

A.  

D.  

E.  

Official Snowflake documentation reference:

Snowflake Query Profile documentation explains that spilling to local or remote storage can occur when operations do not fit in memory. Snowflake performance guidance recommends scaling up the warehouse or rewriting queries to reduce the amount of data processed.

The correct answers are A, B, and D , assuming SNOWFLAKE is a table or queryable object.

Important exam-note correction:

This question is written as a single-answer question, but more than one listed command can consume virtual warehouse credits. Any SELECT query that scans or processes table data generally requires a running virtual warehouse and can consume warehouse credits.

Why A, B, and D are correct:

These are SELECT statements against a table-like object. Query execution that scans or aggregates data uses compute resources from a virtual warehouse.

Examples:

SELECT MAX(UUID) FROM SNOWFLAKE;

SELECT COUNT(FLAKE_ID) FROM SNOWFLAKE GROUP BY UUID;

SELECT COUNT(*) FROM SNOWFLAKE;

These involve SQL query processing and therefore require warehouse compute unless the result is fully served from cache.

Why C is incorrect:

SHOW commands are metadata commands handled by Snowflake’s cloud services layer. They do not require an active virtual warehouse in the same way table-scanning SELECT queries do.

Official Snowflake documentation reference:

Snowflake documentation explains that virtual warehouses provide the compute resources required to execute SQL queries and DML operations. Metadata commands such as SHOW are handled by the cloud services layer.

Snowsight, Snowflake’s user interface for executing and analyzing queries, supports various types of visualizations to help users understand their data better. Among the supported types, area charts and bar charts are two common options. Area charts are useful for representing quantities through the use of filled areas on the graph, often useful for showing volume changes over time. Bar charts, on the other hand, are versatile for comparing different groups or categories of data. Both chart types are integral to data analysis, enabling users to visualize trends, patterns, and differences in their data effectively.

TheACCESS_HISTORYview in Snowflake is a powerful tool for enhancing data governance, especially concerning monitoring and auditing data access patterns for both read and write operations. The key ways in whichACCESS_HISTORYenhances overall data governance are:

B.  

E.  

ACCESS_HISTORYdoes not automatically apply data masking or tag columns with personal information. However, the insights derived from analyzingACCESS_HISTORYcan be used to identify sensitive data and inform the application of masking policies or other security measures.

When unloading data in Snowflake, it is essential to differentiate between empty strings and NULL values to preserve data integrity. The parameters FIELD_OPTIONALLY_ENCLOSED_BY and EMPTY_FIELD_AS_NULL are used together to address this:

FIELD_OPTIONALLY_ENCLOSED_BY: This parameter specifies the character used to enclose fields, which can differentiate between empty strings (as enclosed fields) and NULLs.

EMPTY_FIELD_AS_NULL: By setting this parameter, Snowflake interprets empty fields as NULL values when unloading data, ensuring accurate representation of NULLs versus empty strings.

These parameters are crucial when exporting data for systems that need explicit differentiation between NULL and empty string values.

 Snowflake supports semi-structured data types, which include OBJECT and VARIANT. These data types are capable of storing JSON-like data structures, allowing for flexibility in datarepresentation. OBJECT can directly contain VARIANT, and thus indirectly contain any other data type, including itself1.