Which action allows a role that owns objects in a share but is not the share owner to access those objects?

• A. Revoking the USAGE or SELECT privileges with CASCADE on the objects from the share owner.
• B. Block access by revoking privileges on the objects from the share.
• C. Contacting Snowflake support to revoke privileges of the owner of the share.
• D. Creating a new share to bypass restrictions.

Answer: (A)

The key idea is how privileges flow when data is shared in Snowflake. Access to objects that come from a share is controlled by grants tied to the share. Even if a role owns the underlying objects, that ownership doesn’t automatically override the share’s access path unless the grants allowing access are in place or removed appropriately.

Revoking the USAGE or SELECT privileges on the shared objects from the share owner, using CASCADE, directly alters the grants that govern access through the share. The CASTCADE part ensures that all dependent grants tied to that path are removed as well, effectively clearing the restriction that the share imposes. With those restrictions lifted, the role that owns the objects can access them, because ownership implies inherent access to the object itself once the share-based grant path is no longer blocking it.

Blocking access by revoking privileges would do the opposite, preventing access. Contacting Snowflake support is unnecessary for normal privilege management. Creating a new share wouldn’t grant access to objects already governed by the existing share’s grants.