Secure data sharing basics in Snowflake - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a share named 'my_share'.

Snowflake

CREATE SHARE [1];

Drag options to blanks, or click blank then click option'

Ashare1

Bshare_data

Cdata_share

Dmy_share

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different share name than 'my_share'.

Forgetting the semicolon at the end.

The command CREATE SHARE my_share; creates a new share named 'my_share'.

2fill in blank

medium

Complete the code to add the database 'sales_db' to the share 'my_share'.

Snowflake

ALTER SHARE my_share ADD DATABASE [1];

Drag options to blanks, or click blank then click option'

Asales_db

Bmarketing_db

Cfinance_db

Dhr_db

Attempts:

3 left

💡 Hint

Common Mistakes

Adding the wrong database to the share.

Misspelling the database name.

The command ALTER SHARE my_share ADD DATABASE sales_db; adds the 'sales_db' database to the share.

3fill in blank

hard

Fix the error in the code to grant usage on the share 'my_share' to the account 'ACCOUNT_B'.

Snowflake

GRANT USAGE ON SHARE [1] TO ACCOUNT ACCOUNT_B;

Drag options to blanks, or click blank then click option'

Amyshare

Bmy_share

Cshare_my

Daccount_share

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different share name than 'my_share'.

Omitting underscores in the share name.

The share name must be exactly 'my_share' to match the created share.

4fill in blank

hard

Fill both blanks to create a database from a share named 'my_share' in account 'ACCOUNT_A'.

Snowflake

CREATE DATABASE [1] FROM SHARE ACCOUNT_A.[2];

Drag options to blanks, or click blank then click option'

Ashared_sales_db

Bsales_db

Cmy_share

Daccount_a

Attempts:

3 left

💡 Hint

Common Mistakes

Using the original database name instead of a new name.

Mixing up the share name and database name.

The command creates a database named 'shared_sales_db' from the share 'my_share' in account 'ACCOUNT_A'.

5fill in blank

hard

Fill all three blanks to revoke usage on the share 'my_share' from account 'ACCOUNT_B'.

Snowflake

REVOKE [1] ON SHARE [2] FROM ACCOUNT [3];

Drag options to blanks, or click blank then click option'

AUSAGE

Bmy_share

CACCOUNT_B

DSELECT

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong privilege like SELECT instead of USAGE.

Misspelling the share or account names.

The command revokes USAGE privilege on the share 'my_share' from 'ACCOUNT_B'.

Practice

1. What is the main benefit of using secure data sharing in Snowflake?

easy

A. Encrypt data before sharing it manually

B. Share live data without making copies

C. Create multiple copies of data for each user

D. Send data files via email securely

Solution

1. Step 1: Understand secure data sharing purpose

   Secure data sharing allows sharing data directly without duplication.

2. Step 2: Compare options

   Options A, B, and D involve copying or manual steps, which are not the main benefit.

3. Final Answer:

   Share live data without making copies -> Option B

4. Quick Check:

   Secure sharing = live data, no copies [OK]

Hint: Secure sharing means no data copies needed [OK]

Common Mistakes:

• Thinking data is copied to recipients
• Confusing sharing with encryption only
• Assuming manual file transfer is secure sharing

2. Which Snowflake object do you create first to start sharing data securely?

easy

A. Share

B. Role

C. Warehouse

D. Database

Solution

1. Step 1: Identify the object for sharing

   In Snowflake, a Share object is created to define what data to share.

2. Step 2: Eliminate other options

   Databases hold data, warehouses process queries, roles manage permissions but do not start sharing.

3. Final Answer:

   Share -> Option A

4. Quick Check:

   Create a Share to share data [OK]

Hint: Start sharing by creating a Share object [OK]

Common Mistakes:

• Trying to share by creating a database
• Confusing warehouse with sharing object
• Assuming roles start sharing

3. Given this SQL snippet, what does it do?

CREATE SHARE my_share;
GRANT SELECT ON DATABASE sales_db TO SHARE my_share;
ALTER SHARE my_share ADD ACCOUNTS = ('account_123');

medium

A. Creates a share, grants access to sales_db, and shares with account_123

B. Creates a database named my_share and grants access to account_123

C. Adds a new database to sales_db and shares it with account_123

D. Creates a warehouse named my_share and assigns it to account_123

Solution

1. Step 1: Analyze each command

   CREATE SHARE my_share; creates a share object named my_share.
   GRANT SELECT ON DATABASE sales_db TO SHARE my_share; grants read access on sales_db to the share.
   ALTER SHARE my_share ADD ACCOUNTS = ('account_123'); adds account_123 as a recipient.

2. Step 2: Understand the overall effect

   This sequence shares sales_db data with account_123 via my_share.

3. Final Answer:

   Creates a share, grants access to sales_db, and shares with account_123 -> Option A

4. Quick Check:

   Share + grant + add account = share data [OK]

Hint: Look for CREATE SHARE then GRANT and ADD ACCOUNTS [OK]

Common Mistakes:

• Confusing share with database creation
• Thinking ALTER SHARE adds data, not accounts
• Mixing warehouse and share concepts

4. You run this command but get an error:

ALTER SHARE my_share ADD ACCOUNTS = ('account_123', 'account_123');

What is the likely cause?

medium

A. Account names must be numeric

B. Missing SELECT privilege on the share

C. Share name is invalid

D. Duplicate account names in the list

Solution

1. Step 1: Check the command syntax and parameters

   The command tries to add two accounts with the same name 'account_123' to the share.

2. Step 2: Identify the error cause

   Duplicate account names in the ADD ACCOUNTS list cause an error because each account must be unique.

3. Final Answer:

   Duplicate account names in the list -> Option D

4. Quick Check:

   Duplicate accounts cause errors [OK]

Hint: Avoid duplicate accounts in ADD ACCOUNTS list [OK]

Common Mistakes:

• Assuming share name is invalid without checking
• Thinking privileges cause this error
• Believing account names must be numbers

5. You want to share only specific tables from your database securely. Which approach should you use?

hard

A. Grant SELECT on the entire database to the share

B. Grant SELECT on specific schemas to the share

C. Grant SELECT on specific tables to the share

D. Create a new database with only those tables and share it

Solution

1. Step 1: Understand granularity of sharing

   Snowflake allows granting privileges at database, schema, or table level to shares.

2. Step 2: Choose the most precise option

   Granting SELECT on specific tables limits sharing to only those tables, which fits the requirement.

3. Step 3: Evaluate other options

   Granting on entire database or schema shares more than needed; creating a new database is extra work and less flexible.

4. Final Answer:

   Grant SELECT on specific tables to the share -> Option C

5. Quick Check:

   Grant on tables = share specific data [OK]

Hint: Grant on tables to share only those tables [OK]

Common Mistakes:

• Granting on database shares too much data
• Assuming schema-level grant is always best
• Creating new databases unnecessarily