SnowPro Associate: Platform Question 366
Single answer○ Use a private data shareA data provider needs to give a business partner read-only access to several reporting tables in Snowflake without copying the data. The partner already has its own Snowflake account. The provider wants to use a private data share and ensure the partner can query only the shared objects. Which action should the provider take to make the data available to the partner?
- A
Create a share, grant USAGE on the database and schema and SELECT on the tables to the share, then add the partner's Snowflake account to the share
- B
Create a database role with SELECT privileges on the tables, grant the role to the partner's users, and let the partner query the provider's database directly
- C
Clone the reporting database into the partner's account and grant the partner ownership of the cloned objects
- D
Create a secure data exchange listing and require the partner to import the data from stage files into its own tables
Show answer and explanation
Correct answer: A
Explanation
For a private data share, the provider uses Snowflake Secure Data Sharing. The standard workflow is: create a share, grant privileges on the objects to the share, and add the consumer account to that share. The consumer then creates a database from the share and can query the shared data read-only. This approach avoids data movement or duplication and is the recommended method when both parties already have Snowflake accounts. In Snowflake documentation, key requirements include granting USAGE on the relevant database and schema and SELECT on the tables or secure views being shared. Cross-account access is not implemented by assigning roles directly to users in another account, and private sharing does not require unloading or loading data.
- A. Correct.
Correct. A private data share is the Snowflake feature designed to provide read-only access to objects without copying the underlying data. The provider creates a SHARE object, grants the required privileges to the share, such as USAGE on the database and schema and SELECT on the tables or secure views, and then adds the consumer account to the share. The consumer can then create a database from the share in its own account.
- B. Incorrect.
Incorrect. Database roles are used within an account for access control, but they are not how data is shared across Snowflake accounts through private sharing. The provider cannot simply grant a database role to users in another account and allow direct access to the provider's database.
- C. Incorrect.
Incorrect. Cloning creates a separate copy-like metadata structure inside Snowflake and is not the mechanism for private data sharing to another account. It also does not meet the requirement of sharing data without making it available as a share for controlled read-only consumption by the partner.
- D. Incorrect.
Incorrect. A secure data exchange can be used for broader data collaboration scenarios, but it is not required when the goal is to privately share existing Snowflake data directly with a known partner account. Also, private data sharing does not require exporting to stage files or importing data into the consumer's own tables.