ADA-C01 Question 487
Select 2Access the public and internal MarketplaceA Snowflake account is used by both a central data platform team and several business units. The platform team has created a private data listing that should be discoverable only by users inside the organization through the internal Marketplace. At the same time, analysts in one business unit need to browse and request third-party datasets from the public Snowflake Marketplace. A security administrator wants to grant only the minimum required access so these users can open the Marketplace and work with listings appropriate to their role. Which roles should be granted? Select TWO.
- A
Grant the IMPORT SHARE privilege to the analysts' role so they can browse public Marketplace listings and request datasets
- B
Grant the global CREATE DATA EXCHANGE LISTING privilege to the platform team's role so they can create listings for the internal Marketplace
- C
Grant the SNOWFLAKE.MARKETPLACE_CONSUMER database role to the analysts' role so they can access the Marketplace as consumers
- D
Grant the SNOWFLAKE.MARKETPLACE_PROVIDER database role to the platform team's role so they can manage provider capabilities for listings
- E
Grant OWNERSHIP on the shared database to both roles so they can see all Marketplace listings
Show answer and explanation
Correct answers: C, D
Explanation
To access the Snowflake Marketplace with least privilege, administrators should use the Snowflake-provided database roles for Marketplace personas. Consumer users who need to browse or request listings should receive SNOWFLAKE.MARKETPLACE_CONSUMER. Users responsible for publishing/managing listings should receive SNOWFLAKE.MARKETPLACE_PROVIDER. This scenario distinguishes Marketplace access from older share-based access control and from data exchanges, which use different privileges and workflows. In Snowflake documentation, Marketplace access and listing administration are tied to Snowflake database roles and provider/consumer capabilities, while IMPORT SHARE is for consuming direct shares after access has already been granted. Following least-privilege best practice, avoid broad grants such as OWNERSHIP when a scoped Marketplace role satisfies the requirement.
- A. Incorrect.
Incorrect. IMPORT SHARE is used to create databases from shares that have already been granted to the account. It does not provide Marketplace browsing capability. A common misconception is to treat Marketplace access like classic data sharing, but Marketplace discovery and provider/consumer workflows are controlled through Snowflake database roles and listing-related privileges rather than IMPORT SHARE alone.
- B. Incorrect.
Incorrect. CREATE DATA EXCHANGE LISTING applies to data exchanges, which are a different collaboration mechanism from the Snowflake Marketplace/internal Marketplace listing model described here. For internal Marketplace/provider access, the relevant enablement is through Marketplace provider capabilities, not the data exchange listing privilege. This distractor targets confusion between private exchanges and Marketplace listings.
- C. Correct.
Correct. The SNOWFLAKE.MARKETPLACE_CONSUMER database role is intended for users who need to access and use Marketplace consumer functionality, including browsing/requesting listings as allowed. Granting this role aligns with least privilege for analysts who only need to consume public Marketplace data rather than administer provider settings.
- D. Correct.
Correct. The SNOWFLAKE.MARKETPLACE_PROVIDER database role is used for provider-side Marketplace capabilities, including managing listings. This is appropriate for the platform team responsible for making the internal listing available within the organization. It grants provider functionality without broadly elevating unrelated privileges.
- E. Incorrect.
Incorrect. OWNERSHIP on a shared database is excessive and unrelated to simply accessing Marketplace listings. Marketplace visibility and listing management are not enabled by database ownership. This option reflects an over-privileging mistake that violates least-privilege best practice.