ADA-C01 Question 501
Single answerManage Native AppsA Snowflake administrator manages a consumer account where a Native App from Snowflake Marketplace has already been installed and is used by several analyst roles. The security team now requires the administrator to verify what privileges and objects the app has access to before approving an upgrade to a newer app version. Which action should the administrator take to review the app's granted permissions and references in a way that aligns with Native App management best practices?
- A
Use SHOW APPLICATIONS and DESCRIBE APPLICATION on the installed app to review its metadata, including granted references and version details before upgrading.
- B
Query ACCOUNT_USAGE.GRANTS_TO_ROLES for the app name, because Native Apps are managed only as role grants and do not expose application-level metadata.
- C
Clone the application package into a separate database and inspect its setup script there, because installed Native Apps can only be reviewed by cloning the package.
- D
Use SHOW DATABASES to locate the app objects, because Native Apps are exposed only as standard databases and their permissions are reviewed the same way as shared databases.
Show answer and explanation
Correct answer: A
Explanation
For Native Apps, Snowflake distinguishes between provider-side objects such as the APPLICATION PACKAGE and consumer-side installed APPLICATION objects. In a consumer account, administrators should use Native App management commands to inspect the installed app rather than treating it only as a database or only as a collection of grants. SHOW APPLICATIONS helps identify installed apps, and DESCRIBE APPLICATION is the key command for reviewing installed application details before operational actions such as upgrades. This aligns with Snowflake Native App Framework administration practices, where app lifecycle tasks like inspecting versions, references, and configuration are handled through application-level metadata rather than package cloning or generic database inspection.
- A. Correct.
Correct. In the consumer account, an installed Native App is managed as an application object. SHOW APPLICATIONS lists installed apps, and DESCRIBE APPLICATION provides key metadata about the installed app, such as version-related information and details needed to assess configuration, including references and privileges the application requires or uses. This is the appropriate administrative path before approving an upgrade.
- B. Incorrect.
Incorrect. Although grant-related views can help analyze some access patterns in Snowflake generally, a Native App is not administered only through standard role-grant inspection. Relying solely on ACCOUNT_USAGE.GRANTS_TO_ROLES misses application-specific metadata and does not provide the focused visibility administrators need for Native App review and upgrade readiness.
- C. Incorrect.
Incorrect. Consumers do not manage installed Native Apps by cloning the provider's application package. Application packages are provider-side objects used to build and publish apps, not consumer-side objects used for normal review of installed apps. This option confuses provider development workflow with consumer administration.
- D. Incorrect.
Incorrect. Native Apps are not reviewed solely as standard databases. While an app may create or expose objects internally, the installed unit is an application object with its own management commands. Using SHOW DATABASES would not provide the complete, app-specific permission and reference information needed for upgrade review.