ADA-C01 Question 10
Single answerAnalyze the impact of organizational-level changes on account-level objectsA global enterprise uses an organization with several Snowflake accounts for development, testing, and production. The organization administrator plans to rename one existing account to align with a new corporate naming standard. Several application teams are concerned about possible downstream impact on their account-level objects and integrations. Which statement best describes the effect of this organizational-level change?
- A
Renaming the account changes only the account identifier shown at the organization level; existing databases, schemas, roles, warehouses, and users inside the account are not renamed automatically.
- B
Renaming the account automatically updates all fully qualified object names in SQL, including database, schema, and object references stored in views and procedures.
- C
Renaming the account causes all shares, replication/failover configurations, and data listings associated with the account to be dropped and recreated manually.
- D
Renaming the account automatically changes the names of all account-level objects that include the old account name as part of their object name.
Show answer and explanation
Correct answer: A
Explanation
This question tests the candidate's ability to distinguish organization-level administration from account-level object management. In Snowflake, changing an account name at the organization level does not automatically rename internal account objects such as databases, schemas, roles, warehouses, or users. The practical impact is primarily on references to the account itself, especially in cross-account access patterns, integrations, client connection settings, or operational documentation. Best practice is to perform an impact assessment for anything that references the account name externally, while understanding that contained objects remain unchanged unless explicitly altered. This aligns with Snowflake administration guidance that organization-level actions manage accounts as entities, whereas object names and definitions within an account are controlled independently through account-level DDL and administration.
- A. Correct.
Correct. An account rename is an organization-level administrative change that affects the account's identity and related references such as account locator-based identification or organization/account naming conventions, but it does not automatically rename objects contained within the account. Account-level objects such as databases, schemas, tables, roles, warehouses, and users retain their existing names unless explicitly altered. This is the key distinction between changing an account's organizational metadata and modifying object definitions inside the account.
- B. Incorrect.
Incorrect. Fully qualified SQL object names are based on database, schema, and object names, not on the account name in a way that Snowflake rewrites automatically across code artifacts. Renaming an account does not trigger mass updates to stored SQL text in views, procedures, tasks, or application code. A common misconception is to assume Snowflake propagates name changes throughout dependent code, but administrators must still assess external references and integrations separately.
- C. Incorrect.
Incorrect. Renaming an account does not inherently drop shares, replication groups, failover groups, or listings. However, administrators should validate any integration or configuration that references the account by organization/account name or locator because some external or cross-account references may need to be updated. The misconception here is confusing a metadata rename with destructive reconfiguration.
- D. Incorrect.
Incorrect. Snowflake does not inspect object names and rewrite them just because they happen to contain the old account name as part of a string. If a warehouse, database, role, or other object was manually named using the old naming convention, it keeps that name until an administrator explicitly renames it. This option reflects a common but incorrect assumption that organizational naming changes cascade into object names automatically.