When sharing data in Snowflake, the provider needs to grant the following privileges along with a share:
A . USAGE on the specific tables in the database: This privilege allows the consumers of the share to access the specific tables included in the share.
D . USAGE on the database and the schema containing the tables to share: This privilege is necessary for the consumers to access the database and schema levels, enabling them to access the tables within those schemas.
These privileges are crucial for setting up secure and controlled access to the shared data, ensuring that only authorized users can access the specified resources.
Reference to Snowflake documentation on sharing data and managing access:
Data Sharing Overview
Privileges Required for Sharing Data

The COPY command in Snowflake allows for the reordering of columns as they are loaded into a table, and it also permits the omission of columns from the source file during the load process. This provides flexibility in handling the schema of the data being ingested. References: [COF-C03] SnowPro Core Certification Exam Study Guide

To verify the privileges that have been granted to a specific role in Snowflake, the correct SQL command is SHOW GRANTS TO ROLE <Role Name>. This command lists all the privileges granted to the specified role, including access to schemas, tables, and other database objects. This is a useful command for administrators and users with sufficient privileges to audit and manage role permissions within the Snowflake environment.
References:
Snowflake Documentation: SHOW GRANTS

The correct answer is B. GET_PRESIGNED_URL(@ < stage_name > , ' < relative_file_path > ' , [ < expiration_time > ]); .
A pre-signed URL provides temporary access to a staged file. This is useful when users or applications outside Snowflake need access to a file for a limited period of time.
Why B is correct:
GET_PRESIGNED_URL generates a pre-signed URL for a staged file. The URL can be used to access the file without the user needing a Snowflake account, as long as the URL has not expired.
Example:
SELECT GET_PRESIGNED_URL(@my_stage, ' folder/file.csv ' , 3600);
This generates a URL that is valid for a limited time, such as 3600 seconds.
Why the other options are incorrect:
A). BUILD_STAGE_FILE_URL creates a Snowflake file URL, but it does not provide the same temporary external access behavior as a pre-signed URL.
C). GET_RELATIVE_PATH returns the relative path of a staged file, not an access URL.
D). BUILD_SCOPED_FILE_URL creates a scoped URL that is useful within Snowflake-controlled contexts, but for users without Snowflake accounts who need direct temporary access, GET_PRESIGNED_URL is the best answer.
Official Snowflake documentation reference:
Snowflake documentation describes GET_PRESIGNED_URL as a function that returns a pre-signed URL for a staged file, with an optional expiration time.
Reference: Snowflake Documentation - GET_PRESIGNED_URL; Snowflake Documentation - File functions; SnowPro Core Study Guide - Data Loading and Unloading.
==

To optimize query performance on external tables, you can define a materialized view on top of the external table. Snowflake will manage and cache the result for faster retrieval.
Reference:
Snowflake Docs: External Tables with Materialized Views