Zero-copy cloning in Snowflake - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Zero-copy Cloning Basics

What is the primary benefit of using zero-copy cloning in Snowflake?

A It instantly creates a clone without duplicating data, saving storage space.

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

C It compresses the data to reduce storage costs.

D It moves data to a different region for disaster recovery.

💡 Hint

Think about how cloning affects storage and speed.

Zero-copy cloning creates a new object that references the original data without copying it, saving storage and enabling instant clones.

❓ service_behavior

intermediate

Clone Behavior After Source Data Change

After creating a zero-copy clone of a table in Snowflake, what happens if you update data in the original table?

A The clone automatically reflects the changes made to the original table.

B The clone remains unchanged and keeps the original data state at clone time.

C The clone is deleted automatically to prevent data inconsistency.

D Both the original and clone tables become locked until changes are synced.

💡 Hint

Consider how cloning preserves data snapshots.

Zero-copy clones are snapshots at the time of cloning; changes to the original after cloning do not affect the clone.

❓ Architecture

advanced

Designing a Data Environment Using Zero-copy Cloning

You want to create multiple development environments from a large production database without increasing storage costs significantly. Which Snowflake feature should you use and why?

A Use zero-copy cloning to create instant, storage-efficient copies of the production database.

B Export and import data files for each environment to ensure data isolation.

C Create full physical copies of the database for each environment to avoid data conflicts.

D Use Snowflake Streams to replicate data changes to each environment.

💡 Hint

Think about instant copies that save storage and time.

Zero-copy cloning allows instant creation of full database clones without duplicating data, ideal for multiple environments with minimal storage impact.

❓ security

advanced

Security Implications of Zero-copy Cloning

When you create a zero-copy clone of a secure table in Snowflake, what happens to the access permissions on the clone?

A The clone shares the same access permissions but changes in permissions on the original do not affect the clone.

B The clone inherits all access permissions from the original table automatically.

C The clone has no access permissions; you must grant them explicitly after cloning.

D The clone inherits permissions and any changes to the original's permissions are reflected in the clone.

💡 Hint

Consider how Snowflake treats object permissions on clones.

Clones do not inherit access permissions automatically; permissions must be granted explicitly to control access securely.

✅ Best Practice

expert

Managing Storage Costs with Zero-copy Cloning

You have created multiple zero-copy clones of large tables for testing. Over time, you notice storage costs increasing unexpectedly. What is the most likely cause?

A Storage costs increase due to automatic backups unrelated to cloning.

B Clones physically duplicate all data, so storage grows linearly with each clone.

C Storage costs increase because Snowflake charges extra for cloning operations regardless of data size.

D Changes made to clones or original tables cause Snowflake to store additional data, increasing storage usage.

💡 Hint

Think about how data changes affect storage in zero-copy clones.

Zero-copy clones share data until changes occur; any updates cause Snowflake to store new data, increasing storage usage.