Q50 — AWS SAA-C03 Ch.5

Question 50 of 65 | ← Chapter 5

Q350. A company runs container applications by using Amazon Elastic Kubernetes Service(Amazon EKS).The company's workload is not consistent throughout the day.The company wants Amazon EKS to scale in and out according to the workload.Which combination of steps will meet these requirements with the LEAST operational overhead? (Select TWO.)

• A. Use an AWS Lambda function to resize the EKS cluster
• B. Use the Kubernetes Metrics Server to activate horizontal pod autoscaling ✓
• C. Use the Kubernetes Cluster Autoscaler to manage the number of nodes in the cluster ✓
• D. Use Amazon API Gateway and connect it to Amazon EKS
• E. Use AWS App Mesh to observe network activity

Correct Answer: B. Use the Kubernetes Metrics Server to activate horizontal pod autoscaling, C. Use the Kubernetes Cluster Autoscaler to manage the number of nodes in the cluster

Explanation

Option B and C will meet the given requirements with the least operational overhead. B. Use the Kubernetes Metrics Server to activate horizontal pod autoscaling:The Kubernetes Metrics Server can provide metrics for Kubernetes objects like pods, and can be used to enable horizontal pod autoscaling in Amazon EKS. Horizontal pod autoscaling automatically adjusts the number of replicas of a pod based on CPU utilization or other metrics. This allows the number of pods to quickly scale up or down based on workload changes, without manual intervention. C. Use the Kubernetes Cluster Autoscaler to manage the number of nodes in the cluster:The Kubernetes Cluster Autoscaler automatically adjusts the number of nodes in an Amazon EKS cluster based on the resource demand of the workloads running in the cluster. It can also help reduce costs by ensuring that no more nodes are running than are needed to meet the current workload. By leveraging both horizontal pod autoscaling and the Kubernetes Cluster Autoscaler, the company can ensure optimal resource usage while minimizing operational overhead.Option A involves using an AWS Lambda function to resize the EKS cluster which may require additional configuration and setup time compared to using built-in Kubernetes features. Option D involves using Amazon API Gateway to connect to EKS which is typically used for managing APIs and not scaling Kubernetes clusters.Option E involves using AWS App Mesh to observe network activity, which is not directly related to scaling Amazon EKS clusters.