Exam Associate Cloud Engineer topic 1 question 182 discussion

Answer is C The key point is "ensure that the CLUSTER can scale" A- HorizontalPodAutoscaler - ensures to scale the number of pods while C- Create a GKE cluster with autoscaling enabled on the node pool. Set a minimum and maximum for the size of the node pool. ensures to scale the number of nodes in the cluster. So the answer is C.

C is the right choice... See this for reference https://cloud.google.com/architecture/best-practices-for-running-cost-effective-kubernetes-applications-on-gke#fine-tune_gke_autoscaling A- HorizontalPodAutoscaler - it is best suited for stateless workers that can spin up quickly to react to usage spikes, and shut down gracefully to avoid workload instability.

Maybe ChatGPT never had the opportunity to get the Google Cloud $300 free tier ;-) HorizontalPodAutoscaler and VerticalPodAutoscaler are good for existing pods. Can you create a new node with HorizontalPodAutoscaler or VerticalPodAutoscaler?

c

A is right ans

Answer is C: the HPA is used in for scaling a deployment (an application), but here, the question is asking to scale the cluster when new applications are being added which have different and independent deployments, we have scaling at cluster level, then at deployment level either horizontally or vertically.

In the context of deploying a new application and ensuring future scalability with minimal manual intervention, focusing on pod scalability is indeed fundamental. This is accurately addressed by option A (Deploy the application on GKE, and add a HorizontalPodAutoscaler to the deployment). However, it's also important to have node autoscaling enabled (as mentioned in option C) to ensure that the cluster can accommodate the scaling pods. Both pod and node scaling are important for a fully scalable solution, but the immediate focus when deploying a new application is typically on pod configuration and scaling.

Its A, When you first deploy your workload to a Kubernetes cluster, you may not be sure about its resource requirements and how those requirements might change depending on usage patterns, external dependencies, or other factors. Horizontal Pod autoscaling helps to ensure that your workload functions consistently in different situations, and allows you to control costs by only paying for extra capacity when you need it.

i think it is A "you want to ensure that the cluster can scale as more applications are deployed in the future."

option C

Not knowing how many pods, and like nooneknows said, chatgpt... A is correct.

Chat GPT said A is the Answer!

i believe A is the answer, you cant figure out how many nodes you will need in the future...how you gotta set a maximum

How do you set the maximum number of nodes and you do not know how you app will scale in the future? I think A is more accurate here.

less manual intervention

C is the right choice... See this for reference https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-autoscaler

C is the correct answer, you can enable the cluster autoscaling in node pool by specifying min and max node size. https://cloud.google.com/kubernetes-engine/docs/how-to/cluster-autoscaler#adding_a_node_pool_with_autoscaling