Snowflake database replication uses a primary-secondary architecture in which the source database provides data and object definitions, while the secondary database receives synchronized snapshots through explicit or scheduled refresh operations.
The refresh command must be executed in the Snowflake account containing the secondary database.
In this scenario, PROD_AWS_EAST is the primary database located in AWS_EAST. PROD_AWS_WEST is the secondary database located in AWS_WEST.
Therefore, the appropriate operation is executed from the AWS_WEST account:
ALTER DATABASE PROD_AWS_WEST REFRESH;
Option B correctly identifies both the account location and SQL command.
Options A and C use REFRESH DATABASE, which is not the documented syntax for refreshing a secondary Snowflake database.
Option D uses the correct ALTER DATABASE syntax but identifies the wrong account. The refresh must be initiated against the secondary database rather than the primary source account.
The refresh synchronizes supported data and object changes from the primary database. Snowflake also permits refresh operations to be scheduled through tasks where appropriate.
Current-version qualification: The command remains supported for legacy database replication, but Snowflake recommends replication and failover groups for newer business-continuity architectures. A production design should also establish recovery point objectives, appropriate refresh schedules, and replication monitoring.
Official Snowflake references: ALTER DATABASE — REFRESH; Replicating Databases Across Multiple Accounts; Introduction to Database Replication Across Multiple Accounts.
Submit