Medium1 markMultiple Choice
Domain 4.2: Managing GKE resourcesGKEAutoscalingDomain 4.2

GCP ACE · Question 35 · Domain 4.2: Managing GKE resources

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:

A.

Enable cluster autoscaling on the node pool.

B.

Enable Horizontal Pod Autoscaling (HPA).

C.

Manually resize the node pool to add more nodes.

D.

Restart the pending pods.

E.

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

Enable cluster autoscaling on the node pool. Manually resize the node pool to add more nodes.
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.

Practice the full GCP Associate Cloud Engineer Practice Exam 1

50 questions · hints · full answers · grading

More questions from this exam