Connection encryption in Apache Airflow - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Airflow Connection Encryption Purpose

Why is connection encryption important in Apache Airflow?

A It protects sensitive connection credentials from being exposed in the Airflow metadata database.

B It speeds up the execution of DAGs by compressing connection data.

C It allows Airflow to connect to external APIs without authentication.

D It automatically retries failed tasks using encrypted channels.

💡 Hint

Think about what sensitive information Airflow stores and why encryption matters.

Airflow stores connection credentials like passwords and tokens in its metadata database. Encrypting these credentials prevents unauthorized users from reading them if they access the database.

❓ Configuration

intermediate

Enabling Connection Encryption in Airflow Configuration

Which configuration setting enables connection encryption in Airflow?

A Set <code>encrypt_connections = True</code> in <code>airflow.cfg</code>.

B Add <code>connection_encryption = enabled</code> in the DAG file.

C Set <code>fernet_key</code> in <code>airflow.cfg</code> under the <code>core</code> section.

D Set <code>enable_ssl = True</code> in the <code>webserver</code> section.

💡 Hint

Look for a key related to encryption in the main Airflow config file.

Airflow uses a fernet_key in airflow.cfg to encrypt and decrypt connection passwords. This key must be set under the [core] section.

💻 Command Output

advanced

Output of Airflow Connections List with Encryption Enabled

What is the output of the command airflow connections list when connection encryption is enabled and passwords are set?

Apache Airflow

airflow connections list

A The passwords are shown as encrypted strings (e.g., <code>gAAAAAB...</code>).

B Passwords are replaced with <code>***</code> and not shown.

C The command fails with a decryption error.

D The passwords are shown in plain text.

💡 Hint

Think about how Airflow stores and displays encrypted passwords.

When encryption is enabled, Airflow stores passwords encrypted but decrypts them when displaying. However, the CLI shows the encrypted string to avoid exposing plain text.

❓ Troubleshoot

advanced

Troubleshooting Connection Decryption Failures

You enabled connection encryption by setting a new fernet_key but now Airflow fails to decrypt existing connection passwords. What is the cause?

A The database connection string is incorrect.

B The Airflow version does not support encryption.

C The <code>airflow.cfg</code> file is missing the <code>executor</code> setting.

D The new <code>fernet_key</code> does not match the key used to encrypt existing passwords.

💡 Hint

Think about how encryption keys work for decrypting data.

If you change the fernet_key, Airflow cannot decrypt passwords encrypted with the old key. The key must remain consistent to decrypt existing data.

✅ Best Practice

expert

Best Practice for Managing Airflow Fernet Keys

What is the best practice for managing the fernet_key used for connection encryption in Airflow?

A Generate a new <code>fernet_key</code> every time Airflow starts to maximize security.

B Store the <code>fernet_key</code> securely outside the codebase and rotate it carefully without losing access to encrypted data.

C Hardcode the <code>fernet_key</code> in DAG files for easy access.

D Disable encryption and rely on database user permissions instead.

💡 Hint

Consider security and data availability when handling encryption keys.

The fernet_key must be stored securely and rotated carefully. Losing the key means losing access to encrypted connection passwords. Generating a new key every start or hardcoding it in DAGs is insecure or impractical.