ADA-C01 Question 485
Single answer5.2 Implement and manage the Snowflake MarketplaceA Snowflake administrator at a data provider company is preparing to list a paid data product on the Snowflake Marketplace. The provider wants to expose only a curated subset of tables to consumers, avoid giving consumers direct access to the underlying source schema, and ensure new consumers can be onboarded without manually creating a separate secure share each time. Which approach should the administrator take?
- A
Create a listing backed by a data exchange, and grant consumers imported privileges so they can see only the approved objects.
- B
Create a share directly on the source schema and publish that share as a Marketplace listing so consumers inherit access only to visible objects.
- C
Create a database from the source data, build a secure view layer exposing only approved data, add those objects to a share, and use that share to create the Marketplace listing.
- D
Replicate the source database to each target consumer account and manage access through account-level roles after the listing is published.
Show answer and explanation
Correct answer: C
Explanation
The best answer is to create a curated data product layer, typically using secure views, place the approved objects in a share, and then create the Snowflake Marketplace listing from that share. This approach supports the provider's goals: limiting exposure to a subset of data, hiding the underlying source schema design, and scaling consumer onboarding through the Marketplace rather than by manually provisioning separate shares for each consumer.
In Snowflake, Marketplace listings are provider-managed products that are generally backed by secure data sharing constructs. Providers should expose only the objects intended for consumers and commonly use secure views to present curated datasets while protecting underlying tables and logic. This is aligned with Snowflake guidance for secure data sharing and listing creation in the Marketplace.
Relevant Snowflake documentation areas include: creating and managing listings in the Snowflake Marketplace, secure data sharing, and secure views for controlled data exposure. These topics emphasize designing a clean provider-facing shared dataset rather than sharing raw source schemas directly.
- A. Incorrect.
Incorrect. A data exchange is a mechanism for collaboration and discovery, but it is not the key control needed here. Imported privileges are used by consumer accounts to access shared databases, not by providers to restrict exposure within a Marketplace product. This option also does not address the requirement to avoid exposing the underlying source schema through a curated object layer.
- B. Incorrect.
Incorrect. Publishing a share from the source schema can expose underlying structures more directly than intended and does not meet the requirement for a curated abstraction layer. Best practice for providers is typically to expose only the intended data product objects, often through secure views or other controlled objects in a separate database or schema, rather than sharing the raw source schema directly.
- C. Correct.
Correct. For a Marketplace listing, the provider typically creates a share that contains only the intended objects for consumers. Using a separate database and a secure view layer allows the provider to curate and mask the underlying implementation details while exposing only approved data. A Marketplace listing backed by that share enables scalable onboarding of new consumers without manually creating a separate secure share per consumer; consumers access the product through the listing workflow.
- D. Incorrect.
Incorrect. Replicating a database to each consumer account is not how Snowflake Marketplace listings are normally implemented. Marketplace distribution is based on listings backed by shares (and related provider setup), not per-consumer database replication and role administration. This approach would add unnecessary operational complexity and does not align with Marketplace best practices.