ADA-C01 Question 139
Single answerPerform organizational tasksA global company uses Snowflake Organizations to manage several accounts across AWS and Azure. The security team wants to review all accounts in the organization, identify which accounts are enabled for replication or failover, and retrieve this information from a single place without logging in to each account individually. An administrator has ORGADMIN privileges in the organization account. Which approach should the administrator use to meet this requirement most effectively?
- A
Query organization-level views in ORGANIZATION_USAGE from the organization account to inspect account metadata and replication-related information across accounts.
- B
Log in to each account as ACCOUNTADMIN and query ACCOUNT_USAGE views, then consolidate the results manually in a spreadsheet.
- C
Use the SHOW REPLICATION ACCOUNTS command from any member account because replication metadata is automatically visible organization-wide.
- D
Grant SECURITYADMIN in each account to ORGADMIN and then use DATABASE_USAGE views to retrieve organization-wide replication status.
Show answer and explanation
Correct answer: A
Explanation
For organization-level administrative tasks, Snowflake provides an organization account and the ORGADMIN role so administrators can manage and monitor multiple accounts centrally. When the goal is to retrieve account-level metadata across the organization from one place, the correct pattern is to use organization-scoped metadata such as ORGANIZATION_USAGE views from the organization account. This is more efficient and operationally appropriate than connecting to each account individually and querying ACCOUNT_USAGE. It also reflects the separation of responsibilities in Snowflake: member-account roles such as ACCOUNTADMIN or SECURITYADMIN operate within a specific account, whereas ORGADMIN operates in the organization context. Candidates should recognize that organization-wide visibility comes from the organization account, not from SHOW commands run in arbitrary member accounts. This aligns with Snowflake documentation on Organizations, organization accounts, ORGADMIN responsibilities, and organization-level usage views.
- A. Correct.
Correct. The organization account is designed for organization-wide administration, and ORGADMIN can use organization-level metadata, including ORGANIZATION_USAGE views, to inspect information across accounts from a central location. This is the most effective approach for reviewing account inventory and certain organization-wide operational metadata without logging into each account separately. It aligns with Snowflake best practices for centralized organizational tasks.
- B. Incorrect.
Incorrect. While ACCOUNT_USAGE can provide useful metadata within an individual account, this approach does not satisfy the requirement efficiently because it requires logging into each account separately and manually consolidating results. The scenario explicitly asks for a single-place, organization-wide solution, which is what the organization account and ORGANIZATION_USAGE are intended to provide.
- C. Incorrect.
Incorrect. Replication and failover metadata is not exposed organization-wide simply by running a SHOW command from any member account. SHOW commands are scoped to the current account and object visibility rules. A member account does not automatically have cross-account visibility for organizational reporting purposes.
- D. Incorrect.
Incorrect. ORGADMIN is a role in the organization account and does not become organization-wide operational authority inside each member account by granting SECURITYADMIN. In addition, DATABASE_USAGE is not the correct mechanism for centralized organization-wide replication status reporting. This option reflects a misconception about both role scope and metadata view purpose.