Question 94 of 284
Single answerYou 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 kubectl to examine the status of your Pod and observe that one of them is still in Pending status:
What is the most likely cause?
What is the most likely cause?
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 schedule the pending Pod.
CThe node pool is configured with a service account that does not have permission to pull the container image used by the pending Pod.
DThe pending Pod was originally scheduled on a node that has been preempted between the creation of the Deployment and your verification of the Pods' status. It is currently being rescheduled on a new node.
✓
Correct Answer: B
Too many Pods are already running in the cluster, and there are not enough resources left to schedule the pending Pod.
▥
Explanation
The correct answer is highlighted above. Review the wording carefully, then use the next question to continue building your understanding of Google certification topics.