
Ultimate access to all questions.
As a lead DevOps engineer at a cloud-based startup, you've deployed an application on a Google Kubernetes Engine cluster featuring a single preemptible node pool. Upon executing the command kubectl get pods -l app=helloworld, you observe that one of the two replicas in your deployment is in a Running status while the other remains Pending. What could be the underlying cause of this issue?
A
The pending Pod is requesting more resources than what's available on any single node in the cluster.
B
The cluster's current resource usage is too high, leaving insufficient resources to schedule the pending Pod.
C
The node pool's service account lacks the necessary permissions to pull the container images required by the pending Pod.
D
The pending Pod was scheduled on a preemptible node that has been preempted and is awaiting rescheduling on a new node.