ADA-C01 Question 205
Single answerIdentify when a given account identifier needs to be usedA Snowflake administrator is documenting how different teams should reference the company's production account after a recent organization rename. The account currently has users connecting through Snowsight, a partner application configured with OAuth redirect URIs, and a separate business unit that needs to create a cross-account share to this account from another Snowflake account in the same organization. Which identifier should the administrator tell each team to use so the integrations continue to work correctly?
- A
Tell all teams to use the account name only, because Snowflake resolves the current organization automatically for all account-level operations.
- B
Tell the Snowsight users and the OAuth-integrated application to use the account locator, and tell the data sharing team to use the account URL.
- C
Tell the Snowsight users and OAuth-integrated application to use the organization-account name in the account URL, and tell the data sharing team to use the locator-based account identifier where Snowflake requires an account identifier.
- D
Tell the Snowsight users to use the region name, the OAuth-integrated application to use the account name, and the data sharing team to use the organization name.
Show answer and explanation
Correct answer: C
Explanation
Snowflake uses different account identifiers depending on the task. For user access and web-based integrations, administrators generally use the account URL, which is typically built from the organization name and account name (for example, in Snowsight and OAuth-related endpoint/redirect configurations). For some cross-account features, such as data sharing or commands that explicitly require an account identifier, Snowflake may require the account locator-based identifier rather than the friendly account name. This is why administrators must distinguish between the organization-account name used in URLs and the account locator used where Snowflake documentation specifically calls for an account identifier. Best practice is to check the identifier format required by the specific feature: account URL for login/browser integrations, and locator/account identifier format for account-to-account references where documented.
- A. Incorrect.
Incorrect. The account name by itself is not sufficient for all scenarios. User-facing access typically uses the account URL, which in modern Snowflake deployments is based on the organization name and account name. In addition, some cross-account and programmatic operations require a specific account identifier format rather than just the account name alone.
- B. Incorrect.
Incorrect. This reverses the common usage. End users and browser-based tools such as Snowsight typically access the account through its account URL, not the raw locator. OAuth redirect URIs also must match the actual account URL being used. By contrast, certain Snowflake features and SQL commands that reference another account can require the locator-style account identifier.
- C. Correct.
Correct. Snowsight access and OAuth redirect URIs depend on the account URL, which is commonly expressed using the organization name and account name. For account-to-account operations such as sharing or other features that explicitly ask for an account identifier, Snowflake may require the locator-based form (sometimes with region/cloud context depending on the account and feature). This distinction is important after an organization rename or when validating which identifier a specific integration expects.
- D. Incorrect.
Incorrect. None of these identifiers are appropriate as stated. A region name alone does not identify a Snowflake account for user login, an account name alone is often not enough for OAuth endpoint and URL configuration, and an organization name alone does not identify the target account for data sharing or cross-account operations.