|
2 | 2 | uid: learn.wwl.configure-scaling-azure-kubernetes-service.knowledge-check |
3 | 3 | title: Module assessment |
4 | 4 | metadata: |
5 | | - title: Module assessment |
| 5 | + title: Module Assessment |
6 | 6 | description: "Knowledge check" |
7 | | - ms.date: 10/25/2023 |
| 7 | + ms.date: 04/20/2026 |
8 | 8 | author: Orin-Thomas |
9 | 9 | ms.author: orthomas |
10 | 10 | ms.topic: unit |
11 | 11 | module_assessment: true |
12 | | -durationInMinutes: 7 |
| 12 | +durationInMinutes: 9 |
13 | 13 | content: | |
14 | 14 | [!include[](includes/8-knowledge-check.md)] |
15 | 15 | quiz: |
16 | 16 | title: "Check your knowledge" |
17 | 17 | questions: |
18 | | - - content: "What is the purpose of the Horizontal Pod Autoscaler in Azure Kubernetes Service?" |
| 18 | + - content: "What is the purpose of the horizontal pod autoscaler (HPA) in Azure Kubernetes Service?" |
19 | 19 | choices: |
20 | | - - content: "To provision a larger number of application instances" |
| 20 | + - content: "To add VM-backed nodes to the cluster when pods can't be scheduled" |
21 | 21 | isCorrect: false |
22 | | - explanation: "Incorrect. Provisioning a larger number of application instances is a separate concept from the purpose of the Horizontal Pod Autoscaler." |
23 | | - - content: "To manually scale replicas or nodes based on a fixed cost" |
| 22 | + explanation: "Incorrect. Adding nodes is the role of the cluster autoscaler. The HPA changes the number of pod replicas for a workload; it doesn't expand node pools." |
| 23 | + - content: "To manually set replica or node counts to a fixed value" |
24 | 24 | isCorrect: false |
25 | | - explanation: "Incorrect. This describes manually scaling resources, not the purpose of the Horizontal Pod Autoscaler." |
26 | | - - content: "To monitor resource demand and automatically scale the number of pods based on defined metrics such as CPU usage" |
| 25 | + explanation: "Incorrect. Manual scaling sets a chosen replica or node count directly. The HPA is automatic horizontal scaling that adjusts pod replicas based on metrics." |
| 26 | + - content: "To monitor workload metrics and automatically adjust the number of pod replicas" |
27 | 27 | isCorrect: true |
28 | | - explanation: "Correct. The Horizontal Pod Autoscaler monitors resource demand and automatically scales the number of pods based on defined metrics such as CPU usage, allowing for efficient use of resources." |
| 28 | + explanation: "Correct. The HPA increases or decreases pod replicas based on metrics such as CPU, memory, custom, or external metrics. For CPU or memory metrics, containers need resource requests so Kubernetes can calculate utilization." |
29 | 29 | - content: "What is the purpose of the Kubernetes cluster autoscaler?" |
30 | 30 | choices: |
31 | 31 | - content: "To monitor the status of the Kubernetes API server" |
32 | 32 | isCorrect: false |
33 | | - explanation: "Incorrect. The cluster autoscaler monitors the Metrics API server, not the Kubernetes API server." |
| 33 | + explanation: "Incorrect. API server health is a monitoring and platform operations concern. The cluster autoscaler focuses on node pool capacity for scheduling workloads." |
34 | 34 | - content: "To adjust the number of pods based on application demand" |
35 | 35 | isCorrect: false |
36 | | - explanation: "Incorrect. This is the purpose of the horizontal pod autoscaler." |
37 | | - - content: "To adjust the number of nodes based on the requested compute resources in the node pool" |
| 36 | + explanation: "Incorrect. The horizontal pod autoscaler (HPA) adjusts pod replicas based on workload metrics. The cluster autoscaler changes node count when scheduling needs require more or fewer nodes." |
| 37 | + - content: "To adjust the number of nodes when pods can't be scheduled because their resource requests don't fit on existing nodes" |
38 | 38 | isCorrect: true |
39 | | - explanation: "Correct. The cluster autoscaler adjusts the number of nodes in the AKS cluster based on the requested compute resources in the node pool to ensure that there are enough resources to run the pods." |
40 | | - - content: "What is the purpose of the cluster autoscaler component in AKS?" |
| 39 | + explanation: "Correct. The cluster autoscaler reacts to unschedulable pending pods when adding a node could make them schedulable. It adds nodes within node pool limits and can remove underutilized nodes when capacity is no longer needed." |
| 40 | + - content: "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?" |
41 | 41 | choices: |
42 | | - - content: "To manually enable or edit settings for scale set autoscale in the Azure portal or using the Azure CLI." |
| 42 | + - content: "Manually scaling the existing node pool to a higher fixed node count before the spike." |
43 | 43 | isCorrect: false |
44 | | - explanation: "Incorrect. This is not the purpose of the cluster autoscaler component in AKS." |
45 | | - - content: "To create a resource group using the az group create command." |
| 44 | + explanation: "Incorrect. Manual scaling requires advance knowledge of the spike and keeps extra VM-backed nodes running between spikes, which adds cost and isn't reactive." |
| 45 | + - content: "Increasing the cluster autoscaler `max-count` for the node pool." |
46 | 46 | isCorrect: false |
47 | | - explanation: "Incorrect. This is not the purpose of the cluster autoscaler component in AKS." |
48 | | - - content: "Enables the automation and validation of the creation and teardown of environments to help deliver secure and stable application hosting platforms." |
| 47 | + explanation: "Incorrect. Raising `max-count` only changes the upper bound. The cluster autoscaler still needs time to provision new VM-backed nodes, so it doesn't address the per-second responsiveness the scenario requires." |
| 48 | + - content: "Enabling virtual nodes so AKS can schedule burst pods on Azure Container Instances (ACI)." |
49 | 49 | isCorrect: true |
50 | | - explanation: "Correct. The cluster autoscaler component can watch for pods in your cluster that can't be scheduled because of resource constraints. When issues are detected, the number of nodes in a node pool increases to meet the application demand. Nodes are also regularly checked for a lack of running pods, with the number of nodes then decreased as needed. This ability to automatically scale up or down the number of nodes in your AKS cluster lets you run an efficient, cost effective cluster." |
| 50 | + explanation: "Correct. Virtual nodes use the Virtual Kubelet to present ACI as a Kubernetes node, letting AKS schedule burst pods on ACI in seconds without waiting for the cluster autoscaler to add new VM-backed nodes." |
| 51 | + - content: "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?" |
| 52 | + choices: |
| 53 | + - content: "Configure the horizontal pod autoscaler and cluster autoscaler with matching minimum and maximum values." |
| 54 | + isCorrect: false |
| 55 | + explanation: "Incorrect. HPA and the cluster autoscaler are automatic scaling features. Manual scaling sets a fixed replica or node count directly." |
| 56 | + - content: "Use `kubectl scale deployment <name> --replicas=5` for the workload and `az aks nodepool scale --node-count 3` for the node pool." |
| 57 | + isCorrect: true |
| 58 | + explanation: "Correct. `kubectl scale` changes the desired replica count for a workload, and `az aks nodepool scale` sets a fixed node count for an AKS node pool." |
| 59 | + - content: "Delete Kubernetes nodes with `kubectl delete node` until three nodes remain." |
| 60 | + isCorrect: false |
| 61 | + explanation: "Incorrect. AKS node counts should be changed through AKS scaling operations such as `az aks nodepool scale` or `az aks scale`. Removing AKS nodes directly with `kubectl` isn't supported." |
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments