ADA-C01 Question 497
Single answerManage listings and listing requestsA Snowflake provider account publishes a private data product as a listing and wants to tightly control which consumer accounts can access it. The provider's governance team also wants a workflow in which consumers can request access before the listing is shared with them. Which approach should the Snowflake administrator take to meet these requirements with the least operational overhead?
- A
Create a public listing and require consumers to submit a support ticket outside Snowflake before using it.
- B
Create a private listing targeted to specific consumer accounts and enable listing requests so consumers can request access through Snowflake.
- C
Share the underlying database directly with all potential consumers, then use reader accounts to restrict access after they connect.
- D
Create a private listing without specifying target consumers, because private listings are automatically discoverable to all accounts in the same region and can be approved later.
Show answer and explanation
Correct answer: B
Explanation
The best answer is to use a private listing and the built-in listing request workflow. In Snowflake, listings are the governed mechanism for sharing data products, and private listings are designed for limited distribution to specific consumers instead of open marketplace-style discovery. Listing requests help providers manage inbound access requests in Snowflake rather than relying on external ticketing or ad hoc processes. This approach reduces administrative friction while preserving governance and selective sharing. By contrast, public listings are intended for wider visibility, and direct shares bypass the listing-based workflow the scenario specifically requires. This aligns with Snowflake best practices for managing controlled data distribution through listings and handling consumer access requests within the platform.
- A. Incorrect.
Incorrect. A public listing is broadly discoverable in the marketplace context and is not the right mechanism when the provider wants to limit visibility and access to selected consumer accounts. Requiring an external support ticket also increases operational overhead rather than using Snowflake's built-in request workflow.
- B. Correct.
Correct. A private listing is intended for controlled sharing with specific consumers rather than general marketplace discovery. Using listing requests supports an in-platform access request workflow, allowing consumers to request access and providers to manage approvals with less manual coordination. This best aligns with the requirement for controlled access and lower operational overhead.
- C. Incorrect.
Incorrect. A direct share can provide secure access, but it does not satisfy the requirement to manage access through listings and listing requests. In addition, reader accounts are typically used for consumers that do not have their own Snowflake account, not as a post-connection restriction mechanism for broadly shared databases.
- D. Incorrect.
Incorrect. Private listings are not automatically discoverable to all accounts in a region. They are intended for selected consumers. Omitting the target consumers would not meet the requirement for controlled access, and this option reflects a misunderstanding of how private listing visibility works.