ADA-C01 Question 152
Single answerChange account namesA global company wants to standardize naming across its Snowflake deployment after a rebranding effort. The primary account currently has an account name that no longer matches corporate standards, and administrators are concerned about downtime and broken connectivity for users and applications. Which statement best describes what an administrator should expect when changing the Snowflake account name?
- A
The account name can be changed, but administrators must also plan for updates to URLs and connection settings that reference the account identifier or account name.
- B
The account name cannot be changed after account creation; the only supported approach is to create a new account and migrate all objects and users.
- C
Changing the account name automatically updates all client connection strings, bookmarks, and third-party integrations, so no application changes are required.
- D
Changing the account name also changes the organization name, so administrators should validate both names with Snowflake Support before proceeding.
Show answer and explanation
Correct answer: A
Explanation
In Snowflake, an account name can be changed, but administrators should treat this as a change-management exercise rather than a simple cosmetic update. The main risk is impact on connectivity: web UI URLs, JDBC/ODBC connection properties, scripts, automation, SSO integrations, and external tools may depend on the current account name or account URL format. Snowflake documentation distinguishes the account name from the organization name, and administrators should not assume they are changed together. Best practice is to inventory all connection points, validate how clients reference the account, communicate the change window, and test critical integrations before and after the rename.
- A. Correct.
Correct. Snowflake supports changing an account name, but administrators must evaluate downstream impact. Any URLs, bookmarks, scripts, drivers, SSO settings, private connectivity configurations, or third-party tools that explicitly reference the account name or account locator-based connection details may need review and updates. The key operational concern is not the metadata change itself, but dependencies on account-specific identifiers in connection endpoints and integrations.
- B. Incorrect.
Incorrect. This is a common misconception because many platform identifiers are immutable, but Snowflake does allow account names to be changed. Re-creating the account and migrating workloads would be unnecessary and operationally risky when the requirement is only to rename the account.
- C. Incorrect.
Incorrect. Snowflake does not automatically update customer-managed connection strings, saved bookmarks, partner integrations, or application configuration values outside the platform. Administrators must inventory and validate these dependencies as part of change planning.
- D. Incorrect.
Incorrect. The account name and organization name are distinct concepts in Snowflake. Renaming an account does not imply that the organization name changes. Confusing these two identifiers can lead to incorrect assumptions about account URLs and governance scope.