What is the main purpose of enabling audit logging in Apache Airflow?
Think about why organizations need to keep records of who did what and when.
Audit logging records user actions and system changes, helping with security audits and compliance. It does not affect execution speed or retry logic.
What is the expected output or effect after setting audit_logging = True in the Airflow configuration file airflow.cfg and restarting the scheduler?
[logging]
audit_logging = TrueEnabling audit logging should add extra logging, not remove or break existing features.
Setting audit_logging = True enables detailed logging of user actions and system changes, which are saved in audit logs. It does not disable other logs or cause errors.
Which configuration snippet correctly sets up Airflow audit logging to output logs in JSON format for easier parsing?
Audit logging must be enabled and the format set to 'json' exactly.
To output audit logs in JSON, audit_logging must be true and audit_log_format set to 'json'. Other formats or disabling audit logging will not produce JSON logs.
You enabled audit logging in Airflow but notice no audit logs are being generated. Which of the following is the most likely cause?
Think about what could prevent logs from being saved even if logging is enabled.
If the Airflow process cannot write to the audit log directory due to permissions, no audit logs will be created. DAG scheduling or webserver status does not directly affect audit log creation.
Which sequence correctly describes the workflow for using Airflow audit logs to investigate a suspicious DAG modification?
Think about the logical order from setup to investigation to action.
The correct workflow starts with enabling audit logging, then locating logs, searching for events, and finally reviewing and acting on findings.