Question 180
An engineer wants to see why a newly created Kubernetes Pod remains Pending. What should the administrator do?
- Run kubectl apply -f against the manifest
- Create a GKE Standard cluster
- Run gcloud container clusters get-credentials for that cluster
- Use kubectl describe pod and inspect scheduling events
- Inspect kubectl config current-context and relevant context settings
Explanation
Correct Answer
D:Pod descriptions include status conditions and events such as insufficient resources or unsatisfied node constraints. A service URL alone does not reveal scheduler decisions.
Incorrect Answers
A:The tool can apply a Kubernetes declarative manifest, but it cannot be substituted for the capability needed to diagnose a Pending Pod. Its operational effect is not equivalent.
B:An operator would use this action to configure Kubernetes node infrastructure directly, chiefly when trying to choose detailed cluster node control; The current requirement is to diagnose a Pending Pod, which remains unresolved by that operation.
C:It can populate kubeconfig with GKE cluster access; however, it does not provide the specific operation to diagnose a Pending Pod. The two controls serve different purposes.
E:This choice is useful to inspect the active kubectl context. The stated task is to diagnose a Pending Pod, which requires a different mechanism or permission scope.
Question 181
A team wants Kubernetes workloads but prefers Google to manage the node infrastructure and many cluster operations. Which solution should be used?
- Choose a zonal GKE cluster
- Create a GKE Autopilot cluster
- Create a GKE Standard cluster
- Choose a regional GKE cluster
Explanation
Correct Answer
B:Autopilot manages node provisioning and configuration around workload requests under its constraints. Teams remain responsible for defining Pods and application behavior.
Incorrect Answers
A:This approach can deploy a zonal GKE control plane. The requirement is to reduce Kubernetes node operations, so it controls a different part of the workflow and leaves that result unaddressed.
C:Administrators use it to configure Kubernetes node infrastructure directly, rather than to reduce Kubernetes node operations. Applying it would change the wrong component of this deployment.
D:While this can increase GKE control plane zonal resilience, the present task requires an action to reduce Kubernetes node operations. This operation does not supply the behavior described in the requirements.
Question 182
A platform team must control node pools, machine types, and more cluster infrastructure settings. How should the team proceed?
- Create a GKE Autopilot cluster
- Create a GKE Standard cluster
- Choose a regional GKE cluster
- Choose a zonal GKE cluster
- Run gcloud container clusters get-credentials for that cluster
Explanation
Correct Answer
B:GKE Standard exposes more responsibility and configurability for node pools and scaling choices. It suits workloads that require supported node-level control.
Incorrect Answers
A:It can use managed GKE workload infrastructure; however, it does not provide the specific operation to choose detailed cluster node control. The two controls serve different purposes.
C:The tool can increase GKE control plane zonal resilience, but it cannot be substituted for the capability needed to choose detailed cluster node control. Its operational effect is not equivalent.
D:Select this when the goal is to deploy a zonal GKE control plane. Here the decisive requirement is to choose detailed cluster node control, and that outcome is not achieved by this action.
E:This proposal can populate kubeconfig with GKE cluster access, but the failure or goal described here calls for a way to choose detailed cluster node control; It changes the wrong control or scope for the requested outcome.
Question 183
An HA requirement favors a GKE control plane deployed across multiple zones within a region. What is the most direct solution?
- Create a GKE Standard cluster
- Choose a zonal GKE cluster
- Choose a regional GKE cluster
- Create an appropriately configured private GKE cluster or private nodes
- Create a GKE Autopilot cluster
Explanation
Correct Answer
C:A regional cluster replicates the control plane across zones in its region. Workload distribution still depends on node placement and scheduling.
Incorrect Answers
A:This approach can configure Kubernetes node infrastructure directly. The requirement is to protect the Kubernetes API against one zone outage, so it controls a different part of the workflow and leaves that result unaddressed.
B:This setting would deploy a zonal GKE control plane. That behavior does not establish the requested ability to protect the Kubernetes API against one zone outage; it addresses an adjacent concern instead.
D:An operator would use this action to run GKE nodes using private addresses, chiefly when trying to avoid public node IPs; The current requirement is to protect the Kubernetes API against one zone outage, which remains unresolved by that operation.
E:Using this action would use managed GKE workload infrastructure, not protect the Kubernetes API against one zone outage. Its function is different from the specific change described in the scenario.
Question 184
A small test cluster is allowed to have zonal control plane placement rather than regional redundancy. Which implementation matches this requirement?
- Create a GKE Standard cluster
- Create a ClusterIP Kubernetes Service
- Choose a zonal GKE cluster
- Create a GKE Autopilot cluster
- Choose a regional GKE cluster
Explanation
Correct Answer
C:Zonal clusters place the control plane in a selected zone, so their failure-domain exposure differs from regional clusters. The choice can suit lower-criticality workloads.
Incorrect Answers
A:This mechanism is intended to configure Kubernetes node infrastructure directly. It does not implement the required action to build a lower-resilience test cluster, even though both are relevant to the same general service.
B:For the stated need to build a lower-resilience test cluster, this would instead provide cluster-internal service discovery; it supports the separate task to expose Pods only within Kubernetes, not the required configuration.
D:The result of this choice would be to use managed GKE workload infrastructure. The requested outcome, to build a lower-resilience test cluster, is handled at a different layer or through another operation.
E:Select this when the goal is to increase GKE control plane zonal resilience. Here the decisive requirement is to build a lower-resilience test cluster, and that outcome is not achieved by this action.
Question 185
A security architecture requires GKE nodes without external IPv4 addresses. Which action is most appropriate?
- Create an appropriately configured private GKE cluster or private nodes
- Configure private control plane endpoint access with suitable routing and permissions
- Allocate appropriate secondary subnet ranges for GKE VPC-native networking
- Provide supported private outbound connectivity, such as Cloud NAT, for required image sources
Explanation
Correct Answer
A:Private nodes use internal addresses and avoid assigning external IPs to cluster nodes. Authorized control plane access and outbound dependencies still need design.
Incorrect Answers
B:Using this action would reach the GKE control plane over private networks, not avoid public node IPs. Its function is different from the specific change described in the scenario.
C:It can assign secondary ranges to Pod and Service addresses; however, it does not provide the specific operation to avoid public node IPs. The two controls serve different purposes.
D:This choice is useful to enable private node outbound traffic for dependencies. The stated task is to avoid public node IPs, which requires a different mechanism or permission scope.
Question 186
A restricted GKE environment needs a private endpoint for control plane access from connected authorized networks. Which solution should be used?
- Allocate appropriate secondary subnet ranges for GKE VPC-native networking
- Configure private control plane endpoint access with suitable routing and permissions
- Deploy Compute Engine virtual machines
- Create an appropriately configured private GKE cluster or private nodes
- Provide supported private outbound connectivity, such as Cloud NAT, for required image sources
Explanation
Correct Answer
B:The cluster API endpoint can be configured for private access. Client connectivity must originate from a network with an allowed route and appropriate authentication.
Incorrect Answers
A:Its purpose is to assign secondary ranges to Pod and Service addresses. That distinction matters: the scenario calls for an action to restrict Kubernetes API network access, not this separate configuration task.
C:This mechanism is intended to run and administer virtual machine operating systems. It does not implement the required action to restrict Kubernetes API network access, even though both are relevant to the same general service.
D:Administrators use it to run GKE nodes using private addresses, rather than to restrict Kubernetes API network access. Applying it would change the wrong component of this deployment.
E:The result of this choice would be to enable private node outbound traffic for dependencies. The requested outcome, to restrict Kubernetes API network access, is handled at a different layer or through another operation.
Question 187
A new private cluster cannot pull external images because its nodes lack an internet egress path. How should the team proceed?
- Choose a zonal GKE cluster
- Create an appropriately configured private GKE cluster or private nodes
- Provide supported private outbound connectivity, such as Cloud NAT, for required image sources
- Allocate appropriate secondary subnet ranges for GKE VPC-native networking
- Configure private control plane endpoint access with suitable routing and permissions
Explanation
Correct Answer
C:Private nodes need a permitted path to external registries when images are not available through supported private Google access. Network egress is separate from image pull IAM.
Incorrect Answers
A:For the stated need to restore image downloads from external registries, this would instead deploy a zonal GKE control plane; it supports the separate task to build a lower-resilience test cluster, not the required configuration.
B:This choice is useful to run GKE nodes using private addresses. The stated task is to restore image downloads from external registries, which requires a different mechanism or permission scope.
D:Select this when the goal is to assign secondary ranges to Pod and Service addresses. Here the decisive requirement is to restore image downloads from external registries, and that outcome is not achieved by this action.
E:The tool can reach the GKE control plane over private networks, but it cannot be substituted for the capability needed to restore image downloads from external registries. Its operational effect is not equivalent.
Question 188
A network team wants the GKE cluster's Pod IP ranges isolated from ordinary primary subnet addresses. What is the most direct solution?
- Allocate appropriate secondary subnet ranges for GKE VPC-native networking
- Provide supported private outbound connectivity, such as Cloud NAT, for required image sources
- Create a GKE Autopilot cluster
- Create an appropriately configured private GKE cluster or private nodes
- Configure private control plane endpoint access with suitable routing and permissions
Explanation
Correct Answer
A:VPC-native clusters use alias IP secondary ranges for Pods and Services as configured. Capacity planning must include both node and Pod address needs.
Incorrect Answers
B:While this can enable private node outbound traffic for dependencies, the present task requires an action to plan GKE IP address allocation. This operation does not supply the behavior described in the requirements.
C:In a workflow for gke cluster operating modes, it can use managed GKE workload infrastructure; This question instead asks how to plan GKE IP address allocation; substituting the former action would leave that distinct technical requirement unmet.
D:Its purpose is to run GKE nodes using private addresses. That distinction matters: the scenario calls for an action to plan GKE IP address allocation, not this separate configuration task.
E:This approach can reach the GKE control plane over private networks. The requirement is to plan GKE IP address allocation, so it controls a different part of the workflow and leaves that result unaddressed.
Question 189
An application should maintain a chosen number of interchangeable stateless Pod replicas. What should be configured?
- Create a DaemonSet
- Create a Kubernetes Deployment
- Create a Kubernetes Job
- Create a Kubernetes StatefulSet
Explanation
Correct Answer
B:Deployments manage ReplicaSets and support declarative updates for stateless workloads. Their Pods are replaceable and do not have stable ordinal identities by default.
Incorrect Answers
A:The tool can schedule one Pod on each selected node, but it cannot be substituted for the capability needed to deploy a scalable stateless service. Its operational effect is not equivalent.
C:The result of this choice would be to run finite Kubernetes workloads. The requested outcome, to deploy a scalable stateless service, is handled at a different layer or through another operation.
D:This mechanism is intended to manage stable Pod identities. It does not implement the required action to deploy a scalable stateless service, even though both are relevant to the same general service.
Question 190
A clustered database requires stable Pod identities and ordered deployment semantics. Which action is most appropriate?
- Create a managed instance group from an instance template
- Create a Kubernetes StatefulSet
- Create a Kubernetes Deployment
- Create a DaemonSet
- Create a Kubernetes Job
Explanation
Correct Answer
B:StatefulSets provide stable identities and ordered operations for stateful applications. Storage persistence still requires suitable persistent volumes.
Incorrect Answers
A:For the stated need to orchestrate a stateful cluster, this would instead maintain self-healing identical VM replicas; it supports the separate task to replace unhealthy stateless compute instances, not the required configuration.
C:This approach can maintain stateless Pod replicas. The requirement is to orchestrate a stateful cluster, so it controls a different part of the workflow and leaves that result unaddressed.
D:This setting would schedule one Pod on each selected node. That behavior does not establish the requested ability to orchestrate a stateful cluster; it addresses an adjacent concern instead.
E:This choice is useful to run finite Kubernetes workloads. The stated task is to orchestrate a stateful cluster, which requires a different mechanism or permission scope.