System-defined roles (ACCOUNTADMIN, SYSADMIN, etc.) in Snowflake - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Role Privilege Scope Understanding

Which system-defined role in Snowflake has the highest level of privileges, including the ability to manage all other roles and account-level settings?

A SECURITYADMIN

B ACCOUNTADMIN

C SYSADMIN

D PUBLIC

💡 Hint

Think about the role that controls the entire account and can assign other roles.

The ACCOUNTADMIN role has the highest privileges in Snowflake. It can manage all other roles, users, and account-level settings. Other roles have more limited scopes.

❓ service_behavior

intermediate

Role Behavior on Object Ownership

If a user with the SYSADMIN role creates a new database, who becomes the owner of that database by default?

A The ACCOUNTADMIN role

B The PUBLIC role

C The SYSADMIN role

D The SECURITYADMIN role

💡 Hint

Ownership is assigned to the role that performs the creation.

When a user with the SYSADMIN role creates a database, the SYSADMIN role becomes the owner of that database by default.

❓ security

advanced

Role Hierarchy and Privilege Delegation

Which system-defined role is primarily responsible for managing role grants and user access control in Snowflake?

A PUBLIC

B ACCOUNTADMIN

C SYSADMIN

D SECURITYADMIN

💡 Hint

This role handles security-related tasks like granting roles and privileges.

The SECURITYADMIN role manages role grants and user access control, including creating users and assigning roles.

✅ Best Practice

advanced

Least Privilege Principle Application

To follow the least privilege principle, which role should be assigned to a user who only needs to create and manage warehouses but not manage users or roles?

A SYSADMIN

B SECURITYADMIN

C ACCOUNTADMIN

D PUBLIC

💡 Hint

Consider the role that manages compute resources but not security.

The SYSADMIN role is appropriate for managing warehouses and other objects without access to user or role management, aligning with least privilege.

❓ Architecture

expert

Role Usage in Multi-Account Architecture

In a Snowflake multi-account setup, which role should be used to centrally manage security policies and user access across all accounts?

A SECURITYADMIN role in each account coordinated centrally

B A custom role with SYSADMIN privileges

C ACCOUNTADMIN in each account separately

D PUBLIC role with elevated privileges

💡 Hint

Think about a role designed for security management that can be used consistently across accounts.

The SECURITYADMIN role is designed to manage security policies and user access. In multi-account setups, using SECURITYADMIN in each account coordinated centrally is best practice.

Practice

1. Which Snowflake system-defined role has full control over the entire account, including all objects and users?

easy

A. ACCOUNTADMIN

B. SYSADMIN

C. SECURITYADMIN

D. PUBLIC

Solution

1. Step 1: Understand role privileges

   ACCOUNTADMIN is designed to have full control over the Snowflake account, including all objects and user management.

2. Step 2: Compare with other roles

   SYSADMIN manages data objects, SECURITYADMIN manages users and roles, and PUBLIC has minimal default privileges.

3. Final Answer:

   ACCOUNTADMIN -> Option A

4. Quick Check:

   Full account control = ACCOUNTADMIN [OK]

Hint: Full control role is ACCOUNTADMIN, others have limited scopes [OK]

Common Mistakes:

• Confusing SYSADMIN with full control
• Thinking SECURITYADMIN manages data objects
• Assuming PUBLIC has admin privileges

2. Which of the following is the correct syntax to switch to the SYSADMIN role in Snowflake?

easy

A. SET ROLE SYSADMIN;

B. CHANGE ROLE TO SYSADMIN;

C. USE ROLE SYSADMIN;

D. SWITCH TO SYSADMIN;

Solution

1. Step 1: Recall Snowflake role switching syntax

   The correct command to switch roles is USE ROLE <role_name>;.

2. Step 2: Verify options

   Only USE ROLE SYSADMIN; matches the correct syntax exactly.

3. Final Answer:

   USE ROLE SYSADMIN; -> Option C

4. Quick Check:

   Switch role command = USE ROLE [OK]

Hint: Switch roles with USE ROLE followed by role name [OK]

Common Mistakes:

• Using SET ROLE instead of USE ROLE
• Adding extra words like TO or SWITCH
• Missing semicolon at the end

3. Given the following commands executed in order:

USE ROLE SECURITYADMIN;
CREATE USER test_user PASSWORD='Pass1234';
USE ROLE SYSADMIN;
CREATE TABLE test_table(id INT);

Which statement is true about the created objects?

medium

A. test_user is created successfully; test_table creation fails due to insufficient privileges.

B. Both test_user and test_table creation fail.

C. test_user creation fails; test_table is created successfully.

D. Both test_user and test_table are created successfully.

Solution

1. Step 1: Analyze role privileges for user creation

   SECURITYADMIN can create users, so CREATE USER test_user succeeds.

2. Step 2: Analyze role privileges for table creation

   SYSADMIN manages data objects, so CREATE TABLE test_table succeeds.

3. Final Answer:

   Both test_user and test_table are created successfully. -> Option D

4. Quick Check:

   SECURITYADMIN creates users, SYSADMIN creates tables [OK]

Hint: SECURITYADMIN for users, SYSADMIN for tables; both succeed [OK]

Common Mistakes:

• Assuming SYSADMIN can create users
• Assuming SECURITYADMIN can create tables
• Confusing role privileges

4. You run the command CREATE USER new_user PASSWORD='abc123'; while using the SYSADMIN role and get an error. What is the most likely cause?

medium

A. Password does not meet complexity requirements.

B. SYSADMIN role does not have privileges to create users.

C. The command syntax is incorrect.

D. The user already exists.

Solution

1. Step 1: Check role privileges for user creation

   Only SECURITYADMIN or ACCOUNTADMIN can create users; SYSADMIN lacks this privilege.

2. Step 2: Consider other options

   Password complexity or syntax errors would cause different error messages; user existence would be a different error.

3. Final Answer:

   SYSADMIN role does not have privileges to create users. -> Option B

4. Quick Check:

   User creation requires SECURITYADMIN or ACCOUNTADMIN [OK]

Hint: User creation needs SECURITYADMIN, not SYSADMIN [OK]

Common Mistakes:

• Blaming password complexity without checking error
• Assuming SYSADMIN can create users
• Ignoring role privilege boundaries

5. You want to delegate user and role management to one admin and data object management to another, while keeping full control yourself. Which role assignments follow best practices?

hard

A. Assign SECURITYADMIN to user1, SYSADMIN to user2, ACCOUNTADMIN to yourself.

B. Assign ACCOUNTADMIN to user1, SECURITYADMIN to user2, SYSADMIN to yourself.

C. Assign SYSADMIN to user1, ACCOUNTADMIN to user2, SECURITYADMIN to yourself.

D. Assign PUBLIC to user1, SYSADMIN to user2, SECURITYADMIN to yourself.

Solution

1. Step 1: Understand role responsibilities

   SECURITYADMIN manages users and roles; SYSADMIN manages data objects; ACCOUNTADMIN has full control.

2. Step 2: Match roles to admin tasks

   Assign SECURITYADMIN to the admin handling users, SYSADMIN to the admin handling data, and keep ACCOUNTADMIN yourself for full control.

3. Final Answer:

   Assign SECURITYADMIN to user1, SYSADMIN to user2, ACCOUNTADMIN to yourself. -> Option A

4. Quick Check:

   Delegate roles by responsibility, keep ACCOUNTADMIN for full control [OK]

Hint: Delegate SECURITYADMIN for users, SYSADMIN for data, keep ACCOUNTADMIN [OK]

Common Mistakes:

• Giving ACCOUNTADMIN to others unnecessarily
• Assigning PUBLIC role for admin tasks
• Mixing up role responsibilities