Which of the following best explains why access control is critical for sensitive Airflow pipelines?
Think about what could happen if anyone could change or see sensitive pipeline details.
Access control restricts who can see or change pipelines. This protects sensitive data and prevents accidental or malicious changes that could break workflows.
What is the output of running the command airflow users list when RBAC is enabled and there are two users: admin and viewer?
airflow users listRBAC lists users with their roles and emails.
The airflow users list command shows all users with their roles when RBAC is enabled. The roles determine access levels.
Which configuration snippet correctly restricts access to a DAG named finance_report only to users with the finance_team role?
Look for the correct section and syntax to map DAGs to roles.
The [dag_access_control] section maps DAG IDs to roles allowed to access them. RBAC must be enabled.
A user with the role data_analyst tries to access the DAG sales_data but gets an 'Unauthorized' error. What is the most likely cause?
Think about role permissions related to DAG access.
If a userβs role is not mapped to a DAG in access control, they cannot view or trigger it, causing an 'Unauthorized' error.
Which of the following is the best practice to protect sensitive Airflow pipelines from unauthorized access and accidental changes?
Consider security principles of least privilege and controlled access.
Enabling RBAC with minimal roles and DAG-level access control limits who can see or change sensitive pipelines, reducing risk of leaks or errors.