When a SnowflakeBusiness Critical (BC)edition account shares data, it must followdata sharing restrictionsdesigned to maintain thehigher level of compliance and securityguaranteed by BC.
Bydefault, BC accounts canonly share data with other BC (or higher)accounts, to maintain consistent security and compliance (e.g., HIPAA, HITRUST, FedRAMP).
However,an exceptioncan be madeif a user with the proper privilegeexplicitly disables the restriction.
Key Concept: share_restrictions
Snowflake enforcesdata sharing restrictionsby default forBC accounts.
Arole with the OVERRIDE SHARE RESTRICTIONS global privilegecan bypass this by setting theshare_restrictions = FALSEwhen adding the target account.
Correct Option: D
This is correct because:
The usermust have a role with the OVERRIDE SHARE RESTRICTIONS privilege.
That user can thenset share_restrictions = FALSEwhen adding the Enterprise edition consumer account.
Official Documentation Extract:
"If the data provider is a Business Critical (or higher) account, Snowflake enforces a restriction by default that only allows sharing data with other Business Critical (or higher) accounts. A user in the provider account with a role that has the global privilege OVERRIDE SHARE RESTRICTIONS can override this restriction by explicitly setting SHARE_RESTRICTIONS = FALSE when adding the consumer account."
Source:Snowflake Docs – CREATE SHARE
Why Other Options Are Incorrect:
A.Incorrect – This is not absolute. Business Critical accountscanshare data with Enterprise accounts,if the restriction is explicitly overridden.
B.Incorrect – Simply having authority to create or alter a share isnot enough. You must have the OVERRIDE SHARE RESTRICTIONS privilege and set the restriction explicitly.
C.Incorrect – Setting share_restrictions = FALSE is required, but theprivilege to overridemust also be held by the role. Without the privilege, the action will fail.
[References:, CREATE SHARE – SHARE_RESTRICTIONS Parameter, Snowflake Editions Comparison, Managing Shares and Data Sharing Restrictions, , , , ]