Course contents

SnowPro Core COF-C03 Study GuidePart 5: Data protection and sharingExam Focus: Part 5

Exam Focus: Part 5

Exam Focus · Part 5

Old micro-partitions power Time Travel, Fail-safe and clones. For each feature, know who can reach the data and who pays.

Know these cold

TopicRemember
Time TravelDefault 1 day. Standard: 0–1. Enterprise+: up to 90 days, permanent tables
Fail-safe7 days, fixed, permanent tables only. Only Support recovers
Transient, temporaryTime Travel 0–1 day, no Fail-safe, so cheaper storage
RecoverAT(OFFSET => -3600) or TIMESTAMP. Bad DML: BEFORE(STATEMENT => id). Dropped: UNDROP
CloneMetadata only. Not copied: grants on the cloned database or schema itself, load history, internal named stages
ReplicationDatabases and shares: all editions. Account objects, failover: Business Critical+
ShareZero-copy, read-only. Provider pays storage, consumer pays compute
Reader accountFor consumers without Snowflake. The provider pays its compute
Other regionListing with Cross-Cloud Auto-Fulfillment, or replicate, then share

Traps

  • Myth RESTORE SCHEMA brings back a dropped schema.Fact It's UNDROP SCHEMA. Rename whatever holds the name first.
  • Myth A consumer can clone or Time Travel a shared database.Fact Imported databases allow neither.
  • Myth A secondary database accepts writes.Fact It's read-only until failover promotes it.
  • Myth A plain view is safe in a share.Fact Shares take secure views by default. Plain views can leak filtered rows.
Before you turn the page
  • Walk a micro-partition from active to Time Travel to Fail-safe to gone, and say who can reach each stage.
  • List three things a clone doesn't carry.
  • Say who pays storage and compute in a direct share and in a reader account.