The correct answers are C. Data is not transferred between accounts and D. Consumer account will incur compute costs .
Important correction:
The provided answer A, B is not correct.
Secure Data Sharing allows data providers to share selected database objects with consumer accounts without copying or transferring the underlying data. Consumers query the shared data using their own virtual warehouses, so the consumer generally pays for the compute used to query the share.
Why C is correct:
With Secure Data Sharing, the provider’s data remains in the provider account. Snowflake shares metadata and access, not a physical copy of the data.
Why D is correct:
Consumers use their own compute resources to query shared data. Therefore, the consumer account incurs compute costs when querying the share.
Why the other options are incorrect:
A. Regular, non-secure views generally cannot be shared in the standard secure sharing model. Views shared with consumers should be secure views, unless specific account-level settings allow non-secure objects. The general SnowPro Core concept is that secure views are used to share view logic safely.
B. Sensitive data is not automatically masked simply because data is shared. Masking policies or secure views must be designed and applied intentionally.
E. Reader accounts can query shared data but cannot edit the provider’s source data.
Official Snowflake documentation reference:
Snowflake documentation explains that Secure Data Sharing does not copy or move data between accounts. Consumers use their own warehouses to query shared data, while providers retain control of the shared objects.
[Reference: Snowflake Documentation — Secure Data Sharing; Snowflake Documentation — Shares and consumer accounts; Snowflake Documentation — Secure views; SnowPro Core Study Guide — Data Protection and Governance., ========================]
