What is the maximum duration of data retention using Time Travel in Snowflake for standard accounts?
Answer(s): B
For Snowflake Standard Edition accounts, the maximum Time Travel retention period is1 day(24 hours). Time Travel allows users to query historical data, restore dropped objects, and clone objects at a point in time. Although the retention period can be adjusted at the account, database, schema, or table level, Standard Edition restricts the upper limit to 1 day. A value of 0 disables Time Travel entirely. A 7-day retention period applies to Fail-safe, not Time Travel, and Fail-safe is a disaster- recovery mechanism managed exclusively by Snowflake. The 90-day Time Travel retention is available only for Enterprise Edition and above. Therefore, the correct maximum retention period for Standard Edition is 1 day.=====================
What is a "provider" in the context of the Snowflake Marketplace or Data Exchange?
Answer(s): C
In Snowflake Marketplace and Data Exchange, aprovideris any Snowflake user or organization that publishes and shares datasets, data products, or applications with other Snowflake consumers. Providers control access to their listings, configure data sharing models, and can offer either free or paid data products. They manage listing descriptions, update schedules, and refresh logic, ensuring customers or subscribers receive up-to-date and reliable information. Providers can be enterprises, analytics vendors, public data contributors, or research institutions. They are distinct from consumers, who access or use the shared data. Providers also do not handle Snowflake platform infrastructure--that is Snowflake's responsibility. Snowflake employees are not categorized as providers unless they publish official Snowflake datasets. Thus, the primary purpose of a provider is to share curated data offerings on the Marketplace or within private exchanges.=====================
Which of the following is true about data listings in the Snowflake Marketplace?
Data listings in the Snowflake Marketplace can be offered asfree or paiddepending on how the provider chooses to distribute the data. Providers can use usage-based pricing, subscription models, or make datasets available at no cost. Listings are not restricted to static data; Snowflake supportslive data sharing, enabling instant access to continuously updated datasets without copying or ETL. Listings are accessible to any Snowflake user with the appropriate marketplace access--not exclusively administrators. This flexibility makes the Marketplace a powerful ecosystem where organizations can seamlessly obtain external datasets for analytics, machine learning, and reporting needs. Providers define terms of use, pricing, and refresh schedules, while Snowflake manages the secure data-sharing infrastructure.=====================
What is the key difference between a "private listing" and a "public listing" in a Snowflake Data Exchange context?
Aprivate listingis shared only with explicitly selected Snowflake accounts, giving providers fine- grained control over who can access their data. This is ideal for partner organizations, internal business units, or customers requiring restricted access. Apublic listing, on the other hand, is accessible to all Snowflake users via the Marketplace, making it available for broad distribution. Pricing models for both types can be free or paid; neither category inherently requires payment. Both listing types share data, not code. Public listings are not restricted to Snowflake employees-- they are open to the entire Snowflake ecosystem. The distinction lies entirely in access scope:targeted (private) vs. universal (public).=====================
How is the initial activation of the Snowflake Data Exchange feature, which is necessary for establishing private exchanges, typically accomplished?
The Data Exchange feature is not automatically enabled for all Snowflake accounts. Instead, enabling this capability--particularly for private exchanges--typically requires submitting a request toSnowflake Support. Snowflake evaluates account type, region, and compliance requirements before enabling the Data Exchange functionality. Snowflake administrators cannot independently enable this through Snowsight, nor is there a SQL command available to turn it on. Once activated, account administrators can create private exchanges, manage listings, and define which Snowflake accounts can participate. This activation step ensures secure, intentional use of data-sharing capabilities at an account level.=====================
What does "warehouse scaling in/out" refer to in Snowflake?
Answer(s): D
Scalingin/outin Snowflake refers to modifying thenumber of compute clustersassociated with a multi-cluster virtual warehouse. Scalingoutincreases cluster count to accommodate higher concurrency or workload spikes, allowing more queries to run simultaneously without queuing. Scalinginreduces cluster count during periods of lower demand, optimizing compute usage and costs. This is distinct fromscaling up/down, which refers to changing warehouse size (e.g., Small,Medium). Scaling does not involve data movement or region changes; warehouse compute is stateless and operates independently of storage. Multi-cluster warehouses allow Snowflake to automatically add or remove clusters based on demand when auto-scale policies are configured.=====================
Which of the following are benefits of using a multi-clustered warehouse in Snowflake? (Choose any 3 options)
Answer(s): A,B,D
A multi-cluster warehouse raises Snowflake's capability to handle concurrent workloads efficiently. When large numbers of users or queries hit the system, Snowflake can automatically start additional clusters (scaling out) to distribute workloads, reducing queuing and improving performance. As query demand drops, Snowflake scales in by shutting down clusters to conserve credits. This dynamic auto-scaling provides significantly increased compute capacity during peak usage periods and enhances responsiveness. Importantly, multi-cluster warehouses affect only compute, not storage, so they do not reduce storage costs. Their primary benefits revolve around performance stability, concurrency handling, workload isolation, and compute elasticity.=====================
Which command is used to create a new virtual warehouse in Snowflake?
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.=====================
Post your Comments and Discuss Snowflake SnowPro Associate Platform SOL-C01 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the SnowPro Associate Platform SOL-C01 content, but please register or login to continue.