nerdexam
Google

ASSOCIATE-CLOUD-ENGINEER · Question #119

You create a Deployment with 2 replicas in a Google Kubernetes Engine cluster that has a single preemptible node pool. After a few minutes, you use to examine the status of your Pod kubectl and observ

The correct answer is B. Too many Pods are already running in the cluster, and there are not enough resources left to. Reasons for a Pod Status Pending: Troubleshooting Reason #1: Not enough CPU Troubleshooting Reason #2: Not enough memory Troubleshooting Reason #3: Not enough CPU and memory https://managedkube.com/kubernetes/k8sbot/troubleshooting/pending/pod/2019/02/22/pending-

Submitted by khalil_dz· Mar 30, 2026Ensuring successful operation of a cloud solution

Question

You create a Deployment with 2 replicas in a Google Kubernetes Engine cluster that has a single preemptible node pool. After a few minutes, you use to examine the status of your Pod kubectl and observe that one of them is still in status: Pending What is the most likely cause?

Options

  • AThe pending Pod's resource requests are too large to fit on a single node of the cluster.
  • BToo many Pods are already running in the cluster, and there are not enough resources left to
  • CThe node pool is configured with a service account that does not have permission to pull the
  • DThe pending Pod was originally scheduled on a node that has been preempted between the

How the community answered

(70 responses)
  • A
    21% (15)
  • B
    64% (45)
  • C
    6% (4)
  • D
    9% (6)

Explanation

Reasons for a Pod Status Pending: Troubleshooting Reason #1: Not enough CPU Troubleshooting Reason #2: Not enough memory Troubleshooting Reason #3: Not enough CPU and memory https://managedkube.com/kubernetes/k8sbot/troubleshooting/pending/pod/2019/02/22/pending-

Topics

#GKE#preemptible nodes#pod scheduling#resource exhaustion

Community Discussion

No community discussion yet for this question.

Full ASSOCIATE-CLOUD-ENGINEER Practice