A company needs to share its product catalog data with one of its partners. The product catalog data is stored in two database tables: product_category, and product_details. Both tables can be joined

Question

Options

• AUse Secure Data Sharing with an S3 bucket as a destination.
• BPublish product_category and product_details data sets on the Snowflake Marketplace.
• CCreate a database user for the partner and give them access to the required data sets.
• DCreate a reader account for the partner and share the data sets as secure views.

• A
  8% (4)
• B
  16% (8)
• C
  6% (3)
• D
  70% (35)

Explanation

The key constraints are: (1) the partner is NOT a Snowflake customer, (2) access must be governed so only this partner sees their authorized records, (3) cost-effectiveness is required, and (4) the partner uses Amazon S3. A Snowflake Reader Account (Option D) is specifically designed for this scenario: it allows a non-Snowflake customer to query shared Snowflake data through a Snowflake-managed account at no licensing cost to the partner - the data provider's account covers compute. Sharing the data as Secure Views ensures the partner can only query the view definition (not the underlying tables directly) and that the SQL logic governing which records are visible is enforced server-side. This satisfies both governance and the fact that the partner has no Snowflake account. Option A is incorrect because Secure Data Sharing operates between Snowflake accounts, not to S3 buckets - data cannot be 'shared' to S3 via this mechanism. Option B (Marketplace) is for broad distribution to many consumers, not governed single-partner access. Option C (creating a database user) is insecure, requires the partner to have Snowflake access setup, and is not governed at the record level.

No community discussion yet for this question.