Your GKE cluster is running out of resources, and new pods are stuck in the `Pending` state. You are using a Standard GKE cluster. Which TWO actions could resolve this issue? (Select TWO)

Answer options:

Enable cluster autoscaling on the node pool.

Enable Horizontal Pod Autoscaling (HPA).

Manually resize the node pool to add more nodes.

Restart the pending pods.

Change the Service type to LoadBalancer.

How to approach this question

Identify the mechanisms for adding compute capacity (nodes) to a GKE cluster.

Full Answer

Pods remain in the `Pending` state when the Kubernetes scheduler cannot find a node with enough available CPU or memory to run them. To fix this, you must add more compute capacity. You can do this manually by resizing the node pool (`gcloud container clusters resize`), or automatically by enabling the Cluster Autoscaler, which watches for pending pods and provisions new nodes.

Common mistakes

Selecting Horizontal Pod Autoscaler (HPA), which scales pods, not nodes.

Question 34 All questions Question 36

Practice the full GCP Associate Cloud Engineer Practice Exam 1

50 questions · hints · full answers · grading

More questions from this exam

Q01What is the highest level of the Google Cloud resource hierarchy?Easy Q02You need to enable the Compute Engine API in a new project using the command line. Which command ...Easy Q03You are setting up a new GCP environment. You need to grant a group of developers access to view ...Medium Q04You want to receive an email notification when your GCP spending exceeds $1000 this month. What s...Easy Q05You need to analyze your GCP billing data using complex SQL queries to understand cost trends acr...Medium

View all 50 questions →