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.