ADA-C01 Question 206
Single answerUse region IDs and region groupsA global company is preparing to replicate data from its Snowflake account in AWS US East (N. Virginia) to a new account in AWS Canada (Central). The administrator wants to validate ahead of time whether cross-region replication is supported between these two regions and whether they belong to a grouping Snowflake uses for replication and failover planning. Which action should the administrator take?
- A
Query SHOW REGIONS and compare the region_group values for the source and target regions
- B
Run SHOW REPLICATION ACCOUNTS to verify whether both accounts are in the same region ID
- C
Use DESCRIBE ORGANIZATION to list all supported replication region pairs and failover groups
- D
Query ACCOUNT_USAGE.REGIONS to confirm that both regions have identical cloud provider endpoint URLs
Show answer and explanation
Correct answer: A
Explanation
When planning cross-region replication or failover, administrators should verify Snowflake's region metadata using region IDs and region groups rather than relying on account naming, endpoint URLs, or organization metadata. The practical approach is to use SHOW REGIONS, which exposes region details such as the region identifier and region_group. This helps confirm the exact source and target regions involved and supports correct replication planning. In Snowflake documentation, region IDs are the canonical identifiers for Snowflake regions, and region groups are used to organize regions in ways that matter for cross-region features such as replication and failover. Using SHOW REGIONS aligns with Snowflake best practices for validating region-specific configuration before setting up business continuity features.
- A. Correct.
Correct. Snowflake provides region metadata, including region identifiers and region groups, through SHOW REGIONS. Administrators can use this output to confirm the source and target region IDs and see the region_group values that Snowflake uses when organizing regions for features such as replication and failover planning. This is the most direct way to validate region information before configuring cross-region replication.
- B. Incorrect.
Incorrect. SHOW REPLICATION ACCOUNTS is used to view accounts enabled for replication relationships, not to validate region IDs or region groups. Also, cross-region replication does not require the accounts to be in the same region ID; by definition, different regions have different region IDs.
- C. Incorrect.
Incorrect. DESCRIBE ORGANIZATION does not provide a catalog of supported replication region pairs or failover groups. An administrator might choose this option because organizations are involved in account-level administration, but region metadata is not exposed this way.
- D. Incorrect.
Incorrect. ACCOUNT_USAGE does not provide a REGIONS view for this purpose, and matching endpoint URLs would not establish whether two regions are in the same Snowflake region group or whether replication is supported. Endpoint URLs are not the mechanism Snowflake documents for planning replication between regions.