Q13 — AWS SAA-C03 Ch.5

Question 13 of 65 | ← Chapter 5

Q313. A company runs container applications by using Amazon Elastic Kubernetes Service (Amazon EKS) and the Kubernetes Horizontal Pod Autoscaler. The workload is not consistent throughout the day. A solutions architect notices that the number of nodes does not automatically scale out when the existing nodes have reached maximum capacity in the cluster, which causes performance issues. Which solution will resolve this issue with the LEAST administrative overhead?

Correct Answer: B. Use the Kubernetes Cluster Autoscaler to manage the number of nodes in the cluster

Explanation

Option B: Using the Kubernetes Cluster Autoscaler to manage the number of nodes in the cluster is the least administrative overhead solution because it automatically adjusts the number of nodes based on the resource utilization of the cluster. When the workload increases, the autoscaler adds new nodes to the cluster and when the workload decreases, it removes unused nodes from the cluster automatically. Option A: Scaling out the nodes by tracking the memory usage is an effective solution, but it requires manual configuration of scaling policies, thresholds, and targets, which may result in administrative overhead. This option can also lead to over-provisioning or under-provisioning of resources if not configured optimally.Option C: Using an AWS IAMbda function to resize the EKS cluster automatically can be complex to implement and maintain. It requires custom scripting and involves additional components like EventBridge to monitor the node utilization and trigger the Lambda function. This option can lead to additional maintenance overhead.Option D: Using an Amazon EC2 Auto Scaling group to distribute the workload can work, but it requires more administrative overhead compared to using the Kubernetes Cluster Autoscaler. It involves configuring EC2 instances, Launch Configurations, and Auto Scaling Policies, which can take longer to set up and configure than the Kubernetes Cluster Autoscaler. Additionally, managing the integration between Amazon EKS and EC2 Auto Scaling groups can be complex and time-consuming.