ADA-C01 Question 141
Single answerCreate and name an organizationA global company is centralizing administration of several Snowflake accounts that were created over time by different business units. The lead platform engineer wants to create an organization so the company can manage account relationships under a single organizational structure and use a naming standard that will remain valid as the company expands to additional regions. The engineer is using an account that has the privileges required to create an organization. Which action should the engineer take to correctly create and name the organization?
- A
Create the organization with a globally unique organization name that follows Snowflake naming rules, understanding that the organization name becomes part of generated identifiers and should be chosen carefully because it represents the company across accounts.
- B
Create the organization using any internal display label, because Snowflake automatically converts it into a hidden immutable organization ID and the visible name can later be changed without impact.
- C
Create the organization with the same name as an existing account locator, because organization names only need to be unique within the current region.
- D
Create the organization from any ACCOUNTADMIN role in any account, because organization creation is an account-level operation and does not require organization-specific administrative access.
Show answer and explanation
Correct answer: A
Explanation
The key concept is that an organization is a higher-level administrative construct in Snowflake, and its name is an important identifier that should be chosen deliberately. Best practice is to use a globally appropriate, durable name that aligns with enterprise naming standards and Snowflake naming rules. Candidates should distinguish organization-level concepts from account-level concepts such as account locators and ACCOUNTADMIN scope. Snowflake documentation on organizations explains that organizations sit above accounts and that naming should be planned carefully because the organization identifier is foundational to how the organization is represented.
- A. Correct.
Correct. When creating an organization, the organization name must follow Snowflake's naming requirements and should be selected carefully because it is used as part of the organization's identity. In practice, organizations are intended to represent the company or tenant at a higher level than an individual account, so a durable, globally appropriate naming convention is important.
- B. Incorrect.
Incorrect. This reflects a common misconception that the organization name is merely a friendly label. In Snowflake, the organization name is a real administrative identifier, not just a cosmetic display value that can be freely changed later without consequence. Treating it as a temporary label can lead to poor long-term naming decisions.
- C. Incorrect.
Incorrect. Organization names are not scoped like ordinary internal labels for a single region or a single account. Reusing an account locator as the organization name is not the correct rule, and the assumption that uniqueness is only regional is misleading. The engineer should choose a valid organization name based on Snowflake's organization naming requirements, not on an account locator.
- D. Incorrect.
Incorrect. This confuses account-level administration with organization-level administration. While ACCOUNTADMIN is powerful within an account, creating an organization is not something that any arbitrary account administrator can do from any account. The action requires the appropriate authority for organization creation, which is distinct from ordinary account administration.