Snowflake consumer accounts cannot directly modify ownership or assign ordinary object-level grants to secure views owned by a provider in an imported shared database.
For conventional shares where objects are granted directly to the share, granting IMPORTED PRIVILEGES exposes the available shared objects to the recipient role. It does not provide selective grants on individual shared secure views.
Option D is the appropriate solution under this access model. The consumer administrator can create wrapper views in a locally owned database, reference the appropriate provider views, and grant access to each wrapper according to the organization's role-based access requirements.
The role owning these wrapper views must possess the necessary access to the imported database. End-user roles can then receive SELECT privileges on the appropriate local views without being granted unrestricted imported-database access.
Option A is incorrect because consumers cannot directly administer the provider's shared object privileges.
Option B incorrectly treats IMPORTED PRIVILEGES as an individual schema-level grant.
Option C introduces unnecessary data duplication and does not describe the appropriate mechanism for managing access to incoming shared views.
Current-version qualification: Snowflake now supports database roles shared by providers. When the provider has segmented shared objects using database roles, the consumer can grant those imported database roles to local account roles. That is a more direct approach, but it is not offered among the answer choices.
Official Snowflake references: Consume Imported Data; Share Secure Database Objects; Access Control Privileges.
Submit