The SnowPro Associate: Platform Certification Exam (SOL-C01)

An external stage is the Snowflake object that encapsulates a secure connection to external cloud storage such as Amazon S3, Azure Blob Storage, or Google Cloud Storage. It stores the location (URL or bucket path) and, where required, credentials or role-based access configuration, and may also reference a file format. External stages are used as the source or target for COPY INTO operations when loading from or unloading to external storage.

An external table provides a logical SQL interface to data stored externally but relies on a stage for connectivity; it does not itself define the connection. A directory table exposes metadata about files stored in a stage, not the connection. A named file format defines parsing rules (type, delimiter, compression) but has no knowledge of or connection to a specific external storage location.

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

In Snowflake Notebooks, a Markdown cell is a non-executable cell type used for formatted text. It allows the user to format text using Markdown syntax, including headings, lists, tables, emphasis, inline code, and links. This makes it possible to document the analysis, describe steps, and provide commentary alongside SQL and Python cells, improving clarity and collaboration.

Markdown cells do not execute code in “more than one computer language”; they are not code cells at all. Notebook cells are not nested; each cell exists as a separate element in the notebook. There is no concept of “older data” associated specifically with Markdown cells; they simply store text content defined by the user.

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

The correct SQL command for creating a new database in Snowflake isCREATE DATABASE database_name;. This initializes a new logical container for schemas and objects. USE DATABASE switches the active database context but does not create one. Snowflake does not support the shorthand CREATE DB or USE DB syntax. Therefore, CREATE DATABASE is the correct and only valid command for creating a database.

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

Every query executed in Snowflake is assigned a uniqueQuery ID, a system-generated identifier that allows users to retrieve, analyze, and reference the query. Query IDs support debugging, profile retrieval, audit tracking, workload analysis, and support cases.

Transaction IDs are only assigned to transactional operations and do not uniquely identify all queries.

Session IDs identify user sessions—not individual queries. Many queries can occur in the same session.

Account ID is the identifier for the entire Snowflake account and does not relate to specific queries.

Thus,Query IDis the unique attribute used to identify each query in Query History.

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

The default Time Travel retention period for most objects in Snowflake is1 day(24 hours). Time Travel enables access to historical versions of data after updates, deletes, or drops. It also allows cloning databases, schemas, and tables at previous points in time, and recovering dropped objects.

While Snowflake Enterprise Edition and higher tiers allow retention periods up to 90 days, this extended window is not the default—administrators must explicitly configure it for each table, schema, or database.

Retention periods of 7, 45, or 90 days are possible only with higher service editions; the default for all accounts and objects remains 1 day unless explicitly overridden.

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

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.

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

Snowflake supports theEXCLUDEkeyword to simplify queries when excluding certain columns from a SELECT * operation. SELECT * EXCLUDE (column1, column2) reduces verbosity and enhances maintainability, especially when table schemas evolve. Explicitly listing all columns is possible but inefficient. Snowflake does not support REMOVE functions for columns nor an OMIT clause. EXCLUDE is the correct and official mechanism.

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

Snowsight includes a modern, fully capableSQL editordesigned for rich query development, execution, and analysis. The editor offers features such as syntax highlighting, intelligent auto-complete, contextual error display, and result-set visualization. Users can organize work with worksheets, folders, tagging, and versioning-like behavior.

Snowsight is built for both simple and complex SQL workloads. It supports multi-statement execution, script-like workflows, stored procedure development, materialized views, and advanced analytics queries.

Unsupported options include:

Manual data storage configuration: Snowflake abstracts storage management completely.

Pre-built queries only: Snowsight allows fully custom SQL.

Limited to simple queries: It supports enterprise workloads, BI query chains, and operational SQL.

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

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

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