ADA-C01 Question 201
Single answer2.3 Given a scenario, manage account identifiers.A company has separate Snowflake accounts for development, test, and production. The security team is standardizing all automation scripts and private connectivity configurations so they continue to work even if an account is renamed. An administrator must identify which account identifier should be used in URLs and connection definitions when a stable, system-generated identifier is required across the organization. Which identifier should the administrator use?
- A
The account name defined by the organization, because it is unique and intended for long-term use in all endpoints
- B
The locator, because it is the system-assigned account identifier used as the basis for account URLs and remains stable even if the account name changes
- C
The username of the ACCOUNTADMIN role holder, because account URLs are resolved through the primary administrative user
- D
The region name, because Snowflake combines the region with the organization name to create a stable account-specific endpoint
Show answer and explanation
Correct answer: B
Explanation
Snowflake account identifiers can be represented in different ways, including organization-account names and account locators. For operational scenarios where a stable, system-generated identifier is required, such as certain connection definitions or endpoint-related configurations that must continue to work after an account rename, the account locator is the appropriate identifier. By contrast, account names are more human-friendly and can change. Region information is only one component of account location and is not a unique account identifier. This question tests the practical distinction between friendly naming and durable account identity, which is important when managing account identifiers in enterprise automation and connectivity scenarios.
- A. Incorrect.
Incorrect. The account name is human-readable and commonly used with the organization name in modern Snowflake identifiers, but it is not the best choice when the requirement is a stable, system-generated identifier that is not affected by account renaming. This option reflects the misconception that friendly account names are immutable infrastructure identifiers.
- B. Correct.
Correct. The account locator is a system-assigned identifier for the Snowflake account and is used as the basis for account URLs. It is the right choice when scripts, integrations, or private connectivity configurations need a stable identifier that persists even if the account name is changed. This aligns with Snowflake guidance for scenarios where the administrator must rely on a durable account identifier rather than a display-oriented name.
- C. Incorrect.
Incorrect. Usernames and roles are used for authentication and authorization, not for identifying the Snowflake account in URLs or connection endpoints. This distractor targets a common misunderstanding between account-level identifiers and administrative access within the account.
- D. Incorrect.
Incorrect. The region helps determine where the account is hosted, but it does not uniquely identify an account by itself. Multiple accounts can exist in the same region, so region information alone cannot serve as the required stable account identifier for endpoints or connection definitions.