Why access control protects sensitive pipelines in Apache Airflow - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the Airflow role that allows viewing DAGs but not editing them.

Apache Airflow

role = BaseRole(name='Viewer', permissions=[1])

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

A['can_read']

B['can_edit']

C['can_delete']

D['can_create']

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'can_edit' or 'can_delete' instead of 'can_read'.

The 'Viewer' role should have 'can_read' permission to view DAGs without editing rights.

2fill in blank

medium

Complete the code to assign the 'Admin' role to a user in Airflow.

Apache Airflow

user.roles.append([1])

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

A'Operator'

B'Admin'

C'Viewer'

D'User'

Attempts:

3 left

💡 Hint

Common Mistakes

Assigning 'Viewer' or 'Operator' instead of 'Admin'.

Assigning the 'Admin' role gives the user full access to manage pipelines.

3fill in blank

hard

Fix the error in the code to restrict DAG access to only authorized users.

Apache Airflow

dag = DAG('sensitive_data', access_control=[1])

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

A{'User': {'can_read'}}

B['Admin', 'User']

CNone

D{'Admin': {'can_read', 'can_edit'}}

Attempts:

3 left

💡 Hint

Common Mistakes

Using a list instead of a dictionary for access_control.

Access control must be a dictionary mapping roles to permission sets, like {'Admin': {'can_read', 'can_edit'}}.

4fill in blank

hard

Fill both blanks to create a policy that allows only Admins to trigger DAG runs and view logs.

Apache Airflow

access_policy = [1]: {'can_trigger_dag', [2]

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

A'Admin'

B'can_view_logs'

C'User'

D'can_edit'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'User' role or wrong permission names.

The policy grants 'Admin' role permissions to 'can_trigger_dag' and 'can_view_logs'.

5fill in blank

hard

Fill all three blanks to define a secure DAG with restricted access and schedule.

Apache Airflow

dag = DAG('[1]', schedule_interval=[2], access_control=[3])

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

A'secure_pipeline'

B'@daily'

C{'Admin': {'can_read', 'can_edit'}}

D'@hourly'

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong schedule strings or access control formats.

The DAG named 'secure_pipeline' runs daily and restricts access to Admins with read and edit permissions.

Practice

1. Why is access control important in Apache Airflow pipelines?

easy

A. It allows anyone to edit pipelines without restrictions.

B. It speeds up the execution of pipelines automatically.

C. It prevents unauthorized users from changing or viewing sensitive workflows.

D. It deletes old pipeline logs to save space.

Solution

1. Step 1: Understand the purpose of access control

   Access control limits who can see or change pipelines, protecting sensitive data.

2. Step 2: Identify the correct benefit

   Preventing unauthorized changes keeps pipelines safe and reliable.

3. Final Answer:

   It prevents unauthorized users from changing or viewing sensitive workflows. -> Option C

4. Quick Check:

   Access control protects pipelines = A [OK]

Hint: Access control means only allowed users can change pipelines [OK]

Common Mistakes:

• Thinking access control speeds up pipelines
• Believing anyone can edit pipelines safely
• Confusing access control with log management

2. Which Airflow role should be assigned to users who only need to view pipelines but not edit them?

easy

A. Viewer

B. Admin

C. Operator

D. Developer

Solution

1. Step 1: Review Airflow role definitions

   The Viewer role allows users to see pipelines without editing rights.

2. Step 2: Match role to permission needs

   Users who only need to view should not have Admin or Developer roles.

3. Final Answer:

   Viewer -> Option A

4. Quick Check:

   View-only role = Viewer [OK]

Hint: Viewer role means read-only access to pipelines [OK]

Common Mistakes:

• Assigning Admin role to view-only users
• Confusing Operator with Viewer
• Thinking Developer role is for viewing only

3. Given this Airflow access control snippet, what will happen if a user without Admin role tries to edit a pipeline?

roles = {
  "Admin": ["can_edit", "can_view"],
  "Viewer": ["can_view"]
}
user_role = "Viewer"
if "can_edit" in roles[user_role]:
    print("Edit allowed")
else:
    print("Edit denied")

medium

A. Edit allowed

B. Edit denied

C. KeyError because role missing

D. No output

Solution

1. Step 1: Check user role permissions

   The Viewer role only has "can_view", not "can_edit" permission.

2. Step 2: Evaluate the if condition

   Since "can_edit" is not in roles["Viewer"], the else branch runs.

3. Final Answer:

   Edit denied -> Option B

4. Quick Check:

   Viewer lacks edit permission = Edit denied [OK]

Hint: Check if user role includes 'can_edit' permission [OK]

Common Mistakes:

• Assuming Viewer can edit pipelines
• Expecting a KeyError for existing roles
• Ignoring else branch output

4. You set up access control but users report they can still edit sensitive pipelines. What is the most likely cause?

medium

A. Users are using the Viewer role.

B. Airflow scheduler is not running.

C. Pipeline code has syntax errors.

D. Users have Admin role assigned accidentally.

Solution

1. Step 1: Analyze user permissions

   If users can edit, they likely have a role with edit rights, such as Admin.

2. Step 2: Rule out unrelated issues

   Scheduler or syntax errors do not affect access control permissions.

3. Final Answer:

   Users have Admin role assigned accidentally. -> Option D

4. Quick Check:

   Editing despite control = Admin role assigned [OK]

Hint: Check user roles if access control fails [OK]

Common Mistakes:

• Blaming scheduler for permission issues
• Assuming syntax errors cause access problems
• Thinking Viewer role allows editing

5. You want to protect sensitive pipeline variables in Airflow. Which combined approach best secures these variables?

hard

A. Store sensitive data in Airflow variables and restrict access using roles like Admin and Viewer.

B. Use Airflow variables with no access control and share passwords openly.

C. Disable all roles and let everyone access variables freely.

D. Keep sensitive data only in pipeline code without variables.

Solution

1. Step 1: Understand variable security

   Storing sensitive data in Airflow variables is common but risky without access control.

2. Step 2: Combine variables with role-based access

   Restricting variable access by roles like Admin and Viewer protects sensitive info.

3. Final Answer:

   Store sensitive data in Airflow variables and restrict access using roles like Admin and Viewer. -> Option A

4. Quick Check:

   Variables + roles = secure sensitive data [OK]

Hint: Combine variables with role restrictions for safety [OK]

Common Mistakes:

• Sharing passwords without access control
• Disabling roles causing open access
• Hardcoding sensitive data in code