What will be returned when a user runs this command?SELECT count FROM my_table LIMIT 10;
Answer(s): A
When a LIMIT clause is applied without an ORDER BY, Snowflake does not guarantee which rows will be returned. This means the result of:SELECT count FROM my_table LIMIT 10;is anon-deterministic set of 10 rows. Because Snowflake stores data in micro-partitions and distributes processing across compute resources, the natural order of rows is undefined unless explicitly controlled.To retrieve the lowest or highest values, users must specify ORDER BY count ASC or ORDER BY count DESC respectively. Without ordering, Snowflake simply returnsany10 qualifying rows.· Option B (highest values) requires ORDER BY count DESC.· Option D (lowest values) requires ORDER BY count ASC.· Option C (values 10) requires a WHERE clause (WHERE count <= 10).Therefore, the query returns a non-predictable sample of 10 rows from the column, making option A correct.
How are privileges inherited in the Snowflake role hierarchy?
Answer(s): C
Snowflake uses a hierarchical Role-Based Access Control (RBAC) model. When Role A is granted toRole B, the higher-level role (Role B) inherits all privileges of the lower-level role (Role A). This upward inheritance allows broad administrative roles (such as SYSADMIN) to automatically inherit permissions granted to subordinate roles.Key principle:privilege inheritance flows upward, not downward.· Parent roles inherit from child roles.· Child roles donotinherit from parent roles.Sibling roles do not share privileges unless explicitly granted.Thus, roles above a given role in the hierarchy inherit privileges, making option C correct.Options A and D incorrectly describe downward inheritance, which Snowflake does not perform.Option B (same-level inheritance) also does not occur unless privileges are explicitly granted.This hierarchical model simplifies governance by allowing higher-level administrative roles to centrally manage access across multiple subordinate roles.
What is the purpose of Time Travel?
Answer(s): D
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.
What is Snowflake's primary security capability?
Snowflake's foundational security capability isalways-on end-to-end encryption, applied to all customer data both at rest and in transit. Snowflake encrypts data stored in micro-partitions using AES-256, and all network communication uses TLS encryption. Key management is automated through Snowflake's hierarchical key model, providing additional rotation, rekeying, and defense-in- depth mechanisms.While RBAC, masking policies, and network policies are crucial components of Snowflake security, encryption is the platform's guaranteed, baseline, mandatory protection feature. It applies universally to all data, regardless of workload, role configuration, or user settings.Option A: automated masking is optional and policy-driven, not a primary universal mechanism.Option B: network perimeter defense exists but is not the platform's core foundation.Option C: RBAC controls access but does not protect data itself.Thus, Snowflake's primary and most universal security capability is end-to-end encryption.
Changing the size of a virtual warehouse from a Medium to a Large refers to what type of warehouse tuning?
Changing a Snowflake virtual warehouse from Medium to Large increases the compute resources allocated to that warehouse--such as CPU cores, memory, and I/O bandwidth. This process is calledscaling up, or vertical scaling. It is typically performed to improve performance for complex queries, large joins, or computationally heavy workloads.Scaling down is the reverse--reducing warehouse size from Large to Medium or similar.Scaling out refers to adding more clusters to a multi-cluster warehouse, enabling increased concurrency rather than increasing power per cluster.Scaling in is the reverse of scaling out--reducing the number of active clusters.Thus, increasing the size from Medium to Large is vertical scaling, also known as scaling up.
What command can be used to load data from an external stage to a table?
TheCOPY INTOcommand is Snowflake's primary bulk-loading mechanism for ingesting data from stages (internal or external) into tables. It can read from Amazon S3, Azure Blob Storage, Google Cloud Storage, or internal Snowflake stages. COPY INTO supports file formats (CSV, JSON, Parquet), pattern matching, error handling, transformations, and validation modes.PUT uploads filesfrom a local machineto an internal stage--not from stage to table.GET downloads files from an internal stage to a local system.INSERT INTO is for row-by-row inserts and is not designed for large file ingestion.Therefore, COPY INTO is the correct and recommended method for loading stage files into Snowflake tables.
In the Snowsight Query History, what attribute uniquely identifies each query?
Answer(s): B
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.
What is a share?
Asharein Snowflake is a securable object that contains all the metadata required to provide access to selected data--typically tables, views, and secure views--to other Snowflake accounts. The share object defines which objects are included and what privileges (e.g., SELECT, USAGE) consumers receive.A share does not store data itself; it provides a reference to the provider's underlying micro- partitioned storage, enabling real-time, zero-copy access.Reader accounts (option A) can consume shares but do not define them.Replication objects (option C) relate to database replication, not data sharing.Option D is incorrect because Snowflake does not generate share-specific metrics objects.Thus, the purpose of a share is to encapsulate all metadata required for secure, controlled data sharing between Snowflake accounts.
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.