ADA-C01 Question 431
Single answerDomain 5.0: Data Sharing and Snowflake Marketplace (7%)A data provider uses Secure Data Sharing to deliver curated sales data to several external customers. One customer reports that a newly added table in the provider's shared database is not visible in their consumer account, even though existing shared objects are accessible. The provider confirms that the table was created in a schema that is already part of the share. The provider wants the new table to become available to all current consumers with the least operational effort and without recreating consumer databases. What should the administrator do?
- A
Grant SELECT on the new table to the share and ensure USAGE is still granted on the database and schema containing the table
- B
Recreate the consumer databases from the share so the metadata refresh includes the new table
- C
Convert the share to a listing in Snowflake Marketplace so consumers automatically receive new objects
- D
Clone the provider database into a new database, add the new table there, and replace the existing share with the clone
Show answer and explanation
Correct answer: A
Explanation
This question tests practical administration of Secure Data Sharing. In Snowflake, a share contains explicit grants to databases, schemas, and objects. If a new table is created in a schema already available through the share, the provider must still grant SELECT on that specific table to the share. USAGE on the database and schema is also required for consumers to access the object. Consumers do not need to recreate their databases created from the share; updates to the share are reflected automatically once grants are in place. This is a common real-world misconception: administrators often assume that placing a table in a shared schema is sufficient by itself. Snowflake documentation on Secure Data Sharing and GRANT ... TO SHARE behavior makes clear that object-level privileges must be granted explicitly for shared access.
- A. Correct.
Correct. In Secure Data Sharing, adding a new object to an existing shared schema requires granting the appropriate privileges on that object to the share. For tables and secure views, that typically means granting SELECT on the object to the share, while the share must also retain USAGE on the parent database and schema. Consumers do not need to recreate their databases to see newly granted objects; the shared database metadata is updated as the provider modifies the share.
- B. Incorrect.
Incorrect. Consumer accounts do not need to recreate databases created from a share when the provider adds new objects and grants them to the share. Shared objects become visible once the provider updates share privileges appropriately. Recreating consumer databases would add unnecessary operational overhead and is not the recommended approach.
- C. Incorrect.
Incorrect. Snowflake Marketplace listings are a distribution mechanism, but converting an existing direct share to a Marketplace listing is not required to expose a newly added object to current data sharing consumers. Marketplace does not change the underlying need to grant privileges on shared objects. This option confuses the delivery channel with object-level access management.
- D. Incorrect.
Incorrect. Cloning and replacing the shared source is unnecessary and operationally disruptive. Secure Data Sharing is designed so providers can incrementally add objects to an existing share by granting privileges on those objects. Replacing the share source could introduce avoidable complexity and potential governance issues.