ADA-C01 Question 495
Single answerCreate, submit, manage, and modify a data listingA data provider has created a Snowflake Marketplace listing for a shared weather dataset and already submitted it for review. Before the listing is approved, the product team discovers that a column containing sensitive internal notes was accidentally included in the shared data. The provider must prevent consumers from seeing that column and still move forward with publishing the listing as quickly as possible. What should the administrator do?
- A
Modify the secure view or shared dataset to remove the sensitive column, update the listing to use the corrected shared data, and resubmit if the listing status requires it
- B
Delete the listing permanently and create a new listing, because submitted listings cannot be changed before approval
- C
Edit only the listing description to warn consumers not to query the sensitive column, since the listing content itself cannot be changed after submission
- D
Revoke IMPORTED PRIVILEGES from consumers, because that removes access to sensitive columns in an existing listing
Show answer and explanation
Correct answer: A
Explanation
This question tests the candidate's ability to manage and modify a data listing in a realistic prepublication scenario. In Snowflake Marketplace and listings generally, the listing is a presentation and distribution layer for underlying shared data objects. If data needs to be corrected, the administrator should update the shared objects themselves, often using secure views to enforce the intended schema and hide sensitive columns. After that, the administrator updates the listing and follows the submission or resubmission process as required by the listing's current state. Best practice is to expose curated data products through secure views rather than raw base tables when there is any risk of exposing columns that should not be shared. This aligns with Snowflake documentation on provider listings, data sharing, and secure views for governing exposed data.
- A. Correct.
Correct. In Snowflake, a listing references underlying shared data such as tables or secure views. If sensitive data was exposed, the right action is to correct the underlying shared object, commonly by replacing direct table exposure with a secure view or by altering the view so the sensitive column is no longer available. The provider can then update the listing as needed and resubmit depending on its review state. This is the practical and least disruptive way to manage and modify a listing before publication.
- B. Incorrect.
Incorrect. Re-creating the listing is not generally required just because a submitted listing needs correction. Snowflake supports managing and modifying listings, and the proper administrative response is to fix the shared data and update the listing workflow rather than starting over unless there is a specific operational reason to do so.
- C. Incorrect.
Incorrect. Changing descriptive text does not remove access to data that is actually present in the shared dataset. This option reflects a dangerous misconception that metadata or legal text can substitute for technical access controls. For sensitive data exposure, the administrator must change the underlying shared objects.
- D. Incorrect.
Incorrect. IMPORTED PRIVILEGES is used by consumers to access privileges on shared databases after a share is consumed; it is not a mechanism providers use to hide individual columns inside a listing. Column-level exposure must be controlled in the data product itself, typically through secure views, object design, or by changing the shared content.