Kubernetes executor for dynamic scaling in Apache Airflow - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the executor to KubernetesExecutor in Airflow configuration.

Apache Airflow

executor = '[1]'

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

ALocalExecutor

BKubernetesExecutor

CSequentialExecutor

DCeleryExecutor

Attempts:

3 left

💡 Hint

Common Mistakes

Using LocalExecutor disables dynamic scaling.

SequentialExecutor runs tasks one by one, no parallelism.

CeleryExecutor requires a message broker setup.

Setting executor to KubernetesExecutor enables dynamic scaling using Kubernetes pods.

2fill in blank

medium

Complete the code to specify the namespace where Airflow pods will run.

Apache Airflow

kube_namespace = '[1]'

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

Akube-system

Bdefault

Cairflow

Dproduction

Attempts:

3 left

💡 Hint

Common Mistakes

Using default namespace mixes pods with other apps.

Using kube-system is reserved for system pods.

The airflow namespace is commonly used to isolate Airflow pods in Kubernetes.

3fill in blank

hard

Fix the error in the pod template file by completing the container image name.

Apache Airflow

image: [1]

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

Aairflow:apache/latest

Bairflow/apache:latest

Clatest/apache/airflow

Dapache/airflow:latest

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping repository and name parts.

Putting tag before name.

The correct Docker image format is repository/name:tag. Here, apache/airflow:latest is correct.

4fill in blank

hard

Fill both blanks to configure resource limits for CPU and memory in the pod spec.

Apache Airflow

resources:
  limits:
    cpu: '[1]'
    memory: '[2]'

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

A500m

B1Gi

C100m

D512Mi

Attempts:

3 left

💡 Hint

Common Mistakes

Using CPU limits in Gi units.

Using memory limits without units.

CPU limits use millicores like 500m (half a core), and memory limits use units like 512Mi (512 mebibytes).

5fill in blank

hard

Fill all three blanks to create a Kubernetes pod affinity rule for Airflow worker pods.

Apache Airflow

affinity:
  podAffinity:
    requiredDuringSchedulingIgnoredDuringExecution:
      - labelSelector:
          matchExpressions:
            - key: [1]
              operator: [2]
              values:
                - [3]

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

Acomponent

BIn

Cworker

Dapp

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong label keys.

Using operators like Exists without values.

This affinity rule matches pods with label component=worker using the In operator.