Skip to content

Sharing data with another account while keeping it protected

Snowflake enables secure data collaboration through the Snowflake Marketplace and Secure Data Sharing, allowing organizations to share live data without copying or moving it between accounts. Data protection features like row access policies, dynamic data masking, and object tagging help govern who can see what data, while maintaining a single source of truth. These capabilities work together to support governed collaboration both within and across organizational boundaries.

1 · Learn the must-know

  • Secure Data Sharing lets providers share database objects (tables, views, secure UDFs) with consumers via shares, without physically copying data, so consumers always see live, up-to-date data.
  • Data shared via Secure Data Sharing does not count against the consumer's storage costs, but consumers do pay for the compute (virtual warehouses) they use to query shared data.
  • The Snowflake Marketplace allows providers to publish listings (free or paid) that any Snowflake account can discover and access, extending sharing beyond direct account-to-account relationships.
  • Reader accounts allow a data provider to share data with consumers who do not have their own Snowflake account, with the provider typically bearing the compute costs.
  • Row access policies and dynamic data masking are applied at the schema/object level and are enforced consistently even when the underlying data is shared, ensuring consistent protection across direct queries and shares.
  • Object tagging combined with masking policies enables tag-based centralized governance, letting administrators apply a masking policy to a tag once and have it automatically enforce on all columns/objects carrying that tag, including in shared contexts.

2 · Check your understanding

Check this objectiveFree · always available

A Snowflake Practitioner in the provider account creates a share named SALES_SHARE containing one table and grants it to a business partner that has no existing Snowflake account. The partner needs read-only SQL access to the shared data without provisioning any Snowflake infrastructure or incurring compute costs of their own. The provider's account administrator must retain full control over the consumer's warehouse sizing and billing. Which approach should the Practitioner use?

Your objective map0 tried · 0 answered correctly · 19 untouched

What you have tried across SnowPro Core's objectives, not a readiness score.

Snowflake AI Data Cloud Features and Architecture31% of the exam0 of 6 tried
Account Management and Data Governance20% of the exam0 of 3 tried
Data Loading, Unloading, and Connectivity18% of the exam0 of 3 tried
Performance Optimization, Querying, and Transformation21% of the exam0 of 4 tried
Data Collaboration10% of the exam0 of 3 tried

3 · Keep going