Get Unlimited Contributor Access to the all ExamTopics Exams!
Take advantage of PDF Files for 1000+ Exams along with community discussions and pass IT Certification Exams Easily.
You have an Azure Kubernetes Service (AKS) cluster named AKS1. You need to configure cluster autoscaler for AKS1. Which two tools should you use? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.
Suggested Answer:AB🗳️
A: The following example uses the kubectl autoscale command to autoscale the number of pods in the azure-vote-front deployment. If average CPU utilization across all pods exceeds 50% of their requested usage, the autoscaler increases the pods up to a maximum of 10 instances. A minimum of 3 instances is then defined for the deployment: kubectl autoscale deployment azure-vote-front --cpu-percent=50 --min=3 --max=10 B: Use the az aks update command to enable and configure the cluster autoscaler on the node pool for the existing cluster. Reference: https://docs.microsoft.com/en-us/azure/aks/tutorial-kubernetes-scale https://docs.microsoft.com/en-us/azure/aks/cluster-autoscaler
Correct Answer: B and D
We need to configure autoscaler for the AKS cluster. We do not want to scale Kubernetes pods, so kubectl command is not needed.
A: kubectl command is used for configuring Kubernetes and not AKS cluster.
B: The az aks command is used for the AKS cluster configuration.
C: Set-AzVm cmdlet is used for VMs.
D: Azure portal, under node pools, press scale, then choose auto scale.
E: Set-AzAks, creates or updates an AKS cluster, the correct cmdlet is Set-AzAksCluster.
AKS clusters can scale in one of two ways:
- The cluster autoscaler watches for pods that can't be scheduled on nodes because of resource constraints. The cluster then automatically increases the number of nodes.
- The horizontal pod autoscaler uses the Metrics Server in a Kubernetes cluster to monitor the resource demand of pods. If an application needs more resources, the number of pods is automatically increased to meet the demand.
Reference:
https://docs.microsoft.com/en-us/azure/aks/cluster-autoscaler
I agreed already but then you pointed out the two ways:
- The cluster autoscaler
- The horizontal pod autoscaler
The 2nd uses kubectl so the answer is A and B.
The Answer is not correct. The right is B & D.
B is for az aks command , check https://docs.microsoft.com/en-us/azure/aks/cluster-autoscaler
D is for Azure portal. Under node pools, press scale, then choose auto scale.
The Answer A is not correct as it is confusing with Horizontal pod autoscale which is not asked here. The pod autoscale use kubectl.
There are 2 things to understand:
a) Are we talking about pods?
b) Are we talking about nodes?
The question is regarding how to autoscale the AKS, so it means that we are talking about the nodes. As we are talking how to scale the nodes:
a) az aks is neccesary
b) Then you scale the nodes in the portal.
The correct answers are B & D.
If we want to scale the pods, the options would be kubelet, but it is not the case. We are not talking about the containers, we are talking about the infrastructure behind this.
The article does a good job explaining the difference of "cluster autoscaler" and "horizontal pod autoscaler"...
https://docs.microsoft.com/en-us/azure/aks/cluster-autoscaler
FYI also - the PowerShell command that can do this same task is "Set-AzAksCluster" (not Set-AzAks). B and D it is!
To corroborate with your answer, kubectl autoscale "creates an autoscaler that automatically chooses and sets the number of pods that run in a kubernetes cluster":
https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#autoscale
According to Microsoft, this is a Horizontal pod autoscale, not a Cluster autoscale:
https://docs.microsoft.com/en-us/azure/aks/cluster-autoscaler#about-the-cluster-autoscaler
But we are not talking about the pods, we are talinkg about the nodes, so is B and D. Think that this service is managed by Azure, and they will not allow to do this by yourself, and this is the reason why you must choose the portal.
A. the kubectl command: kubectl is a command-line tool used for interacting with Kubernetes clusters, including managing deployments and pods within a cluster. However, it is not used to configure cluster-level settings like autoscaling.
C. the Set-AzVm cmdlet: Set-AzVm is a PowerShell cmdlet used to manage Azure virtual machines (VMs), not AKS clusters or their autoscaling configurations.
E. the Set-AzAks cmdlet: While the Set-AzAks cmdlet is used for managing AKS clusters in PowerShell, it is not specifically used for configuring cluster autoscaler. Cluster autoscaler configuration typically involves different commands or settings, and it's not part of the core Set-AzAks functionality.
To configure cluster autoscaler for AKS, you primarily use the Azure CLI (az) or the Azure portal, as these tools are specifically designed for managing AKS cluster-level settings and configurations.
Correct : AB
The cluster autoscaler is a Kubernetes component. Although the AKS cluster uses a virtual machine scale set for the nodes, don't manually enable or edit settings for scale set autoscale in the Azure portal or using the Azure CLI. Let the Kubernetes cluster autoscaler manage the required scale settings.
https://learn.microsoft.com/en-us/azure/aks/cluster-autoscaler
you wrong, A and B are not correct tools to configure cluster autoscaler for AKS1.
The kubectl command is a tool that allows you to run commands against Kubernetes clusters. You can use the kubectl command to deploy applications, inspect and manage cluster resources, or view logs. However, you cannot use the kubectl command to enable or disable cluster autoscaler for an AKS cluster, as this is a feature that is managed by Azure, not by Kubernetes. You need to use the Azure CLI or the Azure portal to configure cluster autoscaler for an AKS cluster .
The az aks command is a correct tool to configure cluster autoscaler for AKS1, as explained in the previous answer. However, you need to use another tool in addition to the az aks command, such as the Azure portal. Therefore, A and B are not a complete solution.
.Open AI: To configure cluster autoscaler for an Azure Kubernetes Service (AKS) cluster (AKS1), you can use the following tools:
B. the az aks command: You can use the Azure Command-Line Interface (CLI) command az aks update to configure the cluster autoscaler for an AKS cluster. This command allows you to enable or disable the cluster autoscaler and set parameters like minimum and maximum node counts.
D. the Azure portal: You can also configure the cluster autoscaler for AKS using the Azure portal. Navigate to your AKS cluster in the Azure portal, go to the "Node pools" section, and then configure the autoscaler settings for the specific node pool.
The other options (A, C, and E) are not the primary tools used to configure cluster autoscaler for AKS.
Answer:AB
Explanation:
A: The following example uses the kubectl autoscale command to autoscale the number of pods in the azure-vote-front deployment. If average CPU utilization across all pods exceeds 50% of their requested usage, the autoscaler increases the pods up to a maximum of 10 instances. Aminimum of 3 instances is then defined for the deployment:kubectl autoscale deployment azure-vote-front --cpu-percent=50 --min=3 --max=10
B: Use the az aks update command to enable and configure the cluster autoscaler on the nodepool for the existing cluster.
Answer: A and B
Autoscale pods using kubectl autoscale
example:
kubectl autoscale deployment azure-vote-front --cpu-percent=50 --min=3 --max=10
https://learn.microsoft.com/en-us/azure/aks/tutorial-kubernetes-scale?tabs=azure-cli
A. the kubectl command
B. the az aks command
Explanation:
The kubectl command is a command-line tool used to interact with Kubernetes clusters. It allows you to manage and configure various aspects of your AKS cluster, including enabling the cluster autoscaler. You can use kubectl to apply the necessary configuration changes to enable the autoscaler.
The az aks command is a command-line tool provided by the Azure CLI (Command-Line Interface). It specifically deals with managing Azure Kubernetes Service (AKS) resources. Using the az aks command, you can enable the cluster autoscaler by modifying the AKS cluster's properties.
ChatGPT response:
The two tools you should use to configure cluster autoscaler for AKS1 are:
B. the az aks command, which provides a command-line interface for managing AKS clusters, including the ability to enable and configure cluster autoscaler.
E. the Set-AzAks cmdlet, which is a PowerShell cmdlet for managing AKS clusters. It can be used to enable and configure cluster autoscaler.
Therefore, options B and E are correct. Options A, C, and D are not required for this task.
"follow up question"
Will the answer be the same if I need to configure autoscaler for the AKS cluster. I do not want to scale Kubernetes pods
Yes, the answer would still be the same.
Configuring cluster autoscaler for an AKS cluster is independent of scaling Kubernetes pods. The purpose of cluster autoscaler is to automatically adjust the size of the AKS cluster based on the resource demands of the workloads running on it, while scaling Kubernetes pods involves adjusting the number of replicas for a specific deployment or replica set.
Therefore, to configure cluster autoscaler for an AKS cluster, you would still need to use the az aks command and the Set-AzAks cmdlet.
We need to configure autoscaler for the AKS cluster. We do not want to scale Kubernetes pods, so kubectl command is not needed.
Use Portal under Node Pools
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
mlantonis
Highly Voted 2 years, 6 months agoklexams
1 year, 1 month agoMozbius_
1 year, 10 months agofedztedz
Highly Voted 3 years agojantoniocesargatica
2 years, 7 months agomythjava
9 months, 2 weeks agojuniorccs
1 year, 10 months agodiligent176
2 years, 11 months agomarcellov
2 years, 7 months agojantoniocesargatica
2 years, 7 months agoHibs2016
3 years agoRednevi
Most Recent 2 months, 1 week agoraj_raj22
3 months agoQaisFM
3 months, 2 weeks agonahfam123
3 weeks, 1 day agoMGJG
3 months, 3 weeks agoTeroristo
4 months, 2 weeks agoNYTK
4 months, 2 weeks agoJosete1106
4 months, 2 weeks agoraj24051961
5 months, 1 week agoTomix
5 months, 1 week agoJunetGoyal
7 months, 1 week agozzreflexzz
7 months, 1 week agoExilic
7 months, 2 weeks agogarmatey
6 months, 1 week agomythjava
9 months, 2 weeks agoUmbongoDrink
9 months, 3 weeks agotypales2005
10 months, 4 weeks ago