SnowPro Advanced Architect

By Snowflake · Question Mode

QuestionQ35

Data Storage and Processing

An Enterprise Snowflake account covers multiple business units. Earlier today, a shared production database that contains both raw-ingestion tables and curated downstream datasets was accidentally dropped.

Thirty-six hours after the database was dropped, an Architect has confirmed the following:

  1. Multiple users have modified dependent objects in other databases that referenced the original database.
  2. The original database included streams, transient staging layers, and materialized views that support data marts shared across departments.
  3. No manual backups were exported.
  4. Data-retention policies are configured, and Time Travel is set to the account maximum.

The data-recovery strategy must:

  1. MINIMIZE data loss
  2. Maintain object dependencies
  3. Follow Snowflake-recommended practice for resilience and consistency

Which strategy meets these requirements?

Explanation

UNDROP DATABASE uses Snowflake Time Travel to restore the most recent version of a dropped database in place, preserving its recoverable database objects and data as a consistent unit. Dependent objects outside that database can have been altered while it was absent, so their references must be validated and reconciled after restoration. Fail-safe is not the appropriate recovery path while Time Travel remains available; moreover, transient tables have no Fail-safe period and at most one day of Time Travel retention, so transient data beyond that window is unrecoverable.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!