Free Practice Questions for Snowflake SOL-C01 Exam

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).

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

Role hierarchy in Snowflake allows one role to inherit the privileges of another. By granting roles to other roles, Snowflake enables scalable, maintainable access control. Higher-level roles grant privileges downward, allowing administrators to create layered access structures. This hierarchy simplifies permission management across teams and environments. It has no relation to SQL sequencing, network settings, or data storage.

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

Snowflake uses the COPY INTO

Query History in Snowsight includes:

• Query ID – A unique identifier for each executed query.

• Execution Status – Indicates whether the query succeeded, failed, or was canceled.

• Duration – Total time taken for the query to run.

While warehouse name is shown,warehouse sizeis not explicitly displayed. Credit consumption appears in Account Usage views, not directly in Query History.

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

The Snowsight object browser is Snowflake’s built-in visual interface for exploring and navigating all database objects within an account. It provides a hierarchical view across databases, schemas, and contained objects such as tables, views, stages, pipes, file formats, procedures, and functions. The key purpose of the object browser is to make it easy for users to view and filter database objects without needing SQL commands. Users can search objects by name, apply filters, preview table metadata, and inspect properties such as storage usage or row counts.

The object browser does not manage warehouses; warehouse management is done under the “Warehouses” section. It also does not create worksheets; worksheets are created in the “Worksheets” section. Additionally, the object browser does not modify security settings—permissions and grants are controlled through SQL (GRANT, REVOKE, SHOW GRANTS) or through the Access Control interfaces.

In summary, the object browser is a discovery and navigation layer, allowing users to efficiently find, inspect, and explore Snowflake objects.

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

Zero-Copy Cloning allows Snowflake users to create instant, writable clones of databases, schemas, or tableswithout physically copying data. Instead, Snowflake references the same underlying micro-partitions, making the clone creation nearly instantaneous and storage-efficient. New storage is consumed only when updates apply to either the original or the clone, using copy-on-write mechanics. It does not perform physical copies, does not sync data in real-time, and does not freeze the clone from modification.

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

The USE SCHEMA command sets the active schema context for the current session. After it is executed, any unqualified object names (for example, SELECT * FROM my_table) are resolved within that schema. This reduces the need to fully qualify object names with database and schema each time and ensures that statements reference the expected logical container.

CREATE SCHEMA is used to create a new schema. ALTER SCHEMA and GRANT OWNERSHIP are used to modify schema properties or transfer ownership, respectively. USE SCHEMA does not alter structure or ownership; it simply changes the context in which subsequent SQL statements are interpreted.

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

Snowflake’s file format options allow granular control over CSV ingestion. The SKIP_HEADER = 1 parameter instructs Snowflake to ignore the first line of the file, typically containing column headers. This is the correct and official parameter within FILE FORMAT objects or inline COPY INTO options. Other options listed—such as SKIP_FILE_HEADER, IGNORE_HEADER, or HEADER_SKIP—are not valid Snowflake parameters. When SKIP_HEADER is applied, Snowflake begins reading data rows starting from line 2. This ensures proper alignment between file contents and table structure during ingestion. SKIP_HEADER can also be set to values greater than 1 if multiple header rows exist. This behavior is essential when loading structured data where the header row is not intended for table consumption.

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