Role-based access control (RBAC) in Apache Airflow - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable RBAC in Airflow configuration.

Apache Airflow

rbac = [1]

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

ATrue

BNone

CFalse

DAuto

Attempts:

3 left

💡 Hint

Common Mistakes

Setting rbac to False disables RBAC.

Using None or Auto are invalid values for this setting.

Setting rbac = True in the Airflow configuration enables Role-Based Access Control.

2fill in blank

medium

Complete the command to create a new role named 'data_engineer' in Airflow CLI.

Apache Airflow

airflow roles create [1]

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

Auser

Bdata_engineer

Cviewer

Dadmin

Attempts:

3 left

💡 Hint

Common Mistakes

Using existing role names like admin or viewer instead of the new role.

Misspelling the role name.

The command airflow roles create data_engineer creates a new role named 'data_engineer'.

3fill in blank

hard

Fix the error in the command to assign the 'Viewer' role to user 'alice'.

Apache Airflow

airflow users add-role --username alice --role [1]

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

AViewer

BAdmin

Cviewer

Duser

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase role names causes errors.

Using a role name that does not exist.

The role name is case-sensitive and should be 'Viewer' when assigning roles via CLI.

4fill in blank

hard

Fill both blanks to create a user 'bob' with email '[e-mail]' and assign the 'Admin' role.

Apache Airflow

airflow users create --username [1] --email [2] --role Admin --password secret

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

Abob

[e-mail]

[e-mail]

Dadmin

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up username and email values.

Using incorrect email format.

The username is 'bob' and the email is '[e-mail]' to create the user correctly.

5fill in blank

hard

Fill all three blanks to list all roles, filter by name containing 'Admin', and sort by name descending.

Apache Airflow

airflow roles list | grep [1] | sort [2] [3]

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

AAdmin

B-r

C-k

D-n

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong grep keyword.

Using sort options in wrong order or wrong flags.

Use grep Admin to filter roles containing 'Admin', then sort -n -r to sort numerically in descending order.

Practice

1. What is the main purpose of Role-Based Access Control (RBAC) in Apache Airflow?

easy

A. To assign users specific roles that define their permissions

B. To schedule DAG runs automatically

C. To monitor system resource usage

D. To create new DAGs from templates

Solution

1. Step 1: Understand RBAC concept

   RBAC is about controlling who can do what by assigning roles with permissions.

2. Step 2: Identify RBAC purpose in Airflow

   In Airflow, RBAC assigns roles to users to control access to features and data.

3. Final Answer:

   To assign users specific roles that define their permissions -> Option A

4. Quick Check:

   RBAC = Assign roles with permissions [OK]

Hint: RBAC means roles control user permissions [OK]

Common Mistakes:

• Confusing RBAC with scheduling tasks
• Thinking RBAC monitors system resources
• Believing RBAC creates DAGs

2. Which Airflow CLI command correctly creates a user with the role 'Admin'?

easy

A. airflow users create --username alice --role Admin --email [e-mail]

B. airflow create user --name alice --role Admin

C. airflow user add --username alice --role Admin

D. airflow users add --user alice --role Admin

Solution

1. Step 1: Recall correct CLI syntax for user creation

   The correct command uses 'airflow users create' with flags for username, role, and email.

2. Step 2: Match options to syntax

   airflow users create --username alice --role Admin --email [e-mail] matches the correct syntax exactly; others have wrong commands or flags.

3. Final Answer:

   airflow users create --username alice --role Admin --email [e-mail] -> Option A

4. Quick Check:

   Correct CLI syntax = airflow users create --username alice --role Admin --email [e-mail] [OK]

Hint: Use 'airflow users create' with proper flags [OK]

Common Mistakes:

• Using 'create user' instead of 'users create'
• Missing required flags like --email
• Using incorrect command verbs like 'add'

3. Given this Airflow RBAC role assignment command, what will be the user's role?

airflow users create --username bob --role Viewer --email [e-mail]

medium

A. User

B. Admin

C. Viewer

D. Operator

Solution

1. Step 1: Read the command carefully

   The command assigns the role 'Viewer' to user 'bob'.

2. Step 2: Identify the assigned role

   The role specified with --role is 'Viewer', so that is the user's role.

3. Final Answer:

   Viewer -> Option C

4. Quick Check:

   Role assigned = Viewer [OK]

Hint: Look for --role flag value in command [OK]

Common Mistakes:

• Assuming default role instead of specified
• Confusing username with role
• Choosing a role not in the command

4. You run this command but get an error:

airflow users create --username carol --role Admin

What is the most likely cause?

medium

A. Username 'carol' already exists

B. Role 'Admin' does not exist

C. Incorrect command 'users create'

D. Missing required --email flag

Solution

1. Step 1: Check required flags for user creation

   The 'airflow users create' command requires --email flag along with username and role.

2. Step 2: Identify missing flag causing error

   The command lacks --email, so it triggers an error for missing required argument.

3. Final Answer:

   Missing required --email flag -> Option D

4. Quick Check:

   Required flags missing = Missing required --email flag [OK]

Hint: Always include --email when creating users [OK]

Common Mistakes:

• Ignoring required flags
• Assuming role names cause error
• Thinking command syntax is wrong

5. You want to restrict a user to only view DAGs but not edit or trigger them. Which role should you assign in Airflow RBAC to achieve this?

hard

A. Admin

B. Viewer

C. User

D. Op

Solution

1. Step 1: Understand role permissions in Airflow

   'Admin' has full access, 'User' and 'Op' have more permissions than just viewing.

2. Step 2: Identify role for view-only access

   'Viewer' role is designed to allow users to see DAGs without editing or triggering them.

3. Final Answer:

   Viewer -> Option B

4. Quick Check:

   View-only access = Viewer role [OK]

Hint: Use 'Viewer' role for read-only DAG access [OK]

Common Mistakes:

• Assigning Admin role for limited access
• Confusing 'User' or 'Op' with view-only
• Not knowing role permission differences