Zero-copy cloning in Snowflake - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is zero-copy cloning in Snowflake?

Zero-copy cloning is a way to create a copy of a database, schema, or table instantly without duplicating the actual data. It saves storage and time by sharing the original data until changes are made.

beginner

How does zero-copy cloning save storage space?

It saves space by not copying the data itself. Instead, the clone points to the original data. Only changes made after cloning use extra storage.

beginner

Can you modify data in a zero-copy clone without affecting the original?

Yes. Changes in the clone are stored separately. The original data remains unchanged, allowing safe experimentation or testing.

intermediate

Which Snowflake objects support zero-copy cloning?

Databases, schemas, and tables can be cloned using zero-copy cloning in Snowflake.

intermediate

What happens to storage costs when you create a zero-copy clone?

Initially, storage costs do not increase because no data is copied. Costs increase only when changes are made to the clone, using additional storage.

What does zero-copy cloning in Snowflake do?

A Creates a full physical copy of data instantly

B Deletes original data after cloning

C Copies data to an external storage

D Creates a copy without duplicating data until changes occur

Zero-copy cloning creates a copy that shares the original data until changes are made, saving storage.

Which Snowflake objects can you clone using zero-copy cloning?

A Only tables

B Only databases

C Databases, schemas, and tables

D Only schemas

Snowflake supports zero-copy cloning for databases, schemas, and tables.

What happens to the original data when you modify a zero-copy clone?

A Original data remains unchanged

B Original data is overwritten

C Original data is deleted

D Original data is moved to the clone

Changes in the clone do not affect the original data.

When do storage costs increase for a zero-copy clone?

A Immediately after cloning

B Only when changes are made to the clone

C When the clone is deleted

D Storage costs never increase

Storage costs increase only when the clone diverges by changes.

Why is zero-copy cloning faster than traditional copying?

A Because it skips copying data and shares existing data

B Because it copies data to a faster disk

C Because it compresses data during copy

D Because it deletes old data first

Zero-copy cloning is fast because it does not physically copy data initially.

Explain zero-copy cloning in Snowflake and how it benefits storage and performance.

Think about how sharing data instead of copying saves space and time.

Describe what happens to data and storage costs when you modify a zero-copy clone.

Consider how changes affect storage after cloning.