Exam Professional Cloud Architect topic 1 question 186 discussion

A: Is not necessary because you can have multiple node pools with different configurations. B: Optimizes resource usage of CPU/memory in your existing node pool but does not necessarily improve cost - still an option that should be considered. C: This looks really good. Autoscaling workloads and the node pools makes your whole infrastructure more elastic and gives you the option to rely on the same node pool. D: This might not be a good option for every type of workload. Batch and stateless workloads can often handle this quite well, but stateful workloads are not well-suited for operation on preemptible VMs. Since only one answer is accepted, I'll choose C.

C is the correct answer as it doesn't involve major changes to the current Kubernetes configuration

The correct answer is C. Configure a HorizontalPodAutoscaler for all stateless workloads and for all compatible stateful workloads. Configure the cluster to use node auto scaling. Explanation By implementing horizontal pod autoscaling, your cluster will adjust the number of pod replicas based on current demand. In tandem with node autoscaling, the GKE cluster can automatically add or remove nodes based on overall utilization. This means that during periods of low workload, the cluster can scale down—reducing the number of nodes and therefore lowering costs—while still maintaining the necessary capacity to handle peak loads without compromising availability. This approach optimizes resource usage across the cluster, making it cost effective for mixed workloads.

It uses Google features

Vote for C. In B limits could compromise availability.

Answer C. Use HorizontalPodAutoscaler.

HorizontalPodAutoscaler is the way

c is good

The correct answer is C: Configure a HorizontalPodAutoscaler for all stateless workloads and for all compatible stateful workloads. Configure the cluster to use node auto scaling. One way to reduce the cost of a Google Kubernetes Engine (GKE) cluster without compromising availability is to use horizontal pod autoscalers (HPA) and node auto scaling. HPA allows you to automatically scale the number of Pods in a deployment based on the resource usage of the Pods. By configuring HPA for stateless workloads and for compatible stateful workloads, you can ensure that the number of Pods is automatically adjusted based on the actual resource usage, which can help to reduce costs. Node auto scaling allows you to automatically add or remove nodes from the node pool based on the resource usage of the cluster. By configuring node auto scaling, you can ensure that the cluster has the minimum number of nodes needed to meet the resource requirements of the workloads, which can also help to reduce costs.

C is the correct answer as it doesn't involve major changes to the current Kubernetes configuration

C is ok

C is correct

C is correc

Configure a HorizontalPodAutoscaler for all stateless workloads and for all compatible stateful workloads. Configure the cluster to use node auto scaling

Option C is correct. Since, the company does not want to compromise availability of the application so, HPA is suitable option for autoscaling pods. Keeping the cost optimization in mind, nodes of the GKE cluster also needs to be autoscaled. Therefore, the correct option is, C. Configure a HorizontalPodAutoscaler for all stateless workloads and for all compatible stateful workloads. Configure the cluster to use node auto scaling.