ADA-C01 Question 149
Single answerView, create, and list accountsA global company uses Snowflake Organizations to centrally manage multiple accounts across business units. You are logged in to the organization account as a user with the ORGADMIN role. The finance team asks you to provision a new production account in AWS us-east-1 and to verify which existing accounts already belong to the organization before creating anything. Which action should you take to both review the current accounts and create the new account using supported SQL commands?
- A
Run SHOW ACCOUNTS to review existing organization accounts, then run CREATE ACCOUNT finance_prod ADMIN_NAME = fin_admin ADMIN_PASSWORD = 'StrongPassword' EMAIL = 'fin_admin@example.com' EDITION = BUSINESS_CRITICAL REGION = 'AWS_US_EAST_1';
- B
Run SHOW ORGANIZATION ACCOUNTS to review existing accounts, then run CREATE ACCOUNT finance_prod REGION = 'AWS_US_EAST_1' WAREHOUSE = 'FIN_WH' DATABASE = 'FIN_DB';
- C
Run SHOW ACCOUNTS IN ORGANIZATION to review existing accounts, then run CREATE ACCOUNT finance_prod ADMIN_NAME = fin_admin ADMIN_PASSWORD = 'StrongPassword' EMAIL = 'fin_admin@example.com' REGION = 'AWS_US_EAST_1';
- D
Run DESCRIBE ORGANIZATION to review existing accounts, then run CREATE ACCOUNT finance_prod ADMIN_NAME = fin_admin ADMIN_PASSWORD = 'StrongPassword' EMAIL = 'fin_admin@example.com' CLOUD = 'AWS' REGION = 'us-east-1';
Show answer and explanation
Correct answer: C
Explanation
In Snowflake Organizations, account lifecycle tasks such as viewing and creating accounts are performed from the organization account using the ORGADMIN role. To review existing accounts, the supported command is SHOW ACCOUNTS IN ORGANIZATION. To provision a new account, use CREATE ACCOUNT with required administrative details such as ADMIN_NAME, ADMIN_PASSWORD, EMAIL, and the target REGION. A common misconception is to assume generic account-level SHOW commands or custom object provisioning clauses apply at organization scope; they do not. Another common error is confusing Snowflake's region identifier format with raw cloud provider region names. Best practice is to first list current accounts to avoid naming conflicts or duplicate provisioning, then create the account with the correct organization-level SQL command. This aligns with Snowflake documentation for organization and account management under ORGADMIN.
- A. Incorrect.
Incorrect. SHOW ACCOUNTS is not the command used by ORGADMIN to list accounts in an organization. In Snowflake Organizations, the supported command to list organization accounts is SHOW ACCOUNTS IN ORGANIZATION. The CREATE ACCOUNT syntax shown is otherwise broadly aligned with supported account creation parameters, but the listing command makes the overall answer incorrect.
- B. Incorrect.
Incorrect. SHOW ORGANIZATION ACCOUNTS is not valid Snowflake SQL syntax. In addition, CREATE ACCOUNT does not accept WAREHOUSE or DATABASE parameters to provision default objects during account creation. Those resources are created later inside the new account after administrators connect to it.
- C. Correct.
Correct. For organization-level account management, ORGADMIN can use SHOW ACCOUNTS IN ORGANIZATION to list existing accounts managed under the organization. To create a new account, CREATE ACCOUNT is the supported SQL command, and ADMIN_NAME, ADMIN_PASSWORD, EMAIL, and REGION are valid parameters used when provisioning the account. This matches the real operational workflow: verify existing accounts first, then create the new account in the required region.
- D. Incorrect.
Incorrect. DESCRIBE ORGANIZATION is not used to enumerate accounts, and the command shown for CREATE ACCOUNT uses CLOUD and a raw cloud-region value format that is not the standard account creation syntax expected in Snowflake SQL for this task. Snowflake account creation typically uses the Snowflake region identifier format, such as AWS_US_EAST_1, rather than separately specifying CLOUD and us-east-1 in this context.