ADA-C01 Question 505
Single answer6.1 Manage data replication.A global company uses Snowflake in AWS us-east-1 as its primary region and AWS eu-west-1 as its disaster recovery region. The administrators created a failover group to replicate several databases and account objects to the secondary account. During a DR test, analysts in eu-west-1 report that one critical database is missing, even though scheduled replication for the failover group is succeeding. The security team also notices that a newly created network policy was not present in the secondary account. Which action is the MOST appropriate to ensure both the missing database and the new network policy are included in future replications?
- A
Modify the existing failover group to include the missing database and the NETWORK POLICIES object type, then continue or trigger replication for that failover group.
- B
Create a database replication group for the missing database, because failover groups cannot replicate databases and account objects together.
- C
Run a manual refresh on the secondary account, because failover groups automatically include all newly created databases and account objects after the first replication.
- D
Promote the secondary account to primary, add the missing database and network policy there, and then fail back so the original primary account inherits those objects.
Show answer and explanation
Correct answer: A
Explanation
This scenario tests practical administration of Snowflake replication and failover groups. For disaster recovery across regions/accounts, failover groups are used to replicate supported databases and supported account objects together. A key operational detail is that replication is scope-based: only the databases and account object types defined in the failover group are replicated. If administrators add a new database later, or expect supported account objects such as network policies to appear in the secondary account, they must ensure those items are included in the failover group configuration. After altering the failover group, the next scheduled replication or an explicit refresh will copy the newly included objects. This aligns with Snowflake documentation on replication and failover groups, which distinguishes between database replication and failover groups and emphasizes that only explicitly included supported objects are replicated.
- A. Correct.
Correct. In Snowflake, a failover group is the mechanism used to replicate and fail over supported databases together with supported account objects. Objects are replicated only if they are explicitly included in the failover group definition. If a new database or supported account object type such as network policies was not included, administrators must alter the failover group to add them, and then allow the next scheduled refresh or trigger replication. This directly addresses both symptoms in the scenario.
- B. Incorrect.
Incorrect. This reflects a common misunderstanding. Failover groups are specifically designed to replicate collections of supported databases and account objects together for business continuity and disaster recovery. Creating a separate database replication group is not the right fix for a scenario already using a failover group for coordinated replication of databases plus account-level objects.
- C. Incorrect.
Incorrect. Failover groups do not automatically expand to include every newly created database or every supported account object unless those objects or object types are part of the group's definition. A replication refresh only updates the objects already configured for replication; it does not discover and add out-of-scope objects automatically.
- D. Incorrect.
Incorrect. Failing over or promoting the secondary account does not solve a configuration scoping problem. Replication scope must be defined on the failover group. Adding objects on the secondary during a DR event is not the normal method for fixing omitted replication content, and it can complicate recovery planning.