SnowPro Advanced: Administrator free question 5 / 10 · Domain 2: Account Management and Data Governance
From the account that holds a primary database, a replication and failover SQL statement must identify an account in a different region group using the legacy account locator XY12345. Which form matches the documentation?
- region_group.snowflake_region.XY12345, reading the values from the host name of the connection URL
- region_group.snowflake_region.XY12345, taking the values from SHOW REPLICATION ACCOUNTS
- XY12345 alone, since locators are unique in the organization; just confirm it with SHOW REPLICATION ACCOUNTS
- snowflake_region.XY12345, reading the values from the host name of the connection URL
Show the answer and explanation
Answer: B
Why this is correct
The preferred way to identify an account in replication and failover SQL is organization name plus account name, which works for any location. If the legacy locator is used instead, extra segments may be needed depending on where the remote account is relative to the primary: the locator alone in the same region, snowflake_region.account_locator in another region of the same region group, and region_group.snowflake_region.account_locator in a different region group. The values for snowflake_region and region_group can be found in the output of SHOW REPLICATION ACCOUNTS.
Why the other options are wrong
"snowflake_region.XY12345, reading the values from the host name of the connection URL" … This form is enough for an account in another region of the same region group. A different region group also needs the region_group segment, and the values come from SHOW REPLICATION ACCOUNTS rather than a URL.
"XY12345 alone, since locators are unique in the organization; just confirm it with SHOW REPLICATION ACCOUNTS" … Confirming values with SHOW REPLICATION ACCOUNTS is right, but the locator alone works only for an account in the same region as the primary. For a different region group, the extra segments are needed to identify the account uniquely.
"region_group.snowflake_region.XY12345, reading the values from the host name of the connection URL" … The form is right, but the source of the values is not. A locator URL contains cloud_region_id, the cloud region identifier dictated by the cloud platform, not the Snowflake region and region group values; those come from SHOW REPLICATION ACCOUNTS.
Key point
Using organization_name.account_name avoids having to think about regions and region groups. With locator forms, choosing the wrong form for the location means the remote account cannot be identified and the statement fails.