ADA-C01 Question 2
Single answerI need one more page for Domain 6.0.Here are all 6 domains with every skill and sub-item:A Snowflake administrator is preparing a business continuity design for a critical production account. The company requires recovery from an accidental table drop within minutes, and it also requires the ability to continue operations in another cloud region if an entire region becomes unavailable. Cost control is important, so the solution should avoid keeping a fully duplicated environment running unless necessary. Which approach best meets these requirements?
- A
Enable Time Travel and Fail-safe on the production database, and rely on Fail-safe for cross-region business continuity.
- B
Create database replication to a secondary account in another region, promote the secondary only during a regional outage, and use Time Travel in the primary account for accidental object recovery.
- C
Use zero-copy cloning of the production database into another region on a weekly schedule, and use the clone as the recovery environment for both accidental drops and regional outages.
- D
Configure Tri-Secret Secure for the account and use it to recover dropped objects and provide automatic regional failover.
Show answer and explanation
Correct answer: B
Explanation
The best answer is to combine Time Travel for operational recovery of accidental changes with cross-region replication for business continuity. In Snowflake, Time Travel allows administrators to recover dropped or changed data within the data retention period, making it suitable for accidental table drops. For account- or region-level continuity, Snowflake supports replication and failover capabilities across regions and clouds, depending on edition and configuration. Promoting a secondary only when needed helps meet cost-control requirements because the organization avoids running a full active-active environment continuously. Fail-safe should not be treated as a business continuity strategy; it is a Snowflake-managed emergency recovery feature with limited customer control and slower recovery objectives. This aligns with Snowflake documentation and best practices for separating operational recovery objectives from disaster recovery architecture.
- A. Incorrect.
Incorrect. Time Travel helps recover data changes such as accidental drops or deletes within the configured retention period, and Fail-safe provides a last-resort recovery mechanism managed by Snowflake. However, Fail-safe is not intended for customer-driven business continuity or cross-region failover. It does not provide an operational secondary environment in another region.
- B. Correct.
Correct. This design addresses both requirements using the appropriate Snowflake capabilities. Time Travel is the primary mechanism for quick recovery from accidental object drops. For region-level disaster recovery/business continuity, database replication to a secondary account in another region provides a synchronized copy that can be promoted during an outage. This also supports cost control because the secondary does not need to be actively serving workloads until failover is required.
- C. Incorrect.
Incorrect. Zero-copy cloning is useful for fast, space-efficient copies inside Snowflake, but it is not the primary mechanism for cross-region disaster recovery. Clones also depend on the source object's metadata and do not replace replication/failover groups for regional resiliency. A weekly clone schedule would also create unacceptable data loss exposure for a critical production workload.
- D. Incorrect.
Incorrect. Tri-Secret Secure is a key management/security feature related to encryption control, not a disaster recovery or object recovery feature. It does not restore dropped tables and does not provide regional failover capabilities.