Module Assessment

1.

What is the purpose of the horizontal pod autoscaler (HPA) in Azure Kubernetes Service?

To add VM-backed nodes to the cluster when pods can't be scheduled

To manually set replica or node counts to a fixed value

To monitor workload metrics and automatically adjust the number of pod replicas

2.

What is the purpose of the Kubernetes cluster autoscaler?

To monitor the status of the Kubernetes API server

To adjust the number of pods based on application demand

To adjust the number of nodes when pods can't be scheduled because their resource requests don't fit on existing nodes

3.

Your AKS application periodically experiences large traffic spikes that need additional pod capacity within seconds. The cluster autoscaler can take a few minutes to add new VM-backed nodes. Which AKS feature is designed for this rapid burst scenario?

Manually scaling the existing node pool to a higher fixed node count before the spike.

Increasing the cluster autoscaler max-count for the node pool.

Enabling virtual nodes so AKS can schedule burst pods on Azure Container Instances (ACI).

4.

You want to run exactly five replicas of a Deployment for a controlled test and set an AKS node pool to three nodes without automatic scaling. Which approach uses manual scaling correctly?

Configure the horizontal pod autoscaler and cluster autoscaler with matching minimum and maximum values.

Use kubectl scale deployment <name> --replicas=5 for the workload and az aks nodepool scale --node-count 3 for the node pool.

Delete Kubernetes nodes with kubectl delete node until three nodes remain.

Check your knowledge

Feedback