Question 10
An organization running Snowflake reports: An external consumer sees a shared database listed but a read query fails because the receiving account role has no access to imported objects. Which design safeguard best addresses the observed risk?
Explanation
Correct Answer
This guardrail directly addresses cross-account share permissions: importing a share does not automatically grant every consumer role usage and select privileges. The prevention is: Include consumer-side role grants in the shared-dataset onboarding checklist. A separate subsystem check would not prevent the specific recurrence.
Incorrect Answers
The collaboration requirement is live governed read access rather than recurring file transfer. “Review shared-object membership and downstream consumer grants before changing a share” would address that alternative cause, not the condition in this question: importing a share does not automatically grant every consumer role usage and select privileges.
“Review shared view definitions, underlying dependencies and access tests at each release” responds to this separate finding: sharing unprotected base data would reveal more information than the collaboration needs. This question instead needs “Include consumer-side role grants in the shared-dataset onboarding checklist”, so the alternative does not meet the stated condition.
Secure Data Sharing exposes provider objects for read-only consumer use. “Communicate read-only sharing semantics and data-correction workflows before onboarding partners” applies to that separate problem. The observed case is an external consumer sees a shared database listed but a read query fails because the receiving account role has no access to imported objects; choosing this alternative would address the wrong failure mode.