ADA-C01 Question 147
Single answerPerform account tasksA Snowflake organization uses separate production and development accounts. After a security review, the lead administrator must rotate the account-level credentials used by an external integration that connects to the development account. The administrator also needs to verify that the development account can be clearly identified in organization-level reporting to avoid future mistakes when performing account-level administration. Which action best meets these requirements with the least disruption?
- A
Use SYSTEM$GENERATE_SCIM_ACCESS_TOKEN in the development account to create a new token for the integration, and update the account locator so it is easier to identify in reports.
- B
Use ALTER ACCOUNT to set a clearer account name for the development account in the organization, and use SYSTEM$GENERATE_MASTER_TOKEN to rotate the account-level access token used by the integration.
- C
Drop and recreate the development account with a more descriptive account identifier, then re-create the integration so a fresh account token is generated automatically.
- D
Rename the current region and cloud platform label for the development account, and use ALTER USER to rotate the credentials used by the external integration.
Show answer and explanation
Correct answer: B
Explanation
This question tests practical account administration tasks: updating account metadata for operational clarity and rotating account-level credentials with minimal disruption. In Snowflake, account properties can be adjusted with ALTER ACCOUNT, which is appropriate when administrators need a clearer account name for management and reporting. For rotating an account-level token, SYSTEM$GENERATE_MASTER_TOKEN is the relevant function. By contrast, SCIM tokens are specifically for SCIM integrations, user-level changes do not solve account-level credential requirements, and recreating accounts is not a best practice for routine administrative updates. These behaviors align with Snowflake documentation on account management, token generation, and administrative SQL functions.
- A. Incorrect.
Incorrect. SYSTEM$GENERATE_SCIM_ACCESS_TOKEN is used for SCIM provisioning integrations, not for rotating a general account-level master token used for account access or account administration scenarios. Also, the account locator is a system-generated identifier and is not something administrators rename for readability in organization reporting.
- B. Correct.
Correct. ALTER ACCOUNT can be used to modify account properties such as the account name, which helps administrators distinguish accounts in organization-level views and operational processes. SYSTEM$GENERATE_MASTER_TOKEN is the appropriate function for generating a new account-level master token when rotating credentials used for account-level access patterns. This approach avoids recreating the account and minimizes disruption.
- C. Incorrect.
Incorrect. Recreating an account is highly disruptive, unnecessary for simple account metadata updates or token rotation, and would introduce significant operational risk. Account identifiers and account lifecycle operations are not handled this way for routine account administration tasks.
- D. Incorrect.
Incorrect. Administrators cannot rename the region or cloud platform associated with an account; those are deployment characteristics of the Snowflake account. ALTER USER applies to user objects, but the scenario is about account-level credentials used by an external integration, not an individual Snowflake user password or key.