Granting and revoking privileges in Snowflake - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to grant SELECT privilege on the table to the user.

Snowflake

GRANT [1] ON TABLE sales_data TO USER analyst;

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

ASELECT

BUPDATE

CDELETE

DINSERT

Attempts:

3 left

💡 Hint

Common Mistakes

Using INSERT instead of SELECT

Using DELETE which removes data

The SELECT privilege allows the user to read data from the table.

2fill in blank

medium

Complete the code to revoke the USAGE privilege on the schema from the role.

Snowflake

REVOKE [1] ON SCHEMA marketing FROM ROLE marketing_analyst;

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

AOWNERSHIP

BSELECT

CCREATE

DUSAGE

Attempts:

3 left

💡 Hint

Common Mistakes

Revoking SELECT instead of USAGE

Revoking OWNERSHIP which is a higher privilege

USAGE privilege on a schema allows access to objects inside it. Revoking it removes that access.

3fill in blank

hard

Fix the error in the code to grant the role the ability to create schemas in the database.

Snowflake

GRANT [1] ON DATABASE sales_db TO ROLE data_engineer;

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

ACREATE SCHEMA

BSELECT

CCREATE

DCREATE TABLE

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'CREATE TABLE' which is invalid

Using SELECT instead of CREATE SCHEMA

The CREATE SCHEMA privilege on a database allows creating schemas inside it. 'CREATE TABLE' is not a valid privilege keyword.

4fill in blank

hard

Fill both blanks to grant the role the ability to read and write data on the table.

Snowflake

GRANT [1], [2] ON TABLE customer_info TO ROLE sales_team;

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

ASELECT

BINSERT

CDELETE

DUSAGE

Attempts:

3 left

💡 Hint

Common Mistakes

Using DELETE which removes data

Using USAGE which is for schemas

SELECT allows reading data, and INSERT allows adding new data to the table.

5fill in blank

hard

Fill all three blanks to revoke all privileges on the database from the user.

Snowflake

REVOKE [1], [2], [3] ON DATABASE analytics_db FROM USER data_scientist;

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

AUSAGE

BCREATE SCHEMA

COWNERSHIP

DMODIFY

Attempts:

3 left

💡 Hint

Common Mistakes

Revoking MODIFY which is not a valid privilege

Missing OWNERSHIP privilege

Revoking USAGE, CREATE SCHEMA, and OWNERSHIP removes access, ability to create schemas, and full control of the database.

Practice

1. What is the main purpose of granting privileges in Snowflake?

easy

A. To allow roles to perform specific actions on database objects

B. To create new users in the system

C. To delete roles from the account

D. To backup data automatically

Solution

1. Step 1: Understand the role of privileges

   Privileges control what actions roles can perform on database objects like tables or views.

2. Step 2: Identify the purpose of granting privileges

   Granting privileges gives roles permission to do specific tasks, such as SELECT or INSERT on tables.

3. Final Answer:

   To allow roles to perform specific actions on database objects -> Option A

4. Quick Check:

   Grant privileges = Allow role actions [OK]

Hint: Privileges let roles do tasks on objects, not users directly [OK]

Common Mistakes:

• Confusing privileges with user creation
• Thinking privileges delete roles
• Assuming privileges backup data

2. Which of the following is the correct syntax to grant SELECT privilege on a table named sales_data to a role named analyst_role?

easy

A. GRANT SELECT TO ROLE analyst_role ON sales_data;

B. GRANT ROLE analyst_role TO SELECT ON TABLE sales_data;

C. GRANT SELECT ON ROLE analyst_role TO TABLE sales_data;

D. GRANT SELECT ON TABLE sales_data TO ROLE analyst_role;

Solution

1. Step 1: Recall the correct GRANT syntax

   The syntax is: GRANT <privilege> ON <object_type> <object_name> TO ROLE <role_name>;

2. Step 2: Match the syntax to the options

   GRANT SELECT ON TABLE sales_data TO ROLE analyst_role; matches the correct order and keywords exactly.

3. Final Answer:

   GRANT SELECT ON TABLE sales_data TO ROLE analyst_role; -> Option D

4. Quick Check:

   GRANT privilege ON object TO ROLE [OK]

Hint: Remember: GRANT privilege ON object TO ROLE role_name [OK]

Common Mistakes:

• Mixing order of keywords
• Placing role before privilege
• Using TO TABLE instead of TO ROLE

3. Given the following commands executed in order:

GRANT SELECT ON TABLE customers TO ROLE sales_role;
REVOKE SELECT ON TABLE customers FROM ROLE sales_role;
GRANT INSERT ON TABLE customers TO ROLE sales_role;

What privileges does sales_role have on the customers table after these commands?

medium

A. Only SELECT

B. Only INSERT

C. SELECT and INSERT

D. No privileges

Solution

1. Step 1: Analyze the first GRANT

   The role sales_role is granted SELECT privilege on customers.

2. Step 2: Analyze the REVOKE

   The SELECT privilege is revoked from sales_role, removing that permission.

3. Step 3: Analyze the second GRANT

   The role is granted INSERT privilege on customers.

4. Final Answer:

   Only INSERT -> Option B

5. Quick Check:

   Revoked SELECT, granted INSERT = INSERT only [OK]

Hint: Revoke removes privilege; later grants add new ones [OK]

Common Mistakes:

• Assuming revoked privileges remain
• Thinking grants accumulate without revokes
• Confusing privilege types

4. You run the command:

REVOKE ALL PRIVILEGES ON DATABASE sales_db FROM ROLE marketing_role;

But the privileges are not removed. What is the most likely reason?

medium

A. The role marketing_role does not have any privileges on sales_db

B. The syntax REVOKE ALL PRIVILEGES is invalid in Snowflake

C. You must revoke privileges from users, not roles

D. The database sales_db does not exist

Solution

1. Step 1: Check if the role has privileges

   If the role has no privileges on the database, revoking does nothing.

2. Step 2: Verify syntax and object existence

   REVOKE ALL PRIVILEGES is valid syntax, and revoking is done on roles, not users. Assume sales_db exists.

3. Final Answer:

   The role marketing_role does not have any privileges on sales_db -> Option A

4. Quick Check:

   Revoking non-existent privileges has no effect [OK]

Hint: Check if role actually has privileges before revoking [OK]

Common Mistakes:

• Assuming syntax error with REVOKE ALL PRIVILEGES
• Trying to revoke from users directly
• Ignoring role privilege state

5. You want to allow a role data_scientist to both read and write data in tables of the analytics schema but prevent it from dropping any tables. Which set of commands correctly grants and restricts privileges?

hard

A. GRANT SELECT, INSERT, UPDATE ON ALL TABLES IN SCHEMA analytics TO ROLE data_scientist;
GRANT DROP ON SCHEMA analytics TO ROLE data_scientist;

B. GRANT ALL PRIVILEGES ON SCHEMA analytics TO ROLE data_scientist;
REVOKE DROP ON SCHEMA analytics FROM ROLE data_scientist;

C. GRANT SELECT, INSERT, UPDATE ON ALL TABLES IN SCHEMA analytics TO ROLE data_scientist;
REVOKE DROP ON SCHEMA analytics FROM ROLE data_scientist;

D. GRANT SELECT, INSERT, UPDATE ON ALL TABLES IN SCHEMA analytics TO ROLE data_scientist;

Solution

1. Step 1: Grant read and write privileges

   Grant SELECT, INSERT, and UPDATE to allow reading and writing data.

2. Step 2: Revoke DROP privilege

   Explicitly revoke DROP to prevent deleting tables.

3. Step 3: Evaluate other options

   GRANT ALL PRIVILEGES ON SCHEMA analytics TO ROLE data_scientist; REVOKE DROP ON SCHEMA analytics FROM ROLE data_scientist; grants ALL privileges then revokes DROP, which is valid but less precise. GRANT SELECT, INSERT, UPDATE ON ALL TABLES IN SCHEMA analytics TO ROLE data_scientist; does not revoke DROP, so drop is allowed. GRANT SELECT, INSERT, UPDATE ON ALL TABLES IN SCHEMA analytics TO ROLE data_scientist; GRANT DROP ON SCHEMA analytics TO ROLE data_scientist; grants DROP, which is opposite of requirement.

4. Final Answer:

   GRANT SELECT, INSERT, UPDATE ON ALL TABLES IN SCHEMA analytics TO ROLE data_scientist; REVOKE DROP ON SCHEMA analytics FROM ROLE data_scientist; -> Option C

5. Quick Check:

   Grant needed privileges, revoke unwanted ones [OK]

Hint: Grant needed privileges, then revoke unwanted ones explicitly [OK]

Common Mistakes:

• Granting ALL privileges without revoking DROP
• Not revoking DROP privilege
• Granting DROP privilege by mistake