Connection management for cloud services in Apache Airflow - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a connection in Airflow using the CLI.

Apache Airflow

airflow connections add my_gcp_conn --conn-type [1] --conn-extra '{"extra__google_cloud_platform__project": "my-project"}'

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

Agoogle_cloud_platform

Bmysql

Chttp

Daws

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'aws' instead of 'google_cloud_platform' for a GCP connection.

Using 'http' which is for web connections, not cloud services.

The connection type for Google Cloud Platform in Airflow is google_cloud_platform. This tells Airflow how to handle the connection.

2fill in blank

medium

Complete the code to retrieve a connection object in an Airflow DAG.

Apache Airflow

from airflow.hooks.base_hook import BaseHook
conn = BaseHook.get_connection([1])

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

A'my_gcp_conn'

B'my_aws_conn'

C'http_conn'

D'db_conn'

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the connection ID without quotes, causing a NameError.

Using a different connection ID than the one created.

You need to pass the connection ID as a string to get_connection. Here, 'my_gcp_conn' matches the connection you want to retrieve.

3fill in blank

hard

Fix the error in the code to set the connection password in Airflow's connection object.

Apache Airflow

conn = BaseHook.get_connection('my_gcp_conn')
conn.[1] = 'new_password'

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

Auser

Bextra

Chost

Dpassword

Attempts:

3 left

💡 Hint

Common Mistakes

Setting the 'user' attribute instead of 'password'.

Trying to set 'extra' which is a JSON string, not a password.

The password for a connection is stored in the password attribute. Setting it updates the connection's password.

4fill in blank

hard

Fill both blanks to create a connection dictionary for Google Cloud with project and key path.

Apache Airflow

conn = Connection(conn_id='my_gcp_conn', conn_type=[1], extra='{"extra__google_cloud_platform__project": "my-project", "extra__google_cloud_platform__key_path": "[2]"}')

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

A'google_cloud_platform'

Bmy-key.json

C/path/to/key.json

D'aws'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'aws' as connection type for GCP.

Using just the filename instead of full path for key_path.

The connection type must be 'google_cloud_platform' for GCP. The key path is a string with the path to your JSON key file, like '/path/to/key.json'.

5fill in blank

hard

Fill all three blanks to create a connection dictionary with conn_id, conn_type, and extra JSON for AWS.

Apache Airflow

conn = Connection(conn_id=[1], conn_type=[2], extra='{"extra__aws_access_key_id": "[3]"}')

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

A'my_aws_conn'

B'aws'

CAKIAIOSFODNN7EXAMPLE

D'google_cloud_platform'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'google_cloud_platform' as connection type for AWS.

Not quoting the connection ID or access key.

The connection ID is 'my_aws_conn', the type for AWS is 'aws', and the access key ID is a string like AKIAIOSFODNN7EXAMPLE.

Practice

1. What is the main purpose of managing connections in Airflow for cloud services?

easy

A. To manually enter credentials every time a task runs

B. To write custom code for each cloud service login

C. To store cloud login details securely and reuse them in tasks

D. To disable cloud service access in Airflow

Solution

1. Step 1: Understand connection management role

   Connection management stores credentials securely so tasks can access cloud services without exposing secrets.

2. Step 2: Identify reuse benefit

   Reusing connections avoids repeating credentials in multiple tasks, making workflows cleaner and safer.

3. Final Answer:

   To store cloud login details securely and reuse them in tasks -> Option C

4. Quick Check:

   Secure storage + reuse = A [OK]

Hint: Connections store credentials once for many tasks [OK]

Common Mistakes:

• Thinking credentials must be typed in each task
• Assuming connections are only for UI use
• Believing connections disable cloud access

2. Which command correctly adds a Google Cloud connection named 'gcp_default' in Airflow CLI?

easy

A. airflow connections add 'gcp_default' --conn-type google_cloud_platform --conn-extra '{"extra__google_cloud_platform__key_path":"/path/key.json"}'

B. airflow add connection gcp_default --type gcp --extra '{"key_path":"/path/key.json"}'

C. airflow connections create gcp_default --type google --extra '{"key":"/path/key.json"}'

D. airflow connection add gcp_default --conn-type gcp --conn-extra '{"key_path":"/path/key.json"}'

Solution

1. Step 1: Recall correct Airflow CLI syntax

   The command to add connections is 'airflow connections add' followed by connection id and parameters.

2. Step 2: Match correct flags and JSON format

   airflow connections add 'gcp_default' --conn-type google_cloud_platform --conn-extra '{"extra__google_cloud_platform__key_path":"/path/key.json"}' uses '--conn-type google_cloud_platform' and properly formatted JSON for extra parameters, matching Airflow docs.

3. Final Answer:

   airflow connections add 'gcp_default' --conn-type google_cloud_platform --conn-extra '{"extra__google_cloud_platform__key_path":"/path/key.json"}' -> Option A

4. Quick Check:

   Correct command syntax = C [OK]

Hint: Use 'airflow connections add' with correct flags [OK]

Common Mistakes:

• Using 'airflow add connection' instead of 'connections add'
• Wrong JSON key names in --conn-extra
• Missing quotes around JSON string

3. Given this Airflow DAG snippet using a connection ID 'aws_conn', what will happen if the connection is missing?

from airflow.providers.amazon.aws.operators.s3 import S3ListOperator

list_s3 = S3ListOperator(
    task_id='list_s3',
    bucket='my-bucket',
    aws_conn_id='aws_conn'
)

medium

A. The task will create a new connection automatically

B. The task will fail with a connection not found error

C. The task will skip without error

D. The task will run using default AWS credentials

Solution

1. Step 1: Understand connection usage in operator

   The operator uses 'aws_conn_id' to find credentials. If missing, it cannot authenticate.

2. Step 2: Predict behavior on missing connection

   Airflow raises an error when a required connection is not found, causing task failure.

3. Final Answer:

   The task will fail with a connection not found error -> Option B

4. Quick Check:

   Missing connection causes failure = D [OK]

Hint: Missing connection ID causes task failure [OK]

Common Mistakes:

• Assuming default credentials are used automatically
• Thinking task skips if connection missing
• Believing Airflow auto-creates connections

4. You added a connection with the command:

airflow connections add 'azure_default' --conn-type azure --conn-extra '{"tenantId":"abc","clientId":"123"}'

But your tasks fail to authenticate. What is the likely mistake?

medium

A. The JSON keys in --conn-extra are missing the 'extra__azure__' prefix

B. The connection type should be 'azure_cosmos' not 'azure'

C. The connection ID should not be quoted

D. The command should use 'airflow connection add' instead of 'connections add'

Solution

1. Step 1: Check connection type and extra format

   Azure connections require extra keys prefixed with 'extra__azure__' to be recognized properly.

2. Step 2: Identify JSON key format error

   Missing prefix in JSON keys causes Airflow to ignore credentials, leading to authentication failure.

3. Final Answer:

   The JSON keys in --conn-extra are missing the 'extra__azure__' prefix -> Option A

4. Quick Check:

   Correct extra key format fixes auth = B [OK]

Hint: Use 'extra__service__' prefix in --conn-extra keys [OK]

Common Mistakes:

• Using wrong connection type name
• Not prefixing JSON keys correctly
• Wrong CLI command syntax

5. You want to securely manage multiple cloud connections (AWS, GCP, Azure) in Airflow and reuse them in different DAGs. Which approach is best?

hard

A. Use environment variables only and avoid Airflow connections

B. Hardcode credentials in each DAG file for each cloud service

C. Store all credentials in a single connection with mixed cloud keys

D. Create separate connections for each cloud service using Airflow UI or CLI, then reference their IDs in tasks

Solution

1. Step 1: Understand best practice for connection management

   Separate connections per cloud service keep credentials organized and secure.

2. Step 2: Recognize reuse and security benefits

   Referencing connection IDs in tasks avoids duplication and keeps secrets out of code.

3. Final Answer:

   Create separate connections for each cloud service using Airflow UI or CLI, then reference their IDs in tasks -> Option D

4. Quick Check:

   Separate connections + reuse = A [OK]

Hint: Use separate connections per cloud, reference by ID [OK]

Common Mistakes:

• Hardcoding credentials in DAGs
• Mixing all credentials in one connection
• Avoiding Airflow connections for secrets