ADA-C01 Question 498
Single answerManage listings and listing requestsA Snowflake provider account publishes a private listing that contains a secure share of sales data. Several consumer accounts have submitted listing requests through the listing. The provider's security team requires that access be granted only after each request is reviewed, and they want a process that can be audited later to show who requested access and when the request was approved. Which action should the Snowflake administrator take to meet these requirements?
- A
Configure the listing for automatic fulfillment so approved consumers receive the share immediately, then rely on share usage history for the audit trail.
- B
Review and approve each listing request from the provider account, because listing requests support an approval workflow and preserve request details for later auditing.
- C
Convert the private listing to a public listing, because public listings automatically track request and approval events in Snowsight.
- D
Ask consumers to create reader accounts instead of submitting listing requests, because reader accounts are the only supported way to capture approval history for shared data.
Show answer and explanation
Correct answer: B
Explanation
The best answer is to use the listing request workflow and manually review and approve each request in the provider account. In Snowflake Marketplace/Collaboration scenarios, private listings can be configured to allow consumers to request access, and the provider can then approve or deny those requests. This is the most appropriate option when the business requires pre-approval and an auditable record of request activity. By contrast, automatic fulfillment is designed to streamline delivery and is not appropriate when every request must be reviewed first. Public listings are not suitable for tightly controlled, approval-based access to a private data product. Reader accounts are a different sharing model and do not address the requirement to manage listing requests. This aligns with Snowflake guidance on managing listings and handling listing requests through provider-side workflows in Snowsight.
- A. Incorrect.
Incorrect. Automatic fulfillment does not satisfy the requirement that each request be reviewed before access is granted. While usage and sharing metadata may help with operational visibility, they are not a substitute for a manual request approval workflow tied to listing requests.
- B. Correct.
Correct. For private listings that use listing requests, the provider can review and approve requests before granting access. This approach aligns with a controlled access process and supports auditability because the request lifecycle includes who requested access and the approval action taken.
- C. Incorrect.
Incorrect. Public listings are intended for broad discoverability and are not the right mechanism when the provider wants to manually review each consumer request before granting access. Making the listing public would weaken the intended access control model rather than enforce it.
- D. Incorrect.
Incorrect. Reader accounts are a separate sharing mechanism used for consumers who do not have their own Snowflake account. They are not required for managing listing requests, and they do not replace the listing request approval process for private listings.