Free Snowflake SnowPro Associate: Platform Certification Exam SOL-C01 Exam Questions

Roles gain access to objects in Snowflake throughdirect privilege grantsor throughinheritancewithin a role hierarchy. A role may be explicitly granted privileges such as SELECT, OWNERSHIP, or USAGE. Alternatively, if a role is assigned to another role, it inherits all privileges of its parent role. Neither network settings nor data storage processes determine role access.

SnowflakeData Exchangeenables secure, governed sharing oflive databetween Snowflake accounts. It lets providers publish datasets to specific consumers---partners, vendors, departments, or customers---without copying or transferring data. Consumers query shared data instantly, leveraging Snowflake's secure data sharing architecture.

Key capabilities include:

Targeted sharing to selected accounts

Fine-grained access management and auditing

Live, real-time data sharing without data movement

Ability to customize listings and visibility

Data Exchange is different from theMarketplace, which supports public or broad distribution.

It does not store raw data---storage occurs in provider accounts.

It does not manage user permissions (that is the role of RBAC).

Time Travel enables Snowflake users to query, clone, or restore historical versions of data. This includes retrieving previous states of tables, schemas, or databases---even after updates, deletes, or drops. Time Travel operates within a retention period (default: 1 day, up to 90 days on higher editions).

Users can query historical data using the AS OF or BEFORE clause, restore dropped objects, and clone databases at specific points in time for backup or analysis.

Time Travel doesnotautomatically manage timestamp data types. It does not guarantee indefinite recovery---after the retention window expires, data moves into Fail-safe. It also is not primarily designed for loading historical datasets; its purpose is to access past states of Snowflake-managed data.

Thus, the correct purpose is to enable access to historical data inside Snowflake.

Snowsight is the default web-based interface for Snowflake. It provides a graphical, browser-based environment to write and run SQL and Python, manage and explore database objects, create visualizations and dashboards, monitor query and warehouse activity, and collaborate via worksheets. It has replaced the Classic Console as the default UI for new Snowflake accounts.

SnowSQL is a command-line client used to connect to Snowflake from a terminal and execute SQL statements. Snowpark is a developer framework that supports writing data applications in languages like Python, Java, and Scala, but it is not a UI. ''Snowflake CLI'' refers to command-line tooling and automation utilities, again not a graphical web interface.

Snowflake uses the SQL command CREATE WAREHOUSE warehouse_name to create a new virtual warehouse. Warehouses provide the compute resources for executing SQL queries, loading data, and performing transformations. When creating a warehouse, additional parameters may be specified, such as warehouse size, auto-suspend timeout, auto-resume, scaling policy, or multi-cluster mode. The options involving ''CREATE VIRTUALWAREHOUSE'' are invalid syntax in Snowflake. CREATE DATABASE and CREATE SCHEMA create storage containers, not compute resources. Therefore, CREATE WAREHOUSE is the only correct command for provisioning compute.

Amulti-cluster warehouseprovides Snowflake's highest level of concurrency support by allocating multiple compute clusters behind a single warehouse definition. It automatically adds clusters during peak workload to eliminate query queuing and maintain stable performance for dashboards, BI tools, and multi-user environments.

Improved concurrencyis the primary benefit---large numbers of simultaneous queries are distributed across clusters.

Automatic scaling(scaling out and in) ensures compute cost efficiency, as Snowflake adds clusters only when needed and removes them when load decreases.

Incorrect options:

Storage costs are unaffected because compute and storage are independent.

Faster data loading may occur if warehouse size increases, but multi-cluster design is driven by concurrency, not ingestion performance.

The design enables smooth operation in high-demand enterprise environments.

On the Snowflake Marketplace, users can apply a Price filter when searching for data products. This filter helps distinguish between free offerings and paid listings, making it easier to align data acquisition with budget and commercial terms. Marketplace metadata includes pricing information that this filter uses to refine search results.

Dataset ''Size'' is not exposed as a primary Marketplace search filter. ''Compatibility'' is implied, as all Marketplace products are consumable within Snowflake. ''Performance'' is not a filterable attribute, because performance is influenced mainly by the consumer's compute configuration and query design, rather than a fixed property of the Marketplace listing.

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.

SHOW FILE FORMATS listsfile format objectsthat exist in the currently selected schema (or optionally, a specific database or schema). These objects define how Snowflake interprets staged files during data loading.

It doesnotlist supported built-in formats (CSV, Parquet, etc.).

It doesnotshow example usage information and doesnotlist files---LIST @stage handles that.

Cortex LLM functions integrate large language model capabilities directly inside Snowflake. These functions enable:

* Sentiment analysis

* Summarization

* Document question answering

* Text classification

* Embedding generation for vector search

They operate directly on Snowflake data, require no external infrastructure, and support secure in-platform AI workloads.

When auto-resume is enabled, Snowflake automatically starts a suspended warehouse when a query or task is submitted. This ensures smooth operations without manual intervention.

It does not scale the warehouse, prevent suspension, or require manual restarting.

TheLIMITclause is used to restrict the number of rows returned by a query. The correct syntax in Snowflake is:

SELECT * FROM employees LIMIT 10;

This retrieves the first 10 rows of the result set. LIMIT appears at the end of the SELECT statement. Snowflake follows a SQL syntax similar to MySQL/PostgreSQL regarding LIMIT usage.

Incorrect forms include:

Using LIMIT before SELECT

Embedding LIMIT inside WHERE

Reversing the order of SELECT and LIMIT

LIMIT is frequently used for sampling, record previewing, debugging, and exploratory analysis.

Snowflake supports several numeric data types, includingINTEGER(and its aliases INT, BIGINT, SMALLINT, TINYINT) andFLOAT(a floating-point type). INTEGER represents exact whole numbers, and FLOAT supports approximate numerical values with fractional components. BOOLEAN is a logical data type used for TRUE/FALSE values, not numeric. VARCHAR is a string data type, also not numeric. Thus, INTEGER and FLOAT are the correct numeric data types supported by Snowflake.

Snowflake provides multipledate and time data typesto handle various temporal workloads. TheDATEtype stores only the calendar date (year, month, day), suitable for dimensional modeling, slowly changing dimensions, and calendar-related analytics.

TIMESTAMPrepresents a point in time and includes sub-second precision. Snowflake supports multiple variants:

TIMESTAMP_NTZ(no time zone)

TIMESTAMP_LTZ(local time zone)

TIMESTAMP_TZ(explicit time zone)

These options allow flexibility for global operations, event logs, and time-series analytics.

DATETIMEis an alias forTIMESTAMP_NTZ, meaning it stores both date and time but without time-zone awareness. It is commonly used in ETL, application logs, and system-generated events.

TIMEDATEis not a valid Snowflake data type and does not exist in Snowflake's type system.

These temporal types support extensive built-in datetime functions, automatic casting, and integration with semi-structured data through VARIANT.

Snowflake's architecture separates storage and compute, enabling:

* Compute scaling (up/down or multi-cluster) without changing storage

* Storage expansion without affecting compute

* Cost optimization by paying for compute only when needed

This separation does not impact governance, latency, or data loading requirements.