ADA-C01 Question 510
Single answerReplicate account-level objectsA global company uses Snowflake Business Critical Edition with accounts in AWS us-east-1 and AWS us-west-2. The primary account hosts a custom network policy, several account parameters, and a resource monitor that must also exist in the secondary account as part of a disaster recovery design. The lead administrator wants to minimize manual reconfiguration and ensure these account-level objects are synchronized through failover groups. Which configuration should the administrator use?
- A
Create a failover group in the primary account and include the ACCOUNT PARAMETERS, NETWORK POLICIES, and RESOURCE MONITORS object types in the allowed object list before enabling replication to the secondary account.
- B
Create a replication group in the primary account and add ACCOUNT objects such as network policies, account parameters, and resource monitors, because replication groups are designed for account-level object replication.
- C
Use database replication for the databases that reference these settings, because account-level objects associated with replicated databases are automatically included during refresh.
- D
Export the account-level configuration with SHOW commands and recreate it in the secondary account after failover, because Snowflake does not support replication of account parameters, network policies, or resource monitors.
Show answer and explanation
Correct answer: A
Explanation
For disaster recovery scenarios that require replication of account-level objects, administrators should use failover groups. In Snowflake, failover groups are the mechanism intended to replicate and fail over supported account objects in addition to replicated databases and shares. This is the key distinction from replication groups, which are not the correct tool for broad account-level failover needs. In practice, if an organization needs objects such as network policies, resource monitors, and account parameters available in a secondary account with minimal manual effort, those supported object types should be included in a failover group and refreshed according to the DR plan. This aligns with Snowflake documentation on replication and failover, especially the sections covering failover groups and replication of account objects.
- A. Correct.
Correct. Account-level objects are replicated by using failover groups, not database replication alone. Failover groups can include supported account objects such as account parameters, network policies, and resource monitors, allowing those objects to be replicated and failed over together to a secondary account for business continuity and disaster recovery.
- B. Incorrect.
Incorrect. This reverses the purpose of replication groups and failover groups. Replication groups are primarily for databases and certain associated objects, whereas failover groups are used when you need account-level objects and account failover capabilities. Choosing a replication group for account-level objects is a common misconception.
- C. Incorrect.
Incorrect. Database replication does not automatically carry over account-level objects such as network policies, account parameters, or resource monitors. Those are outside the scope of a database and must be handled through account-level replication mechanisms, specifically failover groups when supported.
- D. Incorrect.
Incorrect. Manual export and recreation may be possible operationally, but it does not meet the requirement to minimize manual reconfiguration or keep the objects synchronized through Snowflake-managed replication. Snowflake does support replication of supported account-level objects through failover groups.