ADA-C01 Question 506
Single answer6.1 Manage data replication.A global company uses Snowflake Business Critical Edition with accounts in AWS us-east-1 and AWS eu-west-1. The primary account in us-east-1 contains a database named FINANCE_DB that must be made available in eu-west-1 for disaster recovery. The DR team wants the replicated copy to stay current automatically after the initial setup, while minimizing manual operational steps. Which action should the Snowflake administrator take?
- A
Convert FINANCE_DB to a failover group and enable client redirect so the database replicates automatically across regions.
- B
Create a replication group for FINANCE_DB and set a replication schedule so Snowflake performs automatic refreshes of the secondary database.
- C
Create a secondary database for FINANCE_DB in the eu-west-1 account, then configure automatic replication refreshes from the primary database.
- D
Share FINANCE_DB from us-east-1 to eu-west-1 and create a database from the share, because shares stay synchronized automatically across regions.
Show answer and explanation
Correct answer: C
Explanation
The correct approach for this requirement is Snowflake database replication: create a secondary database for the primary database in the target account/region and configure automatic refreshes. This is the standard pattern when a single database must be replicated for disaster recovery and kept current with minimal manual intervention. Failover groups are a different feature intended for account objects and business continuity at a broader scope, not as the primary mechanism for replicating one database. Secure sharing is also not a DR substitute because it does not create a replicated secondary database that can be promoted. Snowflake documentation distinguishes clearly between database replication/failover and failover groups, and recommends scheduled refreshes to keep secondary databases synchronized.
- A. Incorrect.
Incorrect. Failover groups are used to replicate and fail over account-level objects such as users, roles, warehouses, resource monitors, and certain other supported objects. They are not the mechanism for standard database replication itself. Client redirect is related to connection redirection during failover scenarios, not to configuring database replication for a single database.
- B. Incorrect.
Incorrect. Snowflake supports database replication and failover/failback for databases, and failover groups for account objects. A standalone 'replication group' for a database is not the correct construct in this scenario. The wording may sound plausible because replication groups exist in some technologies, but for Snowflake database replication the administrator creates a secondary database from the primary database and then refreshes it manually or on a schedule.
- C. Correct.
Correct. For database replication, the administrator creates a secondary database in the target account/region from the primary database, then sets up automatic refreshes so the secondary stays current with minimal manual effort. This matches the requirement for a DR copy in another region that remains synchronized after initial setup.
- D. Incorrect.
Incorrect. Secure data sharing provides near real-time access to data without copying it, but it is not a disaster recovery replication mechanism and does not create an independently replicated database copy in the target account. In addition, cross-region sharing does not satisfy the requirement for a DR secondary database that can be promoted during a replication/failover workflow.