Exam AZ-305 topic 4 question 28 discussion

cluster autoscaler for windows Virtual Nodes for Linux

C. virtual nodes To meet the requirements of minimizing the time it takes to provision compute resources during scale-out operations, supporting autoscaling of Linux containers, and minimizing administrative effort, you should recommend virtual nodes for the Azure Kubernetes Service (AKS) solution with Linux nodes. Virtual nodes allow you to scale your AKS cluster quickly by offloading the additional compute resources to Azure Container Instances (ACI). This reduces the time it takes to provision resources during scale-out operations, as the resources can be provisioned instantly without having to wait for a new node to be created. Additionally, virtual nodes support autoscaling of Linux containers and require minimal administrative effort compared to other scaling options.

The best scaling option for your Azure Kubernetes Service (AKS) cluster that meets fast provisioning, Linux container autoscaling, and minimal administrative effort is: ✅ Recommended Option: Azure AKS with Virtual Machine Scale Sets (VMSS) and Cluster Autoscaler Use Virtual Machine Scale Sets (VMSS) for Fast Provisioning VMSS enables fast scale-out operations by automatically provisioning new nodes in seconds. Supports Spot VMs for cost-optimized scaling if needed. Enable Cluster Autoscaler for Dynamic Scaling Automatically adjusts the number of nodes based on demand. Scales out when workloads require more compute resources. Scales in to save costs when workloads decrease. Use Kubernetes Horizontal Pod Autoscaler (HPA) Ensures container-level autoscaling based on CPU, memory, or custom metrics. Works seamlessly with VMSS scaling for optimized resource management.

Given answer C is correct as per o rapidly scale application workloads in an AKS cluster, you can use virtual nodes. With virtual nodes, you have quick provisioning of pods, and only pay per second for their execution time. You don't need to wait for Kubernetes cluster autoscaler to deploy VM compute nodes to run more pods. Virtual nodes are only supported with Linux pods and nodes. https://learn.microsoft.com/en-us/azure/aks/virtual-nodes

To minimize the time it takes to provision compute resources during scale-out operations in an AKS cluster with Linux nodes, the recommended scaling option would be Virtual Nodes. Virtual Nodes allow the AKS cluster to use Azure Container Instances (ACI) as worker nodes, which can be quickly and easily provisioned, enabling faster scaling compared to traditional AKS worker nodes.

To rapidly scale application workloads in an AKS cluster, you can use virtual nodes.

Virtual Nodes

https://learn.microsoft.com/en-us/azure/aks/virtual-nodes The virtual nodes add-on for AKS, is based on the open source project Virtual Kubelet. So if you need to scale out faster than AKS let you, you need to burst to ACI.

C - because "virtual node" is the name of the Microsoft "product". In short, it connects kubernetes management to ACI containers. That said... it uses Virtual Kubelet technology, and probably horizontal pod autoscaler to scale.

https://docs.microsoft.com/en-us/azure/aks/virtual-nodes it should be C then?

I believe Kay000001 meant C, virtual nodes To rapidly scale application workloads in an AKS cluster, you can use virtual nodes. With virtual nodes, you have quick provisioning of pods, and only pay per second for their execution time. You don't need to wait for Kubernetes cluster autoscaler to deploy VM compute nodes to run the additional pods. Virtual nodes are only supported with Linux pods and nodes.

B. https://docs.microsoft.com/en-us/azure/aks/virtual-nodes