ADA-C01 Question 150
Single answerView, create, and list accountsA global company uses Snowflake Organizations to centrally manage multiple accounts. An administrator with the ORGADMIN role has been asked to provision a new production account in AWS for the us-east-1 region and then verify that the account appears in the organization's inventory. Which action should the administrator take to both create the account correctly and confirm it is registered at the organization level?
- A
Use the ORGADMIN role to execute CREATE ACCOUNT with the required edition, admin user, and region/cloud parameters, then run SHOW ACCOUNTS to verify the new account is listed.
- B
Use the ACCOUNTADMIN role in any existing account to execute CREATE ACCOUNT, then run SHOW ORGANIZATION ACCOUNTS to verify the new account.
- C
Use the SECURITYADMIN role to execute CREATE MANAGED ACCOUNT in the source account, then run SHOW ACCOUNTS in that account to verify the new production account.
- D
Use the SYSADMIN role to clone an existing account into us-east-1, then run SHOW ACCOUNTS in the cloned account to verify organization registration.
Show answer and explanation
Correct answer: A
Explanation
In Snowflake Organizations, creating and viewing accounts is an organization-level administrative function. The ORGADMIN role is used for tasks such as creating accounts with CREATE ACCOUNT and listing them with SHOW ACCOUNTS. This differs from account-level roles like ACCOUNTADMIN, SYSADMIN, and SECURITYADMIN, which manage objects and security within a specific account but do not provision new organization accounts. A common misconception is to confuse standard organization account creation with managed accounts or reader-account-related features; those are separate capabilities with different commands and use cases. Snowflake documentation for Organizations and organization-level administration identifies ORGADMIN as the appropriate role for creating and listing accounts.
- A. Correct.
Correct. Creating a new Snowflake account in an organization is an organization-level task performed by ORGADMIN, not by account-level administrative roles such as ACCOUNTADMIN. After creating the account with CREATE ACCOUNT and specifying appropriate properties such as cloud platform and region, the administrator can use SHOW ACCOUNTS to list accounts in the organization and confirm that the new account has been registered.
- B. Incorrect.
Incorrect. ACCOUNTADMIN is powerful within a single Snowflake account, but it does not have organization-level authority to create new accounts in the organization. Also, SHOW ORGANIZATION ACCOUNTS is not the standard command used for this purpose; ORGADMIN uses organization-level commands such as SHOW ACCOUNTS.
- C. Incorrect.
Incorrect. CREATE MANAGED ACCOUNT is associated with provider scenarios such as listings/reader or managed account use cases, not standard organization account provisioning for an internal production account. SECURITYADMIN also does not have the organization-level privilege required to create a regular organization account.
- D. Incorrect.
Incorrect. Snowflake does not support cloning an entire account in the way described. SYSADMIN is an account-level role and cannot create a new organization account. SHOW ACCOUNTS is also run from an account with organization-level authority, not from a newly 'cloned' account.