ADA-C01 Question 525
Select 2Identify key-considerations for account replicationsA global company uses Snowflake Business Critical edition and wants a disaster recovery design for a production account in AWS us-east-1. The team plans to replicate the account to a secondary account in AWS us-west-2 and fail over there during a regional outage. During planning, the administrator is asked to identify key considerations that could affect what is available after failover and how the replication must be configured. Which TWO considerations are most important to validate before implementing account replication?
- A
Whether the source and target accounts are in the same organization and on supported cloud/platform regions for account replication and failover
- B
Whether compute resources such as virtual warehouses will be continuously synchronized and immediately usable in the target account after failover
- C
Whether object-level replication alone is sufficient, or whether account-level objects such as users, roles, network policies, and other supported account metadata must also be replicated for the DR design
- D
Whether Time Travel retention settings are automatically increased in the target account to match the source account's maximum retention after failover
- E
Whether replication will include unsupported objects, such as all integrations and every account parameter, without any exceptions
Show answer and explanation
Correct answers: A, C
Explanation
The best answers are 1 and 3. In Snowflake, account replication and account failover are powerful DR capabilities, but they require careful validation of prerequisites, scope, and supported object types. Two of the most important planning considerations are: (1) confirming that the source and target accounts are eligible for replication/failover, including being in the same organization and using supported region/cloud combinations; and (2) confirming that the replicated scope matches the business DR requirement, especially when the business expects account-level security and governance objects to exist after failover. A common mistake is to assume that warehouses and active compute state are replicated, or that all account objects and settings are covered with no exceptions. Snowflake documentation on account replication and failover, supported objects for replication, and replication considerations emphasizes reviewing prerequisites, edition/organization requirements, and supported object coverage before implementation.
- A. Correct.
Correct. Account replication and failover have important prerequisites and scope constraints. The accounts must be in the same Snowflake organization, and replication/failover is supported only between specific cloud/platform region combinations. Validating edition, organization relationship, and supported source/target regions is a core planning step for cross-region disaster recovery.
- B. Incorrect.
Incorrect. Virtual warehouses are compute objects and are not replicated as running compute resources in a way that makes them continuously synchronized for failover. Replication focuses on supported metadata and data needed for database/account recovery, not preserving active compute state. After failover, compute must be created or managed in the target as needed.
- C. Correct.
Correct. A major account replication consideration is whether the DR requirement includes account objects beyond databases. If the company needs users, roles, grants, network policies, and other supported account metadata available after failover, account replication scope must be reviewed carefully. Relying only on object/database replication may leave the failover account missing critical security and administration configuration.
- D. Incorrect.
Incorrect. Time Travel behavior is not handled by automatically increasing retention in the target account after failover. Retention settings are governed by object/account configuration and service limits, and candidates should not assume the target silently raises retention to match a source maximum. This option reflects a common misunderstanding that replication expands retention guarantees.
- E. Incorrect.
Incorrect. Not every object or parameter in an account is replicated. Snowflake documents supported and unsupported objects for replication/failover, and some integrations, account settings, and operational states require separate planning or recreation. Assuming there are no exceptions is a risky misconception in DR design.