Role creation and management in PostgreSQL - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

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

PostgreSQL

CREATE ROLE [1];

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

Aadmin

Breporter

Cuser

Dguest

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting to specify the role name.

Using reserved keywords as role names.

The CREATE ROLE command followed by the role name creates a new role. Here, 'reporter' is the new role.

2fill in blank

medium

Complete the code to grant login permission to the role 'reporter'.

PostgreSQL

ALTER ROLE reporter [1] LOGIN;

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

AGRANT

BNO

CWITH

DDENY

Attempts:

3 left

💡 Hint

Common Mistakes

Using NO LOGIN which disables login.

Omitting the WITH keyword.

To allow a role to login, use ALTER ROLE role_name WITH LOGIN;. The keyword WITH is required before LOGIN.

3fill in blank

hard

Fix the error in the code to revoke SELECT privilege on table 'sales' from role 'reporter'.

PostgreSQL

REVOKE [1] ON sales FROM reporter;

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

AINSERT

BUPDATE

CDELETE

DSELECT

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong privilege like INSERT instead of SELECT.

Misspelling the privilege name.

The REVOKE command removes privileges. To revoke the ability to read data, use SELECT.

4fill in blank

hard

Fill both blanks to grant SELECT and INSERT privileges on table 'employees' to role 'hr'.

PostgreSQL

GRANT [1], [2] ON employees TO hr;

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

ASELECT

BDELETE

CINSERT

DUPDATE

Attempts:

3 left

💡 Hint

Common Mistakes

Granting wrong privileges like DELETE or UPDATE.

Mixing up privilege names.

To allow reading and adding data, grant SELECT and INSERT privileges.

5fill in blank

hard

Fill all three blanks to create a role 'manager' with login, password 'secure123', and superuser privileges.

PostgreSQL

CREATE ROLE [1] WITH [2] PASSWORD '[3]' SUPERUSER;

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

Amanager

BLOGIN

Csecure123

DNOSUPERUSER

Attempts:

3 left

💡 Hint

Common Mistakes

Using NOSUPERUSER which denies superuser rights.

Forgetting to put the password in quotes.

This command creates a role named 'manager' that can login with password 'secure123' and has superuser rights.

Practice

1. What is the primary purpose of a role in PostgreSQL?

easy

A. To control access and permissions for users and groups

B. To store data in tables

C. To create backups of the database

D. To optimize query performance

Solution

1. Step 1: Understand the concept of roles

   Roles in PostgreSQL are used to manage who can access the database and what they can do.

2. Step 2: Identify the main function of roles

   Roles control permissions and access rights, not data storage or backups.

3. Final Answer:

   To control access and permissions for users and groups -> Option A

4. Quick Check:

   Roles = Access control [OK]

Hint: Roles manage user permissions and access rights [OK]

Common Mistakes:

• Confusing roles with tables or data storage
• Thinking roles handle backups
• Assuming roles optimize queries

2. Which of the following is the correct syntax to create a role with login permission in PostgreSQL?

easy

A. CREATE ROLE user1 WITH LOGIN;

B. CREATE ROLE user1 CAN LOGIN;

C. CREATE ROLE user1 LOGIN;

D. CREATE ROLE user1 ALLOW LOGIN;

Solution

1. Step 1: Recall the syntax for creating a role with login

   The correct syntax uses WITH LOGIN to allow the role to log in.

2. Step 2: Check each option

   CREATE ROLE user1 WITH LOGIN; uses 'WITH LOGIN' which is correct. Others use incorrect keywords.

3. Final Answer:

   CREATE ROLE user1 WITH LOGIN; -> Option A

4. Quick Check:

   WITH LOGIN = enable login [OK]

Hint: Use WITH LOGIN to grant login rights when creating roles [OK]

Common Mistakes:

• Omitting WITH before LOGIN
• Using CAN or ALLOW instead of WITH
• Forgetting semicolon at end

3. Given the commands:

CREATE ROLE analyst NOLOGIN;
ALTER ROLE analyst CREATEDB;

What is true about the role analyst?

medium

A. The role can log in but cannot create databases

B. The role can log in and create databases

C. The role cannot log in but can create databases

D. The role cannot log in and cannot create databases

Solution

1. Step 1: Analyze the CREATE ROLE command

   The role 'analyst' is created with NOLOGIN, so it cannot log in.

2. Step 2: Analyze the ALTER ROLE command

   The role is altered to have CREATEDB permission, so it can create databases.

3. Final Answer:

   The role cannot log in but can create databases -> Option C

4. Quick Check:

   NOLOGIN + CREATEDB = no login, can create DB [OK]

Hint: NOLOGIN disables login; CREATEDB allows database creation [OK]

Common Mistakes:

• Assuming NOLOGIN means role cannot do anything
• Confusing CREATEDB with login permission
• Ignoring ALTER ROLE effects

4. Identify the error in the following command:

CREATE ROLE manager LOGIN PASSWORD 'secret';

medium

A. PASSWORD must be set using ENCRYPTED keyword

B. LOGIN cannot be used with PASSWORD

C. PASSWORD should be set with USING keyword

D. PASSWORD must be set using WITH keyword

Solution

1. Step 1: Check correct syntax for setting password

   In PostgreSQL, options like PASSWORD must be specified after WITH keyword.

2. Step 2: Identify the error in the command

   The command misses WITH before PASSWORD, causing syntax error.

3. Final Answer:

   PASSWORD must be set using WITH keyword -> Option D

4. Quick Check:

   Use WITH before PASSWORD [OK]

Hint: Use WITH before PASSWORD when creating roles [OK]

Common Mistakes:

• Omitting WITH before PASSWORD
• Thinking LOGIN disallows PASSWORD
• Using ENCRYPTED incorrectly

5. You want to create a role named developer that can log in, create databases, and also inherit permissions from another role team_member. Which command correctly achieves this?

hard

A. CREATE ROLE developer WITH LOGIN CREATEDB INHERIT team_member;

B. CREATE ROLE developer WITH LOGIN CREATEDB INHERIT; GRANT team_member TO developer;

C. CREATE ROLE developer WITH LOGIN CREATEDB INHERIT; ALTER ROLE developer IN ROLE team_member;

D. CREATE ROLE developer WITH LOGIN CREATEDB INHERIT; GRANT developer TO team_member;

Solution

1. Step 1: Create role with login, createdb, and inherit

   The role must be created with WITH LOGIN, CREATEDB, and INHERIT options.

2. Step 2: Grant membership to inherit permissions

   To inherit permissions from team_member, grant team_member role to developer using GRANT.

3. Step 3: Check each option

   CREATE ROLE developer WITH LOGIN CREATEDB INHERIT; GRANT team_member TO developer; correctly creates the role and grants team_member to developer. Others misuse syntax or reverse grant direction.

4. Final Answer:

   CREATE ROLE developer WITH LOGIN CREATEDB INHERIT; GRANT team_member TO developer; -> Option B

5. Quick Check:

   GRANT role TO user for inheritance [OK]

Hint: Use GRANT role TO user to inherit permissions [OK]

Common Mistakes:

• Putting role name after INHERIT
• Reversing GRANT direction
• Missing WITH keyword or semicolon