A company using Snowflake works with a third party that provides economic data. The third-party provider recently moved their data to Snowflake. How can the company access the third-party data in…

Question

Options

• AHave the data provider enable database replication so the company can create a replica of the
• BHave the data provider create a share object and add the company's Snowflake account to the
• CHave the data provider create a listing on the Snowflake Marketplace so the company can
• DHave the data provider create a new user and role specifically for the company so the company

• A
  3% (1)
• B
  72% (26)
• C
  17% (6)
• D
  8% (3)

Explanation

Option B is correct because Snowflake's native Secure Data Sharing feature allows a data provider to create a share object and grant access to a specific consumer account - the consumer can immediately query the live data with zero ETL, no data movement, and no copies to maintain, making it the lowest-overhead solution available entirely within Snowflake.

• Option A (database replication) is wrong because replication creates a full copy of the data in the consumer's account, incurring storage costs and requiring ongoing sync management - more overhead, not less.
• Option C (Marketplace listing) is technically possible but adds unnecessary overhead: publishing to the Marketplace is designed for broad public distribution, not a direct one-to-one sharing relationship with a known partner.
• Option D (new user/role) is wrong because it requires the provider to manage credentials, grant permissions, and maintain that user - this is the most operationally heavy option and also crosses account boundaries in a non-native way.

Memory tip: Think of Secure Data Sharing as "giving someone a key to your room, not a copy of your furniture" - the data stays in one place, the consumer just gets read access, so there's nothing to sync, copy, or manage.

No community discussion yet for this question.