MCQs on Managing AKS Clusters | Cluster Management in AKS
This set of 30 MCQs covers key concepts in managing Azure Kubernetes Service (AKS) clusters. Topics include scaling, node pool management, upgrades, monitoring with Azure Monitor, and troubleshooting. These questions will help reinforce your understanding of AKS for certification and practical application.
Scaling AKS Clusters (Manual and Automatic Scaling)
- Which of the following is used for automatic scaling in AKS?
- A) Horizontal Pod Autoscaler
- B) Virtual Machine Scale Sets
- C) Cluster Autoscaler
- D) Azure Load Balancer
- How can you manually scale an AKS cluster?
- A) Modify the cluster size via Azure CLI
- B) Use Horizontal Pod Autoscaler
- C) Update the resource group size
- D) Deploy a new node pool
- What happens when you enable Cluster Autoscaler in AKS?
- A) It automatically scales the pods based on load.
- B) It automatically adjusts the number of nodes based on demand.
- C) It reduces the number of resource group subscriptions.
- D) It scales the Kubernetes API server.
- What is the minimum number of nodes required for automatic scaling in AKS?
- A) 1 node
- B) 2 nodes
- C) 3 nodes
- D) 5 nodes
- When scaling AKS manually, what should you do first?
- A) Add a new pod
- B) Resize node pools via Azure Portal or CLI
- C) Add a load balancer
- D) Change resource limits for pods
- What is the default minimum node count for a node pool in AKS?
- A) 1
- B) 3
- C) 5
- D) 0
Managing Node Pools
- What is a node pool in AKS?
- A) A collection of Kubernetes resources
- B) A group of virtual machines
- C) A set of Kubernetes pods
- D) A virtual network for scaling
- Which of the following can be done when creating a new node pool in AKS?
- A) Set the Kubernetes version
- B) Choose a region
- C) Set the node type and size
- D) All of the above
- How can you add a new node pool to an existing AKS cluster?
- A) Use Azure CLI or Portal to create the node pool
- B) Deploy a new virtual machine
- C) Edit the YAML file of the cluster
- D) Add nodes manually via the AKS management interface
- Which of the following is true about node pool scaling?
- A) Node pools cannot be deleted once created
- B) The size of a node pool cannot be changed after creation
- C) You can scale node pools independently of each other
- D) Node pools can only be scaled manually
- What feature allows a node pool to use different VM sizes in AKS?
- A) Availability Zones
- B) Node Pool Versioning
- C) Mixed-Instance Scaling
- D) Horizontal Pod Autoscaler
- What is the main advantage of using multiple node pools in an AKS cluster?
- A) Separate scaling policies
- B) Single VM size for all nodes
- C) Lower cost for low-priority workloads
- D) All of the above
Upgrading and Maintaining AKS Clusters
- What is the first step in upgrading an AKS cluster?
- A) Update the node pool
- B) Backup the cluster
- C) Deploy new workloads
- D) Restart the API server
- What is the upgrade method used to upgrade AKS clusters?
- A) Rolling upgrades
- B) Sequential upgrades
- C) Parallel upgrades
- D) Incremental upgrades
- Which of the following is recommended for upgrading an AKS cluster?
- A) Directly upgrade the cluster without testing
- B) Use the Azure CLI or Portal to perform the upgrade
- C) Upgrade without first checking for compatibility
- D) Update only the Kubernetes version without other components
- What must you consider before upgrading the Kubernetes version in AKS?
- A) Compatibility of workloads and applications
- B) Version history and supported upgrade paths
- C) Current node pool configuration
- D) All of the above
- How can you automate AKS upgrades?
- A) Using Azure Automation
- B) Through Azure Monitor alerts
- C) Using the Azure CLI
- D) By enabling Auto-Upgrade feature
- What is the purpose of the ‘kubectl get nodes’ command after upgrading AKS?
- A) To monitor the number of pods running
- B) To confirm the upgrade of nodes and their status
- C) To delete outdated nodes
- D) To configure the load balancing policy
Monitoring AKS with Azure Monitor and Log Analytics
- What Azure service integrates with AKS for monitoring and logging?
- A) Azure Monitor
- B) Azure Storage
- C) Azure Active Directory
- D) Azure Load Balancer
- What is the primary function of Azure Monitor in AKS?
- A) Managing resource groups
- B) Monitoring the performance and health of AKS clusters
- C) Scaling node pools automatically
- D) Creating new Kubernetes deployments
- How does Azure Monitor help troubleshoot AKS issues?
- A) By sending email alerts
- B) By collecting logs and metrics from AKS
- C) By performing rolling upgrades
- D) By controlling traffic flow
- What can be analyzed with Log Analytics in AKS?
- A) Pod metrics and logs
- B) Node metrics and logs
- C) Cluster performance and health
- D) All of the above
- Which service can you use to configure diagnostic settings for AKS monitoring?
- A) Azure Monitor
- B) Log Analytics workspace
- C) Azure Advisor
- D) Azure Network Watcher
- What data does Log Analytics collect from AKS?
- A) Only Kubernetes configuration files
- B) Metrics, logs, and diagnostic data
- C) Network traffic data
- D) Only Kubernetes pod events
Troubleshooting Common Issues in AKS
- If an AKS cluster is experiencing slow performance, what is a potential cause?
- A) Insufficient node resources
- B) Outdated Kubernetes version
- C) Misconfigured node pool scaling
- D) All of the above
- Which tool can be used to view logs for troubleshooting in AKS?
- A) kubectl logs
- B) Azure CLI
- C) Log Analytics
- D) Azure Monitor
- What should you check if pods are not scheduling in an AKS cluster?
- A) Node pool capacity and resource availability
- B) The status of Azure Monitor
- C) The network traffic logs
- D) Only the pod configuration
- How can you fix a failed AKS deployment?
- A) Recreate the Kubernetes resources
- B) Review error messages and logs for the issue
- C) Delete the failed resources manually
- D) All of the above
- What is a common cause of Kubernetes pod crashes in AKS?
- A) Memory and CPU resource limits being too low
- B) Incorrect node pool configuration
- C) Outdated Kubernetes components
- D) Incorrect network policies
- Which command is useful to view the status of a pod in AKS?
- A) kubectl describe pod
- B) kubectl delete pod
- C) kubectl get service
- D) kubectl scale pod
Answer Table
| Qno | Answer |
|---|---|
| 1 | C) Cluster Autoscaler |
| 2 | A) Modify the cluster size via Azure CLI |
| 3 | B) It automatically adjusts the number of nodes based on demand. |
| 4 | A) 1 node |
| 5 | B) Resize node pools via Azure Portal or CLI |
| 6 | A) 1 |
| 7 | B) A group of virtual machines |
| 8 | D) All of the above |
| 9 | A) Use Azure CLI or Portal to create the node pool |
| 10 | C) You can scale node pools independently of each other |
| 11 | C) Mixed-Instance Scaling |
| 12 | D) All of the above |
| 13 | B) Backup the cluster |
| 14 | A) Rolling upgrades |
| 15 | B) Use the Azure CLI or Portal to perform the upgrade |
| 16 | D) All of the above |
| 17 | A) Using Azure Automation |
| 18 | B) To confirm the upgrade of nodes and their status |
| 19 | A) Azure Monitor |
| 20 | B) Monitoring the performance and health of AKS clusters |
| 21 | B) By collecting logs and metrics from AKS |
| 22 | D) All of the above |
| 23 | B) Log Analytics workspace |
| 24 | B) Metrics, logs, and diagnostic data |
| 25 | D) All of the above |
| 26 | C) Log Analytics |
| 27 | A) Node pool capacity and resource availability |
| 28 | D) All of the above |
| 29 | A) Memory and CPU resource limits being too low |
| 30 | A) kubectl describe pod |