The correct answer is B. RETURN_ROWS .
Corrected typo:
Option D contains a typing error. RETURN_ALL_ERRORSs should be RETURN_ALL_ERRORS .
When using COPY INTO < location > to unload data, VALIDATION_MODE = RETURN_ROWS returns the query results instead of unloading them to files. This is useful for validating the result set that would be unloaded.
Why B is correct:
RETURN_ROWS is the validation mode used with unload operations to return rows generated by the query.
Example:
COPY INTO @my_stage/output/
FROM (
SELECT *
FROM customers
)
VALIDATION_MODE = RETURN_ROWS;
Why the other options are incorrect:
A). RETURN_ < n > _ROWS is associated with validation behavior for loading data, not the unload query result validation mode.
C). RETURN_ERRORS returns errors and is used for validating data load errors. It does not return query results.
D). RETURN_ALL_ERRORS returns all errors in validation mode for loading scenarios. It does not return the unload query result set.
Official Snowflake documentation reference:
Snowflake documentation for COPY INTO < location > describes VALIDATION_MODE = RETURN_ROWS as returning the rows that would be unloaded.
Reference: Snowflake Documentation - COPY INTO < location > ; Snowflake Documentation - VALIDATION_MODE; SnowPro Core Study Guide - Data Loading and Unloading.
==

Snowflake warehouses can use different warehouse types and resource constraints. Snowpark-optimized warehouses use warehouse properties such as WAREHOUSE_TYPE and RESOURCE_CONSTRAINT to define the compute configuration.
Reference: Snowflake Documentation - Snowpark-optimized warehouses; CREATE WAREHOUSE; ALTER WAREHOUSE.
==

The correct answer is C. Query Acceleration Service .
The Query Acceleration Service allows Snowflake to use additional compute resources to accelerate eligible queries. It is especially useful for queries that scan large amounts of data or include expensive operations that can benefit from extra parallel processing.
Why C is correct:
Query Acceleration Service temporarily uses additional Snowflake-managed compute resources for eligible queries. This can improve performance without permanently resizing the virtual warehouse.
Why the other options are incorrect:
A). Search Optimization Service improves highly selective lookup queries by maintaining search access paths, but it does not temporarily scale compute for expensive queries.
B). A warehouse scaling policy controls how multi-cluster warehouses add or remove clusters, but it is not the feature designed to accelerate individual expensive queries.
D). A multi-cluster warehouse improves concurrency by adding clusters, but it does not split or accelerate a single complex query in the way Query Acceleration Service can.
Official Snowflake documentation reference:
Snowflake documentation describes Query Acceleration Service as a feature that can improve query performance by using additional compute resources for eligible parts of queries.
Reference: Snowflake Documentation - Query Acceleration Service; Snowflake Documentation - Warehouses; SnowPro Core Study Guide - Performance Optimization.
==

In Snowflake, you can share several types of objects with other Snowflake accounts. These include schemas, secure views, and secure user-defined functions (UDFs).Sharing these objects allows for collaboration and data access across different Snowflake accounts while maintaining security and governance controls4.

The TABLE_STORAGE_METRICS metadata table stores the storage utilization information, including for tables that have been dropped but are still incurring storage costs2.