Snowflake SOL-C01 Based on Real Exam Environment

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.

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

COPY INTO

When auto-suspend is enabled on a virtual warehouse, Snowflake automatically suspends (stops) the warehouse after it has been idle for the configured period of time. Once suspended, the warehouse stops consuming compute credits, thereby reducing costs, since Snowflake bills only for active compute usage. When new queries arrive, auto-resume (if enabled) restarts the warehouse automatically.

Auto-suspend does not change the warehouse size; scaling up or down is a separate configuration. The warehouse is not dropped—its metadata and settings remain intact. Costs may be reduced and made more efficient but are not guaranteed to “stabilize month-to-month,” as the bill still depends on actual usage and workload patterns.

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