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.

Practice

1. What is the main benefit of using CLONE in Snowflake for development?

easy

A. It moves data to a different cloud provider automatically.

B. It permanently deletes the original data after copying.

C. It creates a quick, space-saving copy of data without affecting the original.

D. It encrypts the data for security during development.

Solution

1. Step 1: Understand cloning purpose in development

   Cloning creates a copy of data instantly without changing the original, allowing safe development.

2. Step 2: Identify benefits of cloning

   It saves storage by sharing unchanged data and avoids risks to original data.

3. Final Answer:

   It creates a quick, space-saving copy of data without affecting the original. -> Option C

4. Quick Check:

   Clone = quick, safe copy [OK]

Hint: Clones copy data fast without changing original [OK]

Common Mistakes:

• Thinking clone deletes original data
• Believing clone moves data between clouds
• Confusing clone with encryption

2. Which of the following is the correct syntax to clone a table named sales_data in Snowflake?

easy

A. CREATE TABLE sales_data_clone CLONE sales_data;

B. CREATE TABLE sales_data_clone AS CLONE sales_data;

C. CLONE TABLE sales_data TO sales_data_clone;

D. COPY TABLE sales_data TO sales_data_clone;

Solution

1. Step 1: Recall Snowflake clone syntax

   The correct syntax is CREATE TABLE new_table CLONE source_table;.

2. Step 2: Match syntax to options

   CREATE TABLE sales_data_clone CLONE sales_data; matches the correct syntax exactly.

3. Final Answer:

   CREATE TABLE sales_data_clone CLONE sales_data; -> Option A

4. Quick Check:

   CREATE TABLE ... CLONE ... = correct syntax [OK]

Hint: Use CREATE TABLE new_table CLONE source_table syntax [OK]

Common Mistakes:

• Using AS CLONE instead of CLONE
• Using COPY instead of CLONE
• Incorrect order of keywords

3. Given the following commands:

CREATE TABLE orders (id INT, amount FLOAT);
INSERT INTO orders VALUES (1, 100.0), (2, 200.0);
CREATE TABLE orders_clone CLONE orders;
INSERT INTO orders_clone VALUES (3, 300.0);
SELECT COUNT(*) FROM orders;

What will be the result of the SELECT COUNT(*) FROM orders; query?

medium

A. 2

B. 3

C. 0

D. Error

Solution

1. Step 1: Understand cloning effect on data

   Cloning creates a copy at that moment. Changes to clone do not affect original.

2. Step 2: Analyze inserts and counts

   Original table has 2 rows inserted. The clone gets a new row inserted separately.

3. Step 3: Query original table count

   Original table still has 2 rows; clone changes do not affect it.

4. Final Answer:

   2 -> Option A

5. Quick Check:

   Original rows unchanged after clone insert [OK]

Hint: Clone changes don't affect original data count [OK]

Common Mistakes:

• Assuming clone insert adds to original
• Thinking clone shares insert changes
• Expecting error due to cloning

4. You cloned a database for testing but later found that some data changes in the clone are missing. Which is the most likely cause?

medium

A. You forgot to commit the changes in the clone before querying.

B. Cloning only copies metadata, not data.

C. Changes were made in the original, not the clone.

D. You cloned the database before the data was inserted.

Solution

1. Step 1: Understand cloning timing

   Cloning copies data as it exists at clone time; later changes in source are not included.

2. Step 2: Analyze missing data cause

   If clone was made before data insertion, clone won't have that data.

3. Final Answer:

   You cloned the database before the data was inserted. -> Option D

4. Quick Check:

   Clone snapshot time matters for data presence [OK]

Hint: Clone captures data state at clone time only [OK]

Common Mistakes:

• Assuming clone updates with source changes
• Confusing metadata-only clone
• Forgetting to commit changes

5. You want to create a backup of a large production schema without using extra storage. Which Snowflake feature should you use and why?

hard

A. Use CREATE DATABASE AS COPY which compresses data automatically.

B. Use CLONE to create a schema copy because it shares unchanged data and saves storage.

C. Create a new schema and manually copy all tables to save storage.

D. Export data to CSV files and store externally for backup.

Solution

1. Step 1: Identify backup needs

   Backup should be space-efficient and quick for large data.

2. Step 2: Evaluate Snowflake features

   Cloning creates instant copies sharing unchanged data, saving storage space.

3. Step 3: Compare options

   Exporting or manual copying uses more storage and time; no CREATE DATABASE AS COPY command exists.

4. Final Answer:

   Use CLONE to create a schema copy because it shares unchanged data and saves storage. -> Option B

5. Quick Check:

   Clone = instant, space-saving backup [OK]

Hint: Clone shares data, saves space for backups [OK]

Common Mistakes:

• Thinking manual copy saves storage
• Assuming export is space-efficient
• Using non-existent commands