COF-C03 Snowflake Secure Data Sharing: Shares, Listings, and Reader Accounts

About this video

Snowflake Secure Data Sharing lets organizations expose live, governed data to consumers without creating physical copies of the underlying tables. In this video, we break down how Snowflake collaboration works for the SnowPro Core COF-C03 exam, including Direct Shares, Listings, Reader Accounts, provider and consumer responsibilities, and secure object design. We’ll cover: Snowflake Secure Data Sharing Zero-copy sharing Share objects Imported databases Provider vs. consumer responsibilities Direct Shares Listings Snowflake Marketplace Cross-cloud distribution Reader Accounts Consumer compute responsibilities Secure Views Masking and row-access controls Troubleshooting shared-data access Common COF-C03 collaboration mistakes One of the most important distinctions is that Secure Data Sharing does not physically copy the provider’s table data into the consumer account. The provider grants access to selected objects through a share, while the consumer creates an imported database and normally uses its own virtual warehouse to query the shared data. Reader Accounts work differently. They are intended for consumers without their own Snowflake account, and the provider administers the environment and pays for the associated compute. You should also distinguish sharing from cloning. A Zero-copy Clone creates an independent object for local use, while Secure Data Sharing provides live, read-only access across provider and consumer boundaries. For COF-C03, focus on choosing the correct collaboration model: Known Snowflake consumer → Direct Share Packaged or discoverable distribution → Listing Consumer without Snowflake → Reader Account Then trace the complete access path from provider grants to the consumer’s imported database and local roles. #Snowflake #COFC03 #SnowProCore