Share security and governance in Snowflake - Mini Project: Build & Apply

Share Security and Governance in Snowflake

📖 Scenario: You are working as a cloud data engineer. Your company uses Snowflake to share data securely with partners. You need to set up a secure data share with proper governance controls to ensure only authorized users can access the shared data.

🎯 Goal: Build a Snowflake data share with controlled access by creating a share, adding a database to it, and granting usage privileges to a specific role. This will demonstrate how to securely share data and manage governance in Snowflake.

📋 What You'll Learn

Create a Snowflake share named partner_share

Add the database sales_db to the share

Create a role named partner_role

Grant usage on the share partner_share to the role partner_role

💡 Why This Matters

🌍 Real World

Companies often share data securely with partners or customers using Snowflake shares. Proper governance ensures only authorized users can access shared data.

💼 Career

Cloud data engineers and administrators must know how to configure secure data sharing and manage access controls in Snowflake to meet compliance and security requirements.

1

Create a Snowflake share

Write a Snowflake SQL statement to create a share named partner_share.

Snowflake

-- Your code here to create the share partner_share

Hint

Use the CREATE SHARE command followed by the share name.

2

Add database to the share

Write a Snowflake SQL statement to add the database sales_db to the share partner_share.

Snowflake

CREATE SHARE partner_share;
-- Your code here to add sales_db to partner_share

Hint

Use ALTER SHARE <share_name> ADD DATABASE <database_name> to add a database to the share.

3

Create a role for partner access

Write a Snowflake SQL statement to create a role named partner_role.

Snowflake

CREATE SHARE partner_share;
ALTER SHARE partner_share ADD DATABASE sales_db;
-- Your code here to create role partner_role

Hint

Use CREATE ROLE <role_name> to create a new role.

4

Grant usage on share to the role

Write a Snowflake SQL statement to grant usage on the share partner_share to the role partner_role.

Snowflake

CREATE SHARE partner_share;
ALTER SHARE partner_share ADD DATABASE sales_db;
CREATE ROLE partner_role;
-- Your code here to grant usage on partner_share to partner_role

Hint

Use GRANT USAGE ON SHARE <share_name> TO ROLE <role_name> to allow the role to access the share.

Practice

1. What is the main purpose of a share in Snowflake?

easy

A. To safely share data without copying or moving it

B. To create a backup of data in another region

C. To encrypt data before storage

D. To delete data from multiple accounts

Solution

1. Step 1: Understand the concept of a share

   A share in Snowflake allows data to be accessed by other accounts without physically moving or copying the data.

2. Step 2: Compare options with the concept

   The options describing encryption before storage, creating backups in another region, and deleting data from multiple accounts are unrelated to sharing data safely.

3. Final Answer:

   To safely share data without copying or moving it -> Option A

4. Quick Check:

   Share = Safe data access without moving [OK]

Hint: Shares let others see data without moving it [OK]

Common Mistakes:

• Thinking shares copy data to other accounts
• Confusing shares with backups
• Assuming shares encrypt data automatically

2. Which SQL command correctly grants usage on a share to a specific account in Snowflake?

easy

A. GRANT USAGE TO SHARE my_share ACCOUNT 'account_name';

B. GRANT SHARE ON USAGE my_share TO ACCOUNT 'account_name';

C. GRANT USAGE ON SHARE my_share TO ACCOUNT = 'account_name';

D. GRANT ACCOUNT USAGE ON SHARE my_share TO 'account_name';

Solution

1. Step 1: Recall correct GRANT syntax for shares

   The correct syntax is: GRANT USAGE ON SHARE <share_name> TO ACCOUNT = '<account_name>';

2. Step 2: Check each option's syntax

   Only GRANT USAGE ON SHARE my_share TO ACCOUNT = 'account_name'; matches the correct syntax. Others have incorrect order or missing keywords.

3. Final Answer:

   GRANT USAGE ON SHARE my_share TO ACCOUNT = 'account_name'; -> Option C

4. Quick Check:

   GRANT USAGE ON SHARE ... TO ACCOUNT = ... [OK]

Hint: GRANT USAGE ON SHARE ... TO ACCOUNT = 'name' [OK]

Common Mistakes:

• Swapping keywords order
• Omitting the equal sign after ACCOUNT
• Using incorrect object types in GRANT

3. Given the following SQL commands, what will be the result when account 'A' tries to query the shared table?

CREATE SHARE my_share;
GRANT USAGE ON DATABASE my_db TO SHARE my_share;
GRANT SELECT ON TABLE my_db.public.my_table TO SHARE my_share;
GRANT USAGE ON SHARE my_share TO ACCOUNT = 'A';

medium

A. Account 'A' cannot query because database usage is not granted

B. Account 'A' can query my_table successfully

C. Account 'A' cannot query because SELECT privilege is missing

D. Account 'A' cannot query because share usage is not granted

Solution

1. Step 1: Check granted privileges on share

   The share has USAGE on the database and SELECT on the table granted, and account 'A' has USAGE on the share.

2. Step 2: Confirm account 'A' can access shared data

   With these grants, account 'A' can query the shared table successfully.

3. Final Answer:

   Account 'A' can query my_table successfully -> Option B

4. Quick Check:

   Proper grants = Access allowed [OK]

Hint: Grant database usage, table select, and share usage to account [OK]

Common Mistakes:

• Forgetting to grant USAGE on database to share
• Missing SELECT privilege on table
• Not granting USAGE on share to account

4. You receive an error when trying to grant SELECT on a table to a share: SQL compilation error: Insufficient privileges. What is the most likely cause?

medium

A. You forgot to create the database

B. The share does not exist

C. The account name is misspelled

D. You do not have OWNERSHIP privilege on the table

Solution

1. Step 1: Understand privilege requirements for granting SELECT to share

   Granting SELECT on a table to a share requires OWNERSHIP or appropriate privileges on that table.

2. Step 2: Analyze error cause

   Insufficient privileges error usually means the user lacks OWNERSHIP or necessary rights on the table.

3. Final Answer:

   You do not have OWNERSHIP privilege on the table -> Option D

4. Quick Check:

   OWNERSHIP needed to grant SELECT to share [OK]

Hint: OWNERSHIP needed to grant privileges on objects [OK]

Common Mistakes:

• Assuming share existence causes privilege errors
• Confusing account name typos with privilege errors
• Ignoring ownership requirements

5. You want to share a subset of data securely with multiple external accounts but restrict access to only certain tables and columns. Which Snowflake feature combination should you use?

hard

A. Create a share with specific tables and use secure views to limit columns, then grant share usage to accounts

B. Create a share with all tables and rely on account-level access control

C. Copy data to each account and grant full access

D. Use database replication to share data and restrict columns via masking policies

Solution

1. Step 1: Identify how to limit tables and columns in shares

   Shares can include specific tables only. To restrict columns, secure views can be created exposing only allowed columns.

2. Step 2: Confirm how to share with multiple accounts securely

   Granting USAGE on the share to multiple accounts allows controlled access without copying data.

3. Final Answer:

   Create a share with specific tables and use secure views to limit columns, then grant share usage to accounts -> Option A

4. Quick Check:

   Shares + secure views = controlled multi-account access [OK]

Hint: Use secure views inside shares to limit columns [OK]

Common Mistakes:

• Sharing all tables without column restrictions
• Copying data instead of sharing
• Using replication which is for disaster recovery, not sharing