Download Full Version SOL-C01 Snowflake Exam

LIST @stage_name displays all files present in a stage (internal or external).

PUT uploads local files to an internal stage.

GET downloads files from an internal stage.

COPY INTO loads or unloads data but does not list files.

==================

Executing anINSERTcommand in a Snowflake worksheet requires three components to be explicitly selected:

Active Warehouse– Provides compute resources to process the query. Without an active warehouse, DML operations cannot execute.

Database– The table receiving the INSERT must reside in the active database context.

Schema– The targeted table must be within a selected schema.

All three define the fully qualified context for locating and writing to the correct object. Snowflake’s compute/storage separation ensures compute is only used when warehouses are active. Schema and database selection ensure correct namespace resolution.

====================================================

TheCOMPLETEfunction is the only Cortex LLM function where the user can explicitly specify the model name (e.g., Mistral, Snowflake Arctic, Meta Llama models).

SUMMARIZE, SENTIMENT, and TRANSLATE are task-specific functions that use built-in, preselected models anddo not allowmodel selection.

The Snowsight Query Profile is a powerful diagnostic tool that provides a visual breakdown of how Snowflake executed a query. Its primary purpose is to help users visualize and analyze query performance. It displays execution steps, including scan operations, join strategies, pruning results, aggregation methods, and data movement between processing nodes.

The profile shows metrics such as execution time per step, partition pruning effectiveness, bytes scanned, and operator relationships. This allows developers, analysts, and DBAs to identify bottlenecks—such as unnecessary full-table scans, non-selective filters, or inefficient joins—and tune SQL accordingly.

Query Profile does not execute queries; execution happens in worksheets or programmatic interfaces. It does not create objects or manage data loading; those tasks involve separate SQL commands and UI interfaces.

Overall, Query Profile is essential for performance tuning, helping teams reduce compute costs, optimize warehouse sizing, and improve query efficiency.

==================