ADA-C01 Question 142
Single answerCreate and name an organizationA global company is consolidating several Snowflake accounts under a single administrative boundary so it can centrally manage account names and support features that rely on organization-level identity. The lead administrator has ACCOUNTADMIN on one existing account and wants to create the organization with a name that will remain valid and usable for future account identifiers. Which action should the administrator take?
- A
Use the ACCOUNTADMIN role in any Snowflake account and run CREATE ORGANIZATION with a mixed-case name such as Global-Data-Corp.
- B
Contact Snowflake Support and request creation of an organization whose name contains only lowercase letters and no underscores or periods, for example globaldatacorp.
- C
Use the ORGADMIN role in the current account and run CREATE ORGANIZATION globaldatacorp; then rename it later if needed.
- D
Create a new account locator first, then assign that locator as the organization name because organization names must match an existing account identifier.
Show answer and explanation
Correct answer: B
Explanation
To create a Snowflake organization, customers generally work with Snowflake rather than issuing a SQL command from an existing account. A key applied skill for administrators is knowing that organization creation is an organizational provisioning activity and that the organization name must be chosen carefully because it becomes part of organization-scoped account identification. Best practice is to select a simple, globally unique, lowercase alphanumeric name that will scale well across future accounts. Snowflake documentation for organizations and account identifiers emphasizes the distinction between organization-level administration and account-level roles, as well as naming constraints for organization and account identifiers.
- A. Incorrect.
Incorrect. An organization is not created by a customer-issued SQL command from an account using ACCOUNTADMIN. In practice, organization creation is handled through Snowflake, and the naming rules are stricter than this option suggests. A name like Global-Data-Corp includes uppercase letters and hyphens, which do not align with Snowflake organization naming requirements used in organization and account identifiers.
- B. Correct.
Correct. Creating an organization is typically done by working with Snowflake Support (or through Snowflake-led provisioning processes), not by issuing a CREATE ORGANIZATION command from an account. The organization name must be globally unique and follow identifier rules appropriate for organization and account naming. A lowercase alphanumeric name such as globaldatacorp aligns with the expected format and avoids characters that are not allowed for organization names.
- C. Incorrect.
Incorrect. ORGADMIN is used after an organization exists to perform organization-level administration; it is not how a new organization is initially created. Also, customers do not create organizations with a SQL CREATE ORGANIZATION statement in their account. The assumption that the name can simply be changed later is risky and misleading because organization naming is part of a foundational identifier strategy and should be planned carefully at creation time.
- D. Incorrect.
Incorrect. Account locators and organization names are different concepts. An account locator is a system-generated account identifier, while the organization name is part of the organization/account naming model used for account identifiers. You do not create an account locator first and then reuse it as the organization name.