ADA-C01 Question 494
Select 3Create, edit, or delete provider profilesA Snowflake administrator is preparing a clean room collaboration for several external consumers. The business wants to expose only a specific set of shareable objects and approved templates under a named identity that can later be referenced by listings and collaborations. The administrator also needs to retire an outdated identity that is no longer used anywhere. Which TWO actions should the administrator take to correctly manage provider profiles?
- A
Create or update the provider profile so it contains the required metadata and approved objects/templates, then associate that provider profile with the clean room publishing workflow.
- B
Drop the outdated provider profile immediately, even if it is still referenced by an active listing or collaboration, because Snowflake automatically rebinds those references.
- C
Before deleting the outdated provider profile, verify that it is no longer referenced by dependent objects such as active listings or collaborations, and remove or update those dependencies first.
- D
Edit the provider profile directly to grant additional consumer account privileges, because provider profiles control account-level access enforcement.
- E
Use the provider profile as the reusable publisher identity for clean room sharing configurations, and modify it when the provider’s approved assets or descriptive metadata changes.
Show answer and explanation
Correct answers: A, C, E
Explanation
This question tests practical administration of provider profiles in Snowflake clean room and sharing workflows. The key applied concepts are: (1) provider profiles are created and edited to represent the provider and define approved content/configuration used in publishing workflows, and (2) provider profiles should not be deleted until any dependent references have been removed or updated. Administrators should distinguish provider-profile management from privilege management; provider profiles are not substitutes for grants, roles, or account-level access controls. Snowflake documentation on clean rooms/provider configuration and general object dependency best practices supports creating or modifying profiles for publishing needs and carefully validating dependencies before deletion.
- A. Correct.
Correct. A provider profile is used as the provider-side identity/configuration for publishing clean room assets. In practice, administrators create or edit the provider profile to define the provider metadata and the assets/templates that should be exposed through the collaboration workflow. This reflects the intended use of provider profiles in managing how the provider is represented and what approved content is available.
- B. Incorrect.
Incorrect. Snowflake does not automatically and safely rebind dependent references when an in-use provider profile is deleted. If the outdated profile is still referenced by a listing, collaboration, or related publishing configuration, the administrator must first address those dependencies. Assuming automatic rebinding is a common but dangerous misconception.
- C. Correct.
Correct. Deleting a provider profile should be treated like deleting any referenced configuration object: the administrator must first confirm it is no longer in use and then update or remove dependent objects. This is the operationally safe approach and aligns with standard Snowflake administration practices for dependent object management.
- D. Incorrect.
Incorrect. Provider profiles are not the mechanism for granting account-level privileges to consumers. Access enforcement is handled through Snowflake roles, grants, shares, listings, and clean room collaboration controls. Confusing descriptive/provider configuration with privilege management is a common misunderstanding.
- E. Correct.
Correct. Provider profiles serve as a reusable provider identity/configuration in clean room publishing scenarios. If the provider’s branding, descriptive information, or approved assets change, the correct action is to edit the profile rather than recreate unrelated security objects or attempt to manage privileges through the profile.