Granting and revoking privileges in Snowflake - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

What happens after this privilege grant?

You run the command:

GRANT SELECT ON TABLE sales TO ROLE analyst;

What is the immediate effect of this command?

Snowflake

GRANT SELECT ON TABLE sales TO ROLE analyst;

A The role 'analyst' can now read data from the 'sales' table.

B The role 'analyst' can now modify data in the 'sales' table.

C The role 'analyst' can create new tables in the database.

D The role 'analyst' can delete the 'sales' table.

💡 Hint

Think about what the SELECT privilege allows.

The SELECT privilege allows reading data from a table. It does not allow modifying, creating, or deleting tables.

❓ security

intermediate

Which command revokes the privilege to insert data?

You want to remove the ability of the role 'data_entry' to add new rows to the 'customers' table. Which command does this?

A GRANT DELETE ON TABLE customers TO ROLE data_entry;

B REVOKE INSERT ON TABLE customers FROM ROLE data_entry;

C REVOKE SELECT ON TABLE customers FROM ROLE data_entry;

D GRANT UPDATE ON TABLE customers TO ROLE data_entry;

💡 Hint

Look for the command that removes the INSERT privilege.

REVOKE INSERT removes the ability to add new rows. Other options either grant privileges or revoke different ones.

❓ Architecture

advanced

What is the effect of granting a privilege on a schema?

You execute:

GRANT USAGE ON SCHEMA sales_data TO ROLE analyst;

What does this allow the 'analyst' role to do?

A Delete the 'sales_data' schema.

B Create new databases inside the 'sales_data' schema.

C Access objects inside the 'sales_data' schema but not read data from tables.

D Read data from all tables inside the 'sales_data' schema.

💡 Hint

USAGE on a schema allows access but not data reading.

USAGE privilege on a schema allows the role to access objects inside it but does not grant data reading rights. SELECT must be granted separately on tables.

✅ Best Practice

advanced

Which approach follows least privilege principle?

You want to give a user read access to only one table in a large database. Which is the best way?

A Grant USAGE on the database and schema only.

B Grant SELECT on the entire database to the user's role.

C Grant OWNERSHIP of the table to the user's role.

D Grant SELECT on the specific table to the user's role.

💡 Hint

Least privilege means giving only what is needed.

Granting SELECT on just the needed table limits access and follows security best practices. Granting more privileges exposes unnecessary data or control.

🧠 Conceptual

expert

What error occurs if you revoke a privilege not granted?

You run:

REVOKE DELETE ON TABLE orders FROM ROLE sales_team;

But the 'sales_team' role never had DELETE privilege on 'orders'. What happens?

A The command succeeds silently with no error.

B An error is raised: privilege does not exist for role.

C The command revokes all privileges from the role.

D The command grants DELETE privilege instead.

💡 Hint

Think about idempotency of revoke commands.

In Snowflake, revoking a privilege that was never granted does not cause an error. The command succeeds silently.

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