Deploying workloads to AKS in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an AKS cluster using Azure CLI.

Azure

az aks create --resource-group myResourceGroup --name myAKSCluster --node-count [1] --enable-addons monitoring --generate-ssh-keys

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

A3

B5

C1

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Setting node count to 0 which is invalid.

Using too many nodes for a simple test cluster.

The --node-count parameter specifies the number of nodes in the AKS cluster. A typical starting count is 3 nodes for availability.

2fill in blank

medium

Complete the command to get credentials for your AKS cluster.

Azure

az aks get-credentials --resource-group myResourceGroup --name [1]

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

AmyResourceGroup

BmyAKSCluster

Cdefault

Dkubeconfig

Attempts:

3 left

💡 Hint

Common Mistakes

Using the resource group name instead of the cluster name.

Using unrelated strings like 'default' or 'kubeconfig'.

The --name parameter expects the AKS cluster name to fetch credentials.

3fill in blank

hard

Fix the error in the kubectl command to deploy a YAML file.

Azure

kubectl [1] -f deployment.yaml

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

Acreate

Bdelete

Capply

Dget

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'create' which fails if resource exists.

Using 'delete' or 'get' which do not deploy resources.

The apply command is used to create or update resources from a YAML file.

4fill in blank

hard

Fill both blanks to scale the AKS deployment to 4 replicas.

Azure

kubectl scale deployment [1] --replicas=[2]

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

Amyapp-deployment

Bservice

C4

D3

Attempts:

3 left

💡 Hint

Common Mistakes

Using service name instead of deployment name.

Setting replicas to a wrong number.

The deployment name is needed to scale it, and the replicas number sets the desired count.

5fill in blank

hard

Fill all three blanks to expose the deployment as a LoadBalancer service on port 80.

Azure

kubectl expose deployment [1] --type=[2] --port=[3]

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

Amyapp-deployment

BLoadBalancer

C80

DClusterIP

Attempts:

3 left

💡 Hint

Common Mistakes

Using ClusterIP which exposes service only inside the cluster.

Using wrong port numbers.

Exposing the deployment with type LoadBalancer creates an external IP. Port 80 is the standard HTTP port.

Practice

1. What is the main purpose of using a Deployment in Azure Kubernetes Service (AKS)?

easy

A. To monitor the health of the AKS cluster nodes

B. To manage and maintain a specified number of app copies running

C. To expose the app to the internet

D. To store data persistently for the app

Solution

1. Step 1: Understand Deployment role in AKS

   A Deployment ensures that a specified number of replicas of an app are running and manages updates to those replicas.

2. Step 2: Differentiate from other components

   Persistent storage is handled by volumes, exposure by Services, and monitoring by Azure Monitor, not Deployments.

3. Final Answer:

   To manage and maintain a specified number of app copies running -> Option B

4. Quick Check:

   Deployment manages app replicas = A [OK]

Hint: Deployments keep app copies running smoothly [OK]

Common Mistakes:

• Confusing Deployment with Service for exposure
• Thinking Deployment stores data
• Assuming Deployment monitors nodes

2. Which kubectl command correctly applies a YAML file named app-deployment.yaml to deploy an app to AKS?

easy

A. kubectl create app-deployment.yaml

B. kubectl run app-deployment.yaml

C. kubectl apply -f app-deployment.yaml

D. kubectl deploy app-deployment.yaml

Solution

1. Step 1: Identify correct kubectl syntax for applying YAML

   The command to apply a YAML file is kubectl apply -f filename.yaml.

2. Step 2: Check other options for correctness

   kubectl create requires resource type, kubectl run is for quick pod creation, and kubectl deploy is not a valid command.

3. Final Answer:

   kubectl apply -f app-deployment.yaml -> Option C

4. Quick Check:

   Apply YAML file = kubectl apply -f [OK]

Hint: Use 'kubectl apply -f' to deploy YAML files [OK]

Common Mistakes:

• Using 'kubectl create' without resource type
• Trying 'kubectl deploy' which doesn't exist
• Confusing 'kubectl run' with applying YAML

3. Given this YAML snippet for an AKS Deployment:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: myapp
spec:
  replicas: 3
  selector:
    matchLabels:
      app: myapp
  template:
    metadata:
      labels:
        app: myapp
    spec:
      containers:
      - name: myapp-container
        image: nginx:latest
        ports:
        - containerPort: 80

How many pods will AKS try to run for this Deployment?

medium

A. 3

B. 2

C. 1

D. 0

Solution

1. Step 1: Identify the replicas count in the YAML

   The replicas field is set to 3, meaning AKS will run 3 pods.

2. Step 2: Confirm no other fields override replicas

   There is no override or scaling specified, so the number remains 3.

3. Final Answer:

   3 -> Option A

4. Quick Check:

   replicas: 3 means 3 pods [OK]

Hint: Check 'replicas' field for pod count [OK]

Common Mistakes:

• Ignoring the replicas field
• Confusing selector labels with pod count
• Assuming default pod count is 1

4. You applied a Deployment YAML but your pods are stuck in 'Pending' state. Which of these is the most likely cause?

medium

A. The container image name is misspelled

B. The Service type is set to ClusterIP

C. The Deployment YAML is missing the 'replicas' field

D. There are not enough cluster resources to schedule pods

Solution

1. Step 1: Understand what 'Pending' pod state means

   Pods in 'Pending' usually wait for resources like CPU or memory to be available on nodes.

2. Step 2: Evaluate options for causing Pending state

   Misspelled image causes ImagePull errors, missing replicas defaults to 1, and Service type doesn't affect pod scheduling.

3. Final Answer:

   There are not enough cluster resources to schedule pods -> Option D

4. Quick Check:

   Pending pods = resource shortage [OK]

Hint: Pending pods often mean no resources available [OK]

Common Mistakes:

• Confusing image pull errors with Pending state
• Thinking missing replicas stops pod creation
• Assuming Service type affects pod scheduling

5. You want to expose your AKS Deployment to the internet with a stable IP and load balancing. Which Kubernetes Service type should you use in your YAML?

hard

A. LoadBalancer

B. NodePort

C. ClusterIP

D. ExternalName

Solution

1. Step 1: Identify Service types and their purposes

   ClusterIP exposes service inside cluster only, NodePort exposes on node ports, LoadBalancer creates cloud load balancer with stable IP, ExternalName maps to external DNS.

2. Step 2: Choose Service type for internet exposure with stable IP

   LoadBalancer is the correct choice to get a cloud-managed IP and load balancing for external access.

3. Final Answer:

   LoadBalancer -> Option A

4. Quick Check:

   Internet exposure with stable IP = LoadBalancer [OK]

Hint: Use LoadBalancer Service for external stable IP [OK]

Common Mistakes:

• Using ClusterIP which is internal only
• Choosing NodePort which uses random ports
• Confusing ExternalName with load balancing