Creating custom roles in Snowflake - Practice Exercises

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Role Hierarchy in Snowflake

In Snowflake, when you create a custom role and grant it to another role, what is the effect on the privileges of the parent role?

A The parent role can use privileges of the custom role only if the custom role is granted to it explicitly.

B The custom role inherits all privileges of the parent role automatically.

C The parent role inherits all privileges of the custom role automatically.

D Privileges are not shared between roles regardless of grants.

💡 Hint

Think about how role inheritance works in Snowflake.

In Snowflake, when a role is granted to another role, the parent role inherits all privileges of the granted role. This allows hierarchical privilege management.

❓ Configuration

intermediate

Creating a Custom Role with Specific Privileges

Which Snowflake SQL command correctly creates a custom role named data_analyst and grants it the privilege to select from the sales_data schema?

A CREATE ROLE data_analyst; GRANT SELECT ON DATABASE sales_data TO ROLE data_analyst;

B CREATE ROLE data_analyst; GRANT SELECT ON SCHEMA sales_data TO ROLE data_analyst;

C CREATE ROLE data_analyst; GRANT USAGE ON SCHEMA sales_data TO ROLE data_analyst;

D CREATE ROLE data_analyst; GRANT SELECT ON TABLE sales_data TO ROLE data_analyst;

💡 Hint

Remember that to select data, the role needs SELECT privilege on the schema or tables.

The correct way is to create the role and grant SELECT privilege on the schema. Granting on database or table named sales_data is incorrect because sales_data is a schema, not a database or table.

❓ Architecture

advanced

Designing Role Hierarchy for Separation of Duties

You want to design a Snowflake role hierarchy to separate duties between data engineers and data analysts. Which design best enforces that data engineers can manage tables but cannot query data, while data analysts can query data but cannot manage tables?

A Create a <code>data_engineer</code> role with CREATE and MODIFY privileges on tables, and a separate <code>data_analyst</code> role with SELECT privileges only; do not grant either role to the other.

B Create a <code>data_analyst</code> role with all privileges and grant it to <code>data_engineer</code> role.

C Create a single role with both CREATE and SELECT privileges and assign it to both engineers and analysts.

D Create a <code>data_engineer</code> role with SELECT privileges and grant it to <code>data_analyst</code> role.

💡 Hint

Think about how granting roles affects privilege inheritance and separation.

To enforce separation of duties, roles should be distinct without granting one to the other. Data engineers get management privileges; data analysts get query privileges only.

❓ security

advanced

Preventing Privilege Escalation with Custom Roles

Which practice helps prevent privilege escalation when creating custom roles in Snowflake?

A Use the PUBLIC role to grant all privileges to custom roles.

B Grant all privileges to custom roles to avoid permission errors during operations.

C Assign the ACCOUNTADMIN role to all users and then create custom roles for auditing.

D Grant only the minimum required privileges to each custom role and avoid granting powerful roles like ACCOUNTADMIN to users directly.

💡 Hint

Think about the principle of least privilege.

Granting only necessary privileges minimizes risk of privilege escalation. Avoid giving powerful roles like ACCOUNTADMIN to users directly.

❓ service_behavior

expert

Effect of Revoking a Role in a Role Hierarchy

Consider the following Snowflake role hierarchy: role_A is granted to role_B, and role_B is granted to role_C. If role_A is revoked from role_B, what is the effect on role_C?

A <code>role_C</code> loses all privileges inherited from <code>role_A</code> because the grant chain is broken.

B <code>role_C</code> retains privileges from <code>role_A</code> because it was granted directly.

C <code>role_C</code> gains additional privileges from <code>role_A</code> automatically.

D Revoking <code>role_A</code> from <code>role_B</code> has no effect on <code>role_C</code>.

💡 Hint

Consider how privilege inheritance works through role grants.

Since role_C inherits privileges from role_B, which in turn inherits from role_A, revoking role_A from role_B breaks the chain. Therefore, role_C loses privileges from role_A.

Practice

1. What is the main purpose of creating a custom role in Snowflake?

easy

A. To create a new user account

B. To store data in a new database

C. To run SQL queries faster

D. To control and manage user access permissions

Solution

1. Step 1: Understand role purpose

   Custom roles in Snowflake are designed to manage what users can do by controlling permissions.

2. Step 2: Identify correct function

   Creating a role is not about storing data, creating users, or speeding queries, but about access control.

3. Final Answer:

   To control and manage user access permissions -> Option D

4. Quick Check:

   Role purpose = Access control [OK]

Hint: Roles control permissions, not data or users [OK]

Common Mistakes:

• Confusing roles with users
• Thinking roles store data
• Assuming roles speed up queries

2. Which of the following is the correct syntax to create a new role named data_analyst in Snowflake?

easy

A. CREATE ROLE data_analyst;

B. NEW ROLE data_analyst;

C. MAKE ROLE data_analyst;

D. ADD ROLE data_analyst;

Solution

1. Step 1: Recall Snowflake role creation syntax

   The correct command to create a role is CREATE ROLE role_name;.

2. Step 2: Match syntax with options

   Only CREATE ROLE data_analyst; uses the correct CREATE ROLE syntax.

3. Final Answer:

   CREATE ROLE data_analyst; -> Option A

4. Quick Check:

   CREATE ROLE = correct syntax [OK]

Hint: Use CREATE ROLE to make new roles [OK]

Common Mistakes:

• Using NEW ROLE instead of CREATE ROLE
• Using MAKE or ADD which are invalid
• Missing semicolon at the end

3. Given the commands:

CREATE ROLE analyst;
GRANT USAGE ON DATABASE sales_db TO ROLE analyst;
GRANT ROLE analyst TO USER alice;

What permission does user alice have on sales_db?

medium

A. No permissions on sales_db

B. Only USAGE permission on sales_db

C. ALL permissions on sales_db

D. SELECT permission on sales_db

Solution

1. Step 1: Analyze role creation and grants

   The role analyst is created and given USAGE permission on sales_db.

2. Step 2: Check role assignment to user

   User alice is granted the analyst role, so she inherits its permissions.

3. Final Answer:

   Only USAGE permission on sales_db -> Option B

4. Quick Check:

   Role grants USAGE, user inherits USAGE [OK]

Hint: User gets permissions of assigned roles [OK]

Common Mistakes:

• Assuming no permissions without direct grant
• Confusing USAGE with SELECT permission
• Ignoring role inheritance

4. You run this command:

CREATE ROLE analyst

but get an error. What is the likely cause?

medium

A. You must create a user before creating a role

B. Role name analyst is reserved and cannot be used

C. Missing semicolon at the end of the command

D. CREATE ROLE command is not supported in Snowflake

Solution

1. Step 1: Check command syntax

   Snowflake commands require a semicolon at the end to execute properly.

2. Step 2: Evaluate other options

   Role names like analyst are allowed, users are independent of roles, and CREATE ROLE is supported.

3. Final Answer:

   Missing semicolon at the end of the command -> Option C

4. Quick Check:

   Semicolon ends command [OK]

Hint: Always end SQL commands with a semicolon [OK]

Common Mistakes:

• Forgetting semicolon causes syntax error
• Thinking role names are restricted
• Believing users must exist first

5. You want to create a custom role report_viewer that can only read data from the reports schema in the analytics database. Which sequence of commands correctly achieves this?

hard

A. CREATE ROLE report_viewer;
GRANT USAGE ON DATABASE analytics TO ROLE report_viewer;
GRANT USAGE ON SCHEMA analytics.reports TO ROLE report_viewer;
GRANT SELECT ON ALL TABLES IN SCHEMA analytics.reports TO ROLE report_viewer;

B. CREATE ROLE report_viewer;
GRANT SELECT ON DATABASE analytics TO ROLE report_viewer;

C. CREATE ROLE report_viewer;
GRANT ALL ON SCHEMA analytics.reports TO ROLE report_viewer;

D. CREATE ROLE report_viewer;
GRANT USAGE ON DATABASE analytics TO ROLE report_viewer;
GRANT SELECT ON SCHEMA analytics.reports TO ROLE report_viewer;

Solution

1. Step 1: Create the role

   Use CREATE ROLE report_viewer; to make the role.

2. Step 2: Grant USAGE on database and schema

   Granting USAGE on the database and schema allows access to objects inside.

3. Step 3: Grant SELECT on all tables in the schema

   Grant SELECT on all tables to allow read access to data.

4. Step 4: Evaluate options

   CREATE ROLE report_viewer; GRANT USAGE ON DATABASE analytics TO ROLE report_viewer; GRANT USAGE ON SCHEMA analytics.reports TO ROLE report_viewer; GRANT SELECT ON ALL TABLES IN SCHEMA analytics.reports TO ROLE report_viewer; correctly grants USAGE and SELECT at proper levels. CREATE ROLE report_viewer; GRANT SELECT ON DATABASE analytics TO ROLE report_viewer; misses schema and USAGE grants. CREATE ROLE report_viewer; GRANT ALL ON SCHEMA analytics.reports TO ROLE report_viewer; grants ALL which is too broad. CREATE ROLE report_viewer; GRANT USAGE ON DATABASE analytics TO ROLE report_viewer; GRANT SELECT ON SCHEMA analytics.reports TO ROLE report_viewer; grants SELECT on schema which is invalid; SELECT must be on tables.

5. Final Answer:

   CREATE ROLE report_viewer; GRANT USAGE ON DATABASE analytics TO ROLE report_viewer; GRANT USAGE ON SCHEMA analytics.reports TO ROLE report_viewer; GRANT SELECT ON ALL TABLES IN SCHEMA analytics.reports TO ROLE report_viewer; -> Option A

6. Quick Check:

   Grant USAGE + SELECT on tables = read access [OK]

Hint: Grant USAGE on DB/schema, SELECT on tables for read-only role [OK]

Common Mistakes:

• Granting SELECT on schema instead of tables
• Missing USAGE grants on database or schema
• Granting ALL permissions instead of SELECT only