Clone use cases (dev, testing, backups) in Snowflake - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use cloning for development environments in Snowflake?

Which of the following is the main advantage of using Snowflake's cloning feature for development environments?

A It disables access controls on the cloned data.

B It creates a full physical copy of data, increasing storage costs.

C It requires manual data export and import for each clone.

D It allows instant creation of a zero-copy clone, saving time and storage.

💡 Hint

Think about how cloning affects storage and speed.

Snowflake cloning creates zero-copy clones instantly, which saves time and storage compared to copying data physically.

❓ service_behavior

intermediate

What happens to data changes in a Snowflake clone?

After cloning a database in Snowflake, if you modify data in the clone, what happens to the original database?

A The original database data changes as well.

B The original database remains unchanged; changes are isolated to the clone.

C Both databases become read-only.

D The clone deletes the original database automatically.

💡 Hint

Consider how cloning isolates data changes.

Snowflake clones share data initially but diverge when changes occur, so changes in the clone do not affect the original.

❓ Architecture

advanced

Best cloning strategy for backup and restore in Snowflake

You want to create a backup strategy using Snowflake cloning that allows quick restore to a previous state. Which approach is best?

A Create a clone of the production database daily with a timestamped name to keep multiple restore points.

B Export data to external storage daily instead of cloning.

C Create a clone of the production database daily and overwrite it each time.

D Use cloning only once and rely on manual snapshots.

💡 Hint

Think about how to keep multiple restore points efficiently.

Timestamped clones keep multiple restore points without duplicating data, enabling quick restores to any point.

❓ security

advanced

Security considerations when cloning in Snowflake

When cloning a database in Snowflake for testing, which security aspect must you verify?

A Cloning copies all access permissions and roles to the clone, so review them before use.

B Cloning disables encryption on the cloned data.

C Cloning removes all user access permissions from the clone.

D Cloning automatically grants all users full access to the clone.

💡 Hint

Consider how permissions behave after cloning.

Cloning copies data and metadata including access permissions, so you must review and adjust permissions on clones to maintain security.

✅ Best Practice

expert

Optimizing storage costs using Snowflake cloning for backups

You have large production data and want to minimize storage costs while keeping frequent backups using Snowflake cloning. Which practice achieves this best?

A Disable time travel and rely only on external backups.

B Keep all clones indefinitely without pruning old clones.

C Use zero-copy clones with time travel retention and periodically drop old clones to free storage.

D Create full physical copies of data for each backup to ensure data safety.

💡 Hint

Think about how cloning and time travel affect storage.

Zero-copy clones share storage with the original data, and time travel allows recovery. Dropping old clones frees storage, optimizing costs.