ADA-C01 Question 449
Single answerConfigure data sharing programmaticallyA data provider wants to automate onboarding of new consumers to a secure data share. The provider has already created a share named SALES_SHARE and granted SELECT on the required objects to the share. A Python script running under an administrative role must add a specific consumer account to the share and make the shared database visible to that consumer without using Snowsight. Which SQL command should the script execute next to complete this task?
- A
ALTER SHARE SALES_SHARE ADD ACCOUNT = XY12345;
- B
GRANT IMPORTED PRIVILEGES ON DATABASE SALES_DB TO ACCOUNT XY12345;
- C
CREATE DATABASE SALES_DB FROM SHARE SALES_SHARE;
- D
ALTER DATABASE SALES_DB SET SHARES = (SALES_SHARE, XY12345);
Show answer and explanation
Correct answer: A
Explanation
To configure secure data sharing programmatically, the provider typically follows this sequence: create the share, grant USAGE on the database and schema plus SELECT on supported objects to the share, and then add one or more consumer accounts to the share using ALTER SHARE ... ADD ACCOUNTS. After that, the consumer creates a database from the share with CREATE DATABASE
- A. Correct.
Correct. On the provider side, adding a consumer account to an existing share is done with ALTER SHARE ... ADD ACCOUNTS = <account_locator> (or the account identifier format supported for the cloud/region context). Once the account is added to the share, the consumer can create a database from that share in their own account. This is the programmatic step the provider must perform after creating the share and granting object privileges to it.
- B. Incorrect.
Incorrect. IMPORTED PRIVILEGES are granted in the consumer account on a database created from a share, typically to allow roles in the consumer account to use the shared database. They are not used by the provider to add an account to a share. This option reflects a common confusion between provider-side sharing configuration and consumer-side access control.
- C. Incorrect.
Incorrect. CREATE DATABASE ... FROM SHARE is executed in the consumer account, not the provider account. The provider cannot make the database appear inside the consumer account by running this statement in its own account. The provider's responsibility is to add the consumer account to the share; the consumer then creates the database from the share.
- D. Incorrect.
Incorrect. Snowflake does not configure shares by setting a SHARES property on a database. Data sharing is managed through SHARE objects and grants to those shares. This distractor targets the misconception that sharing is a database attribute rather than a separate securable object workflow.