Google Associate Cloud Engineer Practice Test 39

Question 380

A workload receives no traffic because its Kubernetes Service has no selected endpoints. What is the most direct solution?

  1. Update the Deployment image reference to an existing valid tag or immutable digest
  2. Check Service selectors against Pod labels and readiness
  3. Read the Pod's current and previous container logs and describe its status
  4. Inspect scheduler events and node resource requests or capacity
  5. Run kubectl get services in the relevant namespace

Explanation

Correct Answer

B:

A Service selects Pods through labels, with readiness affecting endpoint availability. A healthy load balancer cannot route to absent service endpoints.

Incorrect Answers

A:

This approach can correct a nonexistent container image reference. The requirement is to restore Kubernetes backend endpoints, so it controls a different part of the workflow and leaves that result unaddressed.

C:

Its purpose is to diagnose repeated Kubernetes container crashes. That distinction matters: the scenario calls for an action to restore Kubernetes backend endpoints, not this separate configuration task.

D:

While this can diagnose scheduling resource insufficiency, the present task requires an action to restore Kubernetes backend endpoints. This operation does not supply the behavior described in the requirements.

E:

In a workflow for gke cluster inventory operations, it can list Kubernetes Service endpoints; This question instead asks how to restore Kubernetes backend endpoints; substituting the former action would leave that distinct technical requirement unmet.

Question 381

A CI pipeline needs a private destination for built Docker-compatible images used by GKE. What should be configured?

  1. Grant an appropriate Artifact Registry writer role to the build identity
  2. List artifacts and tags in the selected Artifact Registry repository
  3. Grant the relevant node or workload pull identity appropriate Artifact Registry reader access
  4. Create a Docker repository in Artifact Registry and push the images

Explanation

Correct Answer

D:

Artifact Registry hosts versioned container images and artifacts. Permissions govern which build and deployment identities can push or pull.

Incorrect Answers

A:

This mechanism is intended to authorize CI image upload. It does not implement the required action to publish CI-built images for GKE, even though both are relevant to the same general service.

B:

The result of this choice would be to inspect registry image versions. The requested outcome, to publish CI-built images for GKE, is handled at a different layer or through another operation.

C:

The tool can authorize image pulls from Artifact Registry, but it cannot be substituted for the capability needed to publish CI-built images for GKE. Its operational effect is not equivalent.

Question 382

A GKE cluster cannot pull images from a private Artifact Registry repository. Which action is most appropriate?

  1. Grant an appropriate Artifact Registry writer role to the build identity
  2. List artifacts and tags in the selected Artifact Registry repository
  3. Grant appropriate image access to the target project principals
  4. Grant the relevant node or workload pull identity appropriate Artifact Registry reader access
  5. Create a Docker repository in Artifact Registry and push the images

Explanation

Correct Answer

D:

Image pulls use the identities and mechanisms supported by the cluster setup. The right repository permissions are required independently of Kubernetes manifest validity.

Incorrect Answers

A:

This setting would authorize CI image upload. That behavior does not establish the requested ability to permit private registry access; it addresses an adjacent concern instead.

B:

This approach can inspect registry image versions. The requirement is to permit private registry access, so it controls a different part of the workflow and leaves that result unaddressed.

C:

For the stated need to permit private registry access, this would instead share a custom Compute Engine image; it supports the separate task to reuse a vetted machine image across projects, not the required configuration.

E:

Using this action would store container images in a private registry, not permit private registry access. Its function is different from the specific change described in the scenario.

Question 383

A build pipeline can push an image but lacks permission in the target Artifact Registry repository. Which solution should be used?

  1. Grant the relevant node or workload pull identity appropriate Artifact Registry reader access
  2. Use appropriate node labels and Pod node selectors or affinity
  3. Grant an appropriate Artifact Registry writer role to the build identity
  4. Create a Docker repository in Artifact Registry and push the images
  5. List artifacts and tags in the selected Artifact Registry repository

Explanation

Correct Answer

C:

Repository IAM controls push operations. Giving a GKE Pod a runtime service role does not necessarily authorize the separate CI publisher.

Incorrect Answers

A:

The result of this choice would be to authorize image pulls from Artifact Registry. The requested outcome, to fix denied container image push, is handled at a different layer or through another operation.

B:

In a workflow for gke node pool management, it can schedule Pods onto a chosen node pool; This question instead asks how to fix denied container image push; substituting the former action would leave that distinct technical requirement unmet.

D:

While this can store container images in a private registry, the present task requires an action to fix denied container image push. This operation does not supply the behavior described in the requirements.

E:

Administrators use it to inspect registry image versions, rather than to fix denied container image push. Applying it would change the wrong component of this deployment.

Question 384

An operator wants to identify available image tags and digests before updating a deployment. How should the team proceed?

  1. Grant an appropriate Artifact Registry writer role to the build identity
  2. Use gcloud compute ssh over a direct reachable address with appropriate access
  3. List artifacts and tags in the selected Artifact Registry repository
  4. Create a Docker repository in Artifact Registry and push the images
  5. Grant the relevant node or workload pull identity appropriate Artifact Registry reader access

Explanation

Correct Answer

C:

Artifact Registry tracks package versions and immutable content digests. Inspecting the registry helps choose the intended release artifact.

Incorrect Answers

A:

Using this action would authorize CI image upload, not select the proper release image digest. Its function is different from the specific change described in the scenario.

B:

It can start a direct CLI SSH session to a VM; however, it does not provide the specific operation to select the proper release image digest. The two controls serve different purposes.

D:

This setting would store container images in a private registry. That behavior does not establish the requested ability to select the proper release image digest; it addresses an adjacent concern instead.

E:

The tool can authorize image pulls from Artifact Registry, but it cannot be substituted for the capability needed to select the proper release image digest. Its operational effect is not equivalent.

Question 385

A Standard GKE cluster needs a separate set of larger memory-optimized worker nodes. Which configuration best meets the requirement?

  1. Use the supported GKE node pool upgrade process
  2. Drain or migrate affected workloads and remove the unused node pool
  3. Add a node pool with the required supported machine configuration
  4. Use appropriate node labels and Pod node selectors or affinity

Explanation

Correct Answer

C:

Node pools group nodes with shared settings inside a Standard cluster. Distinct pools let specific workloads target specialized capacity.

Incorrect Answers

A:

Its purpose is to upgrade an existing node pool. That distinction matters: the scenario calls for an action to separate memory-heavy nodes, not this separate configuration task.

B:

This approach can delete unused GKE worker capacity. The requirement is to separate memory-heavy nodes, so it controls a different part of the workflow and leaves that result unaddressed.

D:

Administrators use it to schedule Pods onto a chosen node pool, rather than to separate memory-heavy nodes. Applying it would change the wrong component of this deployment.

Question 386

A Standard cluster must update one node pool's version with controlled disruption. What should be configured?

  1. Drain or migrate affected workloads and remove the unused node pool
  2. Use the supported GKE node pool upgrade process
  3. Enable or adjust GKE cluster autoscaling on a suitable node pool
  4. Use appropriate node labels and Pod node selectors or affinity
  5. Add a node pool with the required supported machine configuration

Explanation

Correct Answer

B:

GKE manages node pool upgrade operations with configurable maintenance and disruption considerations. Arbitrarily replacing all nodes at once is unnecessary.

Incorrect Answers

A:

This mechanism is intended to delete unused GKE worker capacity. It does not implement the required action to maintain worker node versions, even though both are relevant to the same general service.

C:

In a workflow for gke autoscaling distinctions, it can scale GKE nodes for pending replicas; This question instead asks how to maintain worker node versions; substituting the former action would leave that distinct technical requirement unmet.

D:

It can schedule Pods onto a chosen node pool; however, it does not provide the specific operation to maintain worker node versions. The two controls serve different purposes.

E:

Select this when the goal is to add specialized Kubernetes worker capacity. Here the decisive requirement is to maintain worker node versions, and that outcome is not achieved by this action.

Question 387

A cluster no longer needs its temporary GPU node pool. Which action is most appropriate?

  1. Drain or migrate affected workloads and remove the unused node pool
  2. Use appropriate node labels and Pod node selectors or affinity
  3. Use the supported GKE node pool upgrade process
  4. Add a node pool with the required supported machine configuration
  5. Run kubectl get nodes using the intended cluster context

Explanation

Correct Answer

A:

Removing a node pool deletes its worker nodes, which can disrupt Pods. Scheduling and persistent storage dependencies must be accounted for first.

Incorrect Answers

B:

This setting would schedule Pods onto a chosen node pool. That behavior does not establish the requested ability to retire a specialized node pool; it addresses an adjacent concern instead.

C:

This approach can upgrade an existing node pool. The requirement is to retire a specialized node pool, so it controls a different part of the workflow and leaves that result unaddressed.

D:

Using this action would add specialized Kubernetes worker capacity, not retire a specialized node pool. Its function is different from the specific change described in the scenario.

E:

The choice is aimed at a different purpose: to check Kubernetes nodes; Even if it can inspect cluster worker node readiness, that would not accomplish the stated requirement to retire a specialized node pool.

Question 388

A cluster has mixed node pools and a workload must run only on one of them. Which solution should be used?

  1. Inspect scheduler events and node resource requests or capacity
  2. Drain or migrate affected workloads and remove the unused node pool
  3. Use appropriate node labels and Pod node selectors or affinity
  4. Add a node pool with the required supported machine configuration
  5. Use the supported GKE node pool upgrade process

Explanation

Correct Answer

C:

Kubernetes scheduling constraints target eligible nodes by labels or other rules. A namespace alone does not select a machine type.

Incorrect Answers

A:

This alternative addresses kubernetes incident diagnostics by allowing a team to diagnose scheduling resource insufficiency; The incident, however, requires the different action to target specialized worker nodes, so its central configuration remains unchanged.

B:

This mechanism is intended to delete unused GKE worker capacity. It does not implement the required action to target specialized worker nodes, even though both are relevant to the same general service.

D:

Administrators use it to add specialized Kubernetes worker capacity, rather than to target specialized worker nodes. Applying it would change the wrong component of this deployment.

E:

Select this when the goal is to upgrade an existing node pool. Here the decisive requirement is to target specialized worker nodes, and that outcome is not achieved by this action.

Question 389

A Standard GKE cluster frequently leaves Pods Pending because its existing node pool has no free capacity. What is the best next step?

  1. Adjust resource requests and limits or use supported Vertical Pod Autoscaler recommendations
  2. Configure a Horizontal Pod Autoscaler for the workload
  3. Adjust Pod resource requests to meet Autopilot constraints
  4. Enable or adjust cluster autoscaler for the eligible node pool

Explanation

Correct Answer

D:

Cluster autoscaler adds nodes when unschedulable Pods require capacity within configured bounds. It is separate from HPA changing Pod replica counts.

Incorrect Answers

A:

This choice is useful to right-size container memory allocations. The stated task is to satisfy unschedulable Pod demand, which requires a different mechanism or permission scope.

B:

Using this action would scale Kubernetes workload replicas, not satisfy unschedulable Pod demand. Its function is different from the specific change described in the scenario.

C:

This setting would fit Pod requests to Autopilot rules. That behavior does not establish the requested ability to satisfy unschedulable Pod demand; it addresses an adjacent concern instead.

Question 390

An application needs more Pod replicas when CPU utilization rises. Which configuration best meets the requirement?

  1. Enable or adjust cluster autoscaler for the eligible node pool
  2. Enable or adjust GKE cluster autoscaling on a suitable node pool
  3. Configure a Horizontal Pod Autoscaler for the workload
  4. Adjust Pod resource requests to meet Autopilot constraints
  5. Adjust resource requests and limits or use supported Vertical Pod Autoscaler recommendations

Explanation

Correct Answer

C:

HPA adjusts Pod replica counts using selected metrics. It does not increase the CPU request of an individual existing Pod.

Incorrect Answers

A:

The result of this choice would be to scale Kubernetes worker node count. The requested outcome, to respond to service load by adding Pods, is handled at a different layer or through another operation.

B:

The choice is aimed at a different purpose: to provide capacity after workload scale-out; Even if it can scale GKE nodes for pending replicas, that would not accomplish the stated requirement to respond to service load by adding Pods.

D:

Administrators use it to fit Pod requests to Autopilot rules, rather than to respond to service load by adding Pods. Applying it would change the wrong component of this deployment.

E:

While this can right-size container memory allocations, the present task requires an action to respond to service load by adding Pods. This operation does not supply the behavior described in the requirements.

Associate Cloud Engineer Practice Tests