Role-based access in MySQL - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new role named 'manager'.

MySQL

CREATE ROLE [1];

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

Aadmin

Bmanager

Cguest

Duser

Attempts:

3 left

💡 Hint

Common Mistakes

Using a role name that is not intended, like 'admin' or 'guest'.

Forgetting to use CREATE ROLE before the role name.

The CREATE ROLE statement creates a new role. Here, 'manager' is the role name.

2fill in blank

medium

Complete the code to grant SELECT permission on the 'employees' table to the 'manager' role.

MySQL

GRANT [1] ON employees TO manager;

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

ADELETE

BINSERT

CSELECT

DUPDATE

Attempts:

3 left

💡 Hint

Common Mistakes

Granting INSERT or UPDATE instead of SELECT.

Forgetting to specify the table name.

The GRANT SELECT statement gives read-only access to the 'employees' table for the 'manager' role.

3fill in blank

hard

Fix the error in the code to assign the 'manager' role to user 'alice'.

MySQL

GRANT [1] TO 'alice'@'localhost';

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

Amanager

BROLE

CUSER

DROLE manager

Attempts:

3 left

💡 Hint

Common Mistakes

Using the keyword ROLE before the role name.

Using USER instead of the role name.

To assign a role, you grant the role name directly to the user. The correct syntax is GRANT manager TO 'alice'@'localhost';

4fill in blank

hard

Fill both blanks to revoke the UPDATE permission on 'projects' table from the 'developer' role.

MySQL

REVOKE [1] ON projects FROM [2];

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

AUPDATE

BSELECT

Cdeveloper

Dmanager

Attempts:

3 left

💡 Hint

Common Mistakes

Revoking SELECT instead of UPDATE.

Revoking from the wrong role like 'manager'.

The REVOKE UPDATE ON projects FROM developer; statement removes the update permission from the developer role on the projects table.

5fill in blank

hard

Fill all three blanks to create a user 'bob', assign the 'analyst' role, and grant SELECT on 'reports' table.

MySQL

CREATE USER '[1]'@'localhost';
GRANT [2] TO '[3]'@'localhost';
GRANT SELECT ON reports TO '[3]'@'localhost';

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

Abob

Banalyst

Attempts:

3 left

💡 Hint

Common Mistakes

Using different usernames in different lines.

Forgetting to grant the role before table permissions.

This sequence creates the user 'bob', grants the 'analyst' role to him, and then grants SELECT permission on the 'reports' table.

Practice

1. What is the main purpose of role-based access control (RBAC) in MySQL?

easy

A. To store user passwords securely

B. To group permissions into roles and assign them to users

C. To optimize query performance

D. To backup the database automatically

Solution

1. Step 1: Understand role-based access control concept

   RBAC groups permissions into roles instead of assigning them individually to users.

2. Step 2: Identify the main purpose in MySQL context

   Assigning roles to users simplifies permission management and improves security.

3. Final Answer:

   To group permissions into roles and assign them to users -> Option B

4. Quick Check:

   RBAC = Group permissions + assign roles [OK]

Hint: RBAC groups permissions, then assigns roles to users [OK]

Common Mistakes:

• Confusing RBAC with password storage
• Thinking RBAC improves query speed
• Assuming RBAC is for backups

2. Which of the following is the correct syntax to create a role named manager in MySQL?

easy

A. CREATE ROLE manager;

B. MAKE ROLE manager;

C. ADD ROLE manager;

D. NEW ROLE manager;

Solution

1. Step 1: Recall MySQL syntax for creating roles

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

2. Step 2: Match syntax with options

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

3. Final Answer:

   CREATE ROLE manager; -> Option A

4. Quick Check:

   CREATE ROLE = create new role [OK]

Hint: Use CREATE ROLE to make a new role in MySQL [OK]

Common Mistakes:

• Using MAKE ROLE instead of CREATE ROLE
• Using ADD ROLE which is invalid
• Using NEW ROLE which is not a MySQL command

3. Given the following commands:

CREATE ROLE analyst;
GRANT SELECT ON sales TO analyst;
GRANT analyst TO alice;

What permission does user alice have on the sales table?

medium

A. SELECT permission on sales

B. INSERT permission on sales

C. No permissions on sales

D. ALL permissions on sales

Solution

1. Step 1: Analyze role creation and permission grant

   The role analyst is created and given SELECT permission on the sales table.

2. Step 2: Check user role assignment

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

3. Final Answer:

   SELECT permission on sales -> Option A

4. Quick Check:

   User with role gets role's permissions [OK]

Hint: User inherits permissions from assigned roles [OK]

Common Mistakes:

• Assuming user gets INSERT without grant
• Thinking user has no permissions without direct grant
• Assuming ALL permissions without explicit grant

4. Consider this MySQL command:

GRANT SELECT ON employees TO 'john';

Why might this command fail when using role-based access?

medium

A. Because 'john' is not a valid username format

B. Because SELECT is not a valid permission

C. Because GRANT cannot be used on tables

D. Because permissions should be granted to roles, not directly to users

Solution

1. Step 1: Understand role-based access best practice

   In RBAC, permissions are granted to roles, then roles are assigned to users.

2. Step 2: Identify why direct grant to user may fail

   Granting permissions directly to users bypasses roles and may be restricted or discouraged.

3. Final Answer:

   Because permissions should be granted to roles, not directly to users -> Option D

4. Quick Check:

   Grant permissions to roles, assign roles to users [OK]

Hint: Grant permissions to roles, not users directly [OK]

Common Mistakes:

• Thinking SELECT is invalid permission
• Assuming username format is wrong
• Believing GRANT can't be used on tables

5. You want to create a role developer with INSERT and UPDATE permissions on the projects table, then assign it to user emma. Which sequence of commands correctly achieves this?

hard

A. CREATE ROLE developer; GRANT SELECT ON projects TO developer; GRANT developer TO emma;

B. GRANT INSERT, UPDATE ON projects TO emma; CREATE ROLE developer; GRANT developer TO emma;

C. CREATE ROLE developer; GRANT INSERT, UPDATE ON projects TO developer; GRANT developer TO emma;

D. CREATE USER developer; GRANT INSERT, UPDATE ON projects TO developer; GRANT developer TO emma;

Solution

1. Step 1: Create the role named developer

   Use CREATE ROLE developer; to define the role.

2. Step 2: Grant INSERT and UPDATE permissions on projects to the role

   Use GRANT INSERT, UPDATE ON projects TO developer; to assign permissions.

3. Step 3: Assign the role to user emma

   Use GRANT developer TO emma; to give emma the role's permissions.

4. Final Answer:

   CREATE ROLE developer; GRANT INSERT, UPDATE ON projects TO developer; GRANT developer TO emma; -> Option C

5. Quick Check:

   Create role, grant permissions, assign role [OK]

Hint: Create role, grant permissions, then assign role to user [OK]

Common Mistakes:

• Granting permissions directly to user instead of role
• Using CREATE USER instead of CREATE ROLE
• Granting wrong permissions like SELECT instead of INSERT, UPDATE