ADA-C01 Question 9
Single answerAnalyze the impact of organizational-level changes on account-level objectsAn enterprise uses Snowflake Organizations to centrally manage several production and non-production accounts. The organization administrator is asked to rename one of the production accounts to align with a new naming standard. A Snowflake administrator in that account is concerned about possible impact on existing account-level objects and integrations. Which statement best describes the expected impact of this organizational-level change?
- A
Renaming the account changes the account locator, so database replication and failover groups referencing the source account must be recreated.
- B
Renaming the account updates the account name shown in the organization, but account-level objects such as databases, warehouses, roles, users, and grants remain unchanged; however, any external processes that reference the account identifier in connection settings may need to be updated depending on what identifier they use.
- C
Renaming the account automatically renames all account-level objects that include the old account name as a naming prefix, including warehouses, databases, and resource monitors.
- D
Renaming the account invalidates all existing network policies and security integrations because they are bound to the original organization-level account name.
Show answer and explanation
Correct answer: B
Explanation
In Snowflake Organizations, certain actions such as renaming an account are performed at the organization level, but they do not automatically modify account-level objects inside that account. A key distinction is between the account name and the account locator: the locator is a stable identifier, while the account name is an administratively managed name that may appear in organization views and some connection contexts. As a result, renaming an account generally does not affect internal objects like databases, schemas, warehouses, users, roles, grants, resource monitors, network policies, or integrations. The main operational concern is external dependency review: connection strings, partner tools, IdP settings, private connectivity documentation, scripts, and automation may rely on account identifiers or URLs. Snowflake documentation on organization and account administration, as well as account identifiers and connection URLs, supports this distinction and the best practice of validating external integrations after organization-level account changes.
- A. Incorrect.
Incorrect. An account rename does not change the account locator. The locator is the stable identifier used in many Snowflake URLs and cross-account operations. Because the locator does not change, replication and failover configurations are not recreated solely due to an account rename. This option reflects a common misconception that the display/account name and locator are the same thing.
- B. Correct.
Correct. An organization-level account rename affects the account's name within the organization, but it does not automatically alter account-level objects such as databases, warehouses, roles, users, grants, resource monitors, or policies. The practical risk is with clients, scripts, SSO configurations, or integration code that may reference an account name or account URL format that includes the old account name rather than a stable locator-based identifier. Administrators should validate connection strings and dependent tooling after the rename.
- C. Incorrect.
Incorrect. Snowflake does not cascade account renames into object renames. Object names are independent metadata objects within the account. If an organization used naming conventions that embedded the old account name in object names, those objects would keep their current names unless explicitly renamed by administrators.
- D. Incorrect.
Incorrect. Network policies and security integrations are not invalidated simply because the account name was changed at the organization level. These account-level objects remain in place. Some external identity provider or client-side configurations might require review if they explicitly reference an old account URL or identifier, but the Snowflake objects themselves are not automatically invalidated.