SnowPro Associate: Platform Question 365
Single answer○ Use a private data shareA data provider wants to give a partner read-only access to a curated sales dataset in Snowflake without copying the data. The partner already has its own Snowflake account. The provider creates a private share and adds the required database objects to it. What must the partner do next to begin querying the shared data?
- A
Create a database from the share in the consumer account, then grant privileges on that database to the partner's users or roles
- B
Clone the provider's database into the consumer account so the partner can query the shared tables locally
- C
Create a virtual warehouse in the provider account and assign it to the partner so compute can run against the shared data
- D
Create a data exchange listing and import the listing into the consumer account
Show answer and explanation
Correct answer: A
Explanation
This scenario tests the standard workflow for using a private data share in Snowflake. The provider creates a share, grants objects to the share, and adds the consumer account to the share. The consumer then creates a database from the shared data and uses its own warehouse to query it. The shared database is read-only to the consumer. This is a core Snowflake capability designed to avoid ETL or copying data between accounts. Snowflake documentation on secure data sharing describes that consumers create a database from a share and manage access with roles in their own account, while compute is billed to the consumer's warehouses.
- A. Correct.
Correct. With a private data share, the consumer must create a database from the share in its own account before users can query the shared objects. The shared database is read-only, and access is then controlled in the consumer account by granting privileges on the created database to appropriate roles.
- B. Incorrect.
Incorrect. Cloning creates a separate copy-like object within Snowflake metadata and is not how private data sharing works between provider and consumer accounts. A private share allows secure live access to provider data without copying the data into the consumer account.
- C. Incorrect.
Incorrect. Consumers use their own virtual warehouses to query shared data. The provider shares data objects, not compute resources. A common misconception is that the provider must supply compute for shared data access, but Snowflake data sharing separates storage sharing from consumer-side compute.
- D. Incorrect.
Incorrect. A private share to a specific Snowflake account does not require a data exchange listing. Listings are used in other sharing patterns, such as Marketplace or exchanges, but direct private sharing to an existing consumer account is done by the provider creating a share and the consumer creating a database from that share.