MockCertMockCert
Menu

Snowflake conceptsSnowPro CoreData sharing

SnowPro Core data collaboration: sharing and Marketplace

What SnowPro Core asks about data sharing: direct shares, listings and reader accounts, what a share can hold, and the limits consumers run into.

By MockCert Editorial3 min readPublished Oct 27, 2026 · Updated Nov 1, 2026

Shared data takes up no storage in the consumer account, so consumers pay only for compute. Yet a direct share works only within one region.

01 What does SnowPro Core test about sharing data?

A partner needs your data tomorrow, and all four sharing options sound right. First see this domain's share of the exam, then what every share has in common.

How much of the exam each domain covers

The whole exam

  1. 1.0Snowflake AI Data Cloud Features and Architecture31%
  2. 2.0Account Management and Data Governance20%
  3. 3.0Data Loading, Unloading, and Connectivity18%
  4. 4.0Performance Optimization, Querying, and Transformation21%
  5. 5.0Data Collaboration10%
Weigh this domain against the others before you plan your time on sharing.

Save the 'How much of the exam each domain covers' graphic as a PNG image PNG for LinkedIn or Pinterest

The kinds of sharing compared

Direct share

  • Same region only
  • Read-only for the consumer

Listing

  • Marketplace or private listing
  • Crosses regions with auto-fulfillment

Reader account

  • Belongs to the provider that made it
  • Consumes data only from that provider
Region decides between a direct share and a listing; a reader account reads only from the provider that made it.

Shared objects are read-only, and the consumer pays only for compute.

02 Which kind of sharing fits which case?

Once the basics are clear, the case decides the method: across regions or clouds, a listing with cross-cloud auto-fulfillment replaces a direct share.

A private listing reaches specific accounts, and a reader account consumes data only from the provider that created it.

A consumer in another region means a listing, not a direct share.

03 What should go into a share?

Next come the contents. Snowflake strongly recommends sharing secure views or secure UDFs, not tables. Streams cannot be shared directly.

Database roles in a share let consumers give groups different subsets, but a shared database role does not support future grants.

Share secure views rather than raw tables, and never streams.

04 What limits apply once data arrives?

Last, the consumer side has traps. A consumer can create only one database per share, and that database cannot be replicated.

Before your next mock exam, take each sharing question you miss and name the provider, the consumer and their regions first.

One database per share, and that database cannot be replicated.

Summary

  1. Direct shares stay in one region; listings can cross regions and clouds.
  2. Share secure views or secure UDFs rather than tables.
  3. Databases created from shares cannot be replicated.

Sources and editorial status

Research checked Nov 1, 2026.

  1. About Secure Data Sharing | Snowflake Documentation
  2. About the Snowflake Native App Framework | Snowflake Documentation
  3. Use secure objects to control data access | Snowflake Documentation
  4. Share secure database objects | Snowflake Documentation
  5. Introduction to database replication across multiple accounts | Snowflake Documentation