To unload data from a table into one or more files in a named stage, the COPY INTO <location> command should be used. This command exports the result of a query, such as selecting all rows from a table, into files stored in the specified stage. The COPY INTO command is versatile, supporting various file formats and compression options for efficient data unloading.
References:
Snowflake Documentation: COPY INTO Location

The purpose of the Snowflake SPLIT_TO_TABLE function is to split a string based on a specified delimiter and flatten the results into rows. This table function is useful for transforming a delimited string into a set of rows that can be further processed or queried5.

To temporarily bypass an active network policy by configuring the user object propertyMINS_TO_BYPASS_NETWORK_POLICY, the minimum set of privileges required is having the ACCOUNTADMIN role. This role has the necessary privileges to make such changes, including modifying user properties that affect network policies.
Snowflake Documentation: Network Policy Management

When a query containing a WHERE clause is running longer than expected, and the Query Profile shows that all micro-partitions are being scanned, the query can be optimized by adding a clustering key to the table.
Understanding Micro-Partitioning in Snowflake:
Snowflake automatically partitions tables into micro-partitions for efficient storage and query performance.
Each micro-partition contains metadata about the range of values it holds, which helps in pruning irrelevant partitions during query execution.
Role of Clustering Keys:
A clustering key defines how data in a table is organized within micro-partitions.
By specifying a clustering key, you can control the physical layout of data, ensuring that related rows are stored together.
This organization improves query performance by reducing the number of micro-partitions that need to be scanned.
Optimizing Queries with Clustering Keys:
Adding a clustering key based on columns frequently used in WHERE clauses helps Snowflake quickly locate and scan relevant micro-partitions.
This minimizes the amount of data scanned and reduces query execution time.
Example:
ALTER TABLE my_table CLUSTER BY (column1, column2);
This command adds a clustering key tomy_tableusingcolumn1andcolumn2.
Future queries that filter on these columns will benefit from improved performance.
Benefits:
Reduced query execution time: Fewer micro-partitions need to be scanned.
Improved resource utilization: More efficient data retrieval leads to lower compute costs.
Snowflake Documentation: Clustering Keys
Snowflake Documentation: Query Profile

Snowflake's data caching features include the ability to clear the least-recently used data when the data cache is full to make room for new data. Additionally, the RESULT_SCAN table function can access and filter the contents of the query result cache, allowing users to retrieve and work with the results of previous queries.
The other statements are incorrect: the data cache is not saved on the remote storage layer when a virtual warehouse is suspended, users can access queries from the query result cache that were run by other users, and there is no setting calledUSE_METADATA_CACHE in Snowflake. References: Caching in the Snowflake Cloud Data Platform, Optimizing the warehouse cache