ADA-C01 Question 493
Single answerCreate, edit, or delete provider profilesA Snowflake administrator manages an account that shares data with several external consumers using listings. The legal team requires the company to stop exposing one provider identity immediately because the branding information is outdated and no new listings should be associated with it. Existing listings tied to the provider profile are also being retired. Which action should the administrator take to meet this requirement with the least ambiguity and in a supported way?
- A
Delete the provider profile after first removing or retiring any listings that reference it.
- B
Rename the provider profile and leave existing listings attached so consumers can continue to resolve the old provider identity during a transition period.
- C
Revoke IMPORTED PRIVILEGES on the share objects associated with the listings; this automatically deletes the provider profile from the account.
- D
Drop the application package that was used to publish listings; provider profiles are stored inside application packages and are removed when the package is dropped.
Show answer and explanation
Correct answer: A
Explanation
The key administrative concept is that provider profiles are separate account-level objects used to represent a data provider's identity for listings. To delete a provider profile in a supported way, the administrator must first ensure that no active listing depends on it; in practice, that means retiring, removing, or updating dependent listings so the profile is no longer referenced. Editing a provider profile changes its metadata but does not decommission it. Likewise, share privileges and Native App application packages are different Snowflake features and do not control provider profile lifecycle. This aligns with Snowflake documentation and best practices for managing listings and provider profiles in Marketplace/Provider Studio workflows.
- A. Correct.
Correct. Provider profiles are account objects used for marketplace/listing provider identity and branding. If the organization must stop using a provider profile entirely, the supported approach is to delete that provider profile only after removing, retiring, or otherwise disassociating any listings that still depend on it. This avoids dependency conflicts and ensures the profile is no longer available for association with listings.
- B. Incorrect.
Incorrect. Editing or renaming a provider profile does not satisfy the stated requirement to stop exposing that provider identity immediately. Leaving listings attached continues use of that provider profile, even if the display information changes. This option reflects a common misconception that changing metadata is equivalent to decommissioning the provider identity.
- C. Incorrect.
Incorrect. IMPORTED PRIVILEGES applies to database access patterns for shared databases, not to lifecycle management of provider profiles. Revoking privileges on shares does not delete a provider profile. This distractor confuses data sharing access control with marketplace/listing provider identity administration.
- D. Incorrect.
Incorrect. Provider profiles are not stored inside application packages. Dropping an application package is unrelated to deleting a provider profile used for listings. This option mixes Native Apps concepts with marketplace provider profile management.