ADA-C01 Question 524
Select 2Identify key-considerations for account replicationsA global company uses Snowflake Business Critical edition and wants to set up account replication from an AWS us-east-1 account to an AWS eu-west-1 account for disaster recovery. The source account contains custom network policies, account parameters, users, roles, and several databases. During planning, the administrators want to identify which considerations are most important before enabling account replication and failover. Which TWO statements are correct?
- A
Account replication can include account-level objects such as users, roles, and certain account parameters, but replicated objects are read-only in the target account until failover occurs.
- B
Replication between accounts in different cloud platforms, such as AWS to Azure, is supported as long as both accounts are in the same Snowflake organization.
- C
To support disaster recovery, administrators should verify edition/region support and understand that some account objects and integrations may have limitations or prerequisites for replication.
- D
Once account replication is enabled, all databases in the source account are automatically included and do not need to be explicitly considered in replication planning.
- E
Network policies and security-related account objects never replicate, so they must always be recreated manually in the target account.
Show answer and explanation
Correct answers: A, C
Explanation
The best answers are 1 and 3. In Snowflake, account replication and failover are intended for business continuity/disaster recovery and require careful validation of supported editions, regions, cloud/platform combinations, and object types. A key design principle is that replicated objects in the target act as secondary copies for DR rather than as independently writable production objects before failover. Administrators must also review supported account objects and limitations, especially for security settings, integrations, and account-level metadata. Snowflake documentation on replication and failover, account failover, and supported objects emphasizes checking prerequisites, supported regions, and object-specific limitations instead of assuming all account content replicates automatically or uniformly.
- A. Correct.
Correct. Account replication is designed to replicate supported account-level metadata and objects, including items such as users, roles, and certain account parameters, subject to Snowflake support and configuration rules. In the secondary account, replicated data and metadata are not independently managed as active primary objects; they are intended for standby/disaster recovery use until a planned or unplanned failover promotes the secondary. This is a key operational consideration because administrators should not expect to make normal changes to replicated objects in the target before failover.
- B. Incorrect.
Incorrect. Same-organization membership alone is not sufficient. Snowflake replication/failover has platform and regional support requirements, and cross-cloud replication is not generally treated as a default capability for account replication planning. Administrators must confirm the specific supported region and cloud combinations for the replication/failover features they intend to use. Choosing this option reflects the common misconception that organization-level grouping removes all replication constraints.
- C. Correct.
Correct. A major planning consideration is validating that the accounts meet Snowflake's edition and regional prerequisites for replication/failover, and that the specific object types in scope are supported. Some account objects, integrations, and security-related configurations can have limitations, dependencies, or additional setup requirements. For a DR design, administrators must review supported objects carefully rather than assume every account-level item behaves identically under replication.
- D. Incorrect.
Incorrect. Replication planning is not something administrators should treat as automatically covering every database without review. Databases and account objects must be explicitly considered in the replication design, including what is supported, what should be included, and how failover groups or replication groups are configured. This option reflects the misconception that enabling account replication removes the need for scoping and governance decisions.
- E. Incorrect.
Incorrect. The word "never" makes this statement inaccurate. Some security-related account objects, including network policies, can be part of account replication considerations, but support depends on the specific object type and Snowflake's documented behavior. The real consideration is to verify support and prerequisites, not to assume all such objects must always be rebuilt manually.