cert
cert-1
cert-2

Pass Google Associate Cloud Engineer Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
Associate Cloud Engineer Exam - Verified By Experts
Associate Cloud Engineer Premium Bundle
$29.98

Associate Cloud Engineer Premium Bundle

$79.99
$109.97
  • Premium File 391 Questions & Answers. Last update: Nov 10, 2026
  • Training Course 234 Video Lectures
  • Study Guide 849 Pages
 
$109.97
$79.99
accept 42 downloads in last 7 days
block-screenshots
Purchase Google Associate Cloud Engineer Exam Training Products Individually
Google Associate Cloud Engineer Premium File
Premium File 391 Q&A
$76.99$69.99
Google Associate Cloud Engineer Video Training Course
Training Course 234 Lectures
$21.99 $19.99
Google Associate Cloud Engineer PDF Study Guide
Study Guide 849 Pages
$21.99 $19.99
Google Associate Cloud Engineer Practice Test 45

Question 440

A team rotates node-pool service-account credentials but new nodes can no longer read authorized Artifact Registry images. What should be verified?

  1. Grant read access to the appropriate GKE image-pull identity at the target Artifact Registry repository and validate repository path.
  2. Restore least-privilege registry-reading permission to the new node identity and validate image pulls in a safe node-pool rollout.
  3. Move the VM to a different billing account and assume its scheduling and storage behavior changes.
  4. Restart the instance repeatedly while leaving the underlying error or missing dependency in place.

Explanation

Correct Answer

B:

GKE node identity and workload identity have different duties; removing node registry access can break container startup.

Incorrect Answers

A:

The proposed setting does not correct the stated machine, disk or scheduling requirement. The necessary distinction is the actual compute scheduling or resource condition. The appropriate action here is: Restore least-privilege registry-reading permission to the new node identity and validate image pulls in a safe node-pool rollout.

C:

Billing changes payment responsibility, not the technical behavior of this workload. The case instead depends on the actual compute scheduling or resource condition. The appropriate action here is: Restore least-privilege registry-reading permission to the new node identity and validate image pulls in a safe node-pool rollout.

D:

The proposed setting does not correct the stated machine, disk or scheduling requirement. It leaves the actual compute scheduling or resource condition unaddressed. The appropriate action here is: Restore least-privilege registry-reading permission to the new node identity and validate image pulls in a safe node-pool rollout.

Question 441

A GKE Standard cluster auto-upgrades its control plane, while an old third-party controller fails because its API client is incompatible. What should the team maintain?

  1. Set an approved control-plane authorized-network or private endpoint access path under the supported GKE networking mode.
  2. Validate controller compatibility against the supported Kubernetes release channel and pin a supported controller version before changes.
  3. Allow the old third-party Kubernetes controller to run through the control-plane upgrade without compatibility checks.
  4. Disable the cluster health checks and treat missing readiness as a successful deployment.

Explanation

Correct Answer

B:

Managed control-plane upgrades do not make all in-cluster controllers automatically compatible with new API versions.

Incorrect Answers

A:

Network settings and service or application controls must be distinguished. The case instead depends on the Kubernetes workload or scheduling control. The appropriate action here is: Validate controller compatibility against the supported Kubernetes release channel and pin a supported controller version before changes.

C:

The controller could break against changed Kubernetes APIs; compatibility needs validation before rollout.

D:

Deploying a separate workload does not automatically configure the existing feature. The specific requirement concerns the Kubernetes workload or scheduling control.

Question 442

A GKE application uses Kubernetes Secrets stored in etcd, but a policy requires customer-managed envelope keys for secret encryption. Which platform configuration should be evaluated?

  1. Set an approved control-plane authorized-network or private endpoint access path under the supported GKE networking mode.
  2. Enable a supported application-layer secret encryption approach with Cloud KMS keys where required and verify key accessibility.
  3. Change only the container image tag and assume a networking or policy failure is repaired.
  4. Disable the cluster health checks and treat missing readiness as a successful deployment.

Explanation

Correct Answer

B:

Kubernetes secret data protection may require configured KMS integration in addition to default storage encryption.

Incorrect Answers

A:

Network settings and service or application controls must be distinguished. It leaves the Kubernetes workload or scheduling control unaddressed. The appropriate action here is: Enable a supported application-layer secret encryption approach with Cloud KMS keys where required and verify key accessibility.

C:

Network settings and service or application controls must be distinguished. The specific requirement concerns the Kubernetes workload or scheduling control.

D:

Deploying a separate workload does not automatically configure the existing feature. The necessary distinction is the Kubernetes workload or scheduling control.

Question 443

A workload has reached a new container image version, but a rolling Deployment still serves previous image Pods because the rollout is paused. What command-level action is appropriate?

  1. Inspect rollout status and resume the paused Deployment only after validating the new revision and available replicas.
  2. Deploy using immutable image digests or versioned tags and keep previous proven images available for rollback.
  3. Change the instance display name as a replacement for modifying the actual machine or disk.
  4. Create a snapshot only and assume it immediately changes the live VM capacity.

Explanation

Correct Answer

A:

Kubernetes deployment pauses halt further rollout changes; editing the image field does not automatically resume a paused rollout.

Incorrect Answers

B:

The proposed setting does not correct the stated machine, disk or scheduling requirement. The specific requirement concerns the actual compute scheduling or resource condition. The appropriate action here is: Inspect rollout status and resume the paused Deployment only after validating the new revision and available replicas.

C:

Display names and labels identify resources; they do not enforce their runtime behavior. The necessary distinction is the actual compute scheduling or resource condition. The appropriate action here is: Inspect rollout status and resume the paused Deployment only after validating the new revision and available replicas.

D:

Snapshots are recovery artifacts and do not directly reconfigure a running resource. The case instead depends on the actual compute scheduling or resource condition. The appropriate action here is: Inspect rollout status and resume the paused Deployment only after validating the new revision and available replicas.

Question 444

A GKE namespace's ResourceQuota blocks adding a new replica even though the cluster has spare nodes. What constraint is actually binding?

  1. Verify the kubectl cluster context and specify the payments namespace explicitly when listing or modifying the Deployment.
  2. Disable the cluster health checks and treat missing readiness as a successful deployment.
  3. Review namespace ResourceQuota and LimitRange usage and adjust approved namespace quotas rather than scaling nodes alone.
  4. Move all Pods to the default namespace and assume this repairs scheduling and authorization.

Explanation

Correct Answer

C:

Namespace admission constraints limit aggregate requests independently of physical cluster spare capacity.

Incorrect Answers

A:

Deploying a separate workload does not automatically configure the existing feature. The necessary distinction is the Kubernetes workload or scheduling control. The appropriate action here is: Review namespace ResourceQuota and LimitRange usage and adjust approved namespace quotas rather than scaling nodes alone.

B:

Deploying a separate workload does not automatically configure the existing feature. The case instead depends on the Kubernetes workload or scheduling control.

D:

Changing an unrelated Pod setting leaves the stated cloud feature unresolved. It leaves the Kubernetes workload or scheduling control unaddressed.

Question 445

A GKE release uses a Job with restartPolicy Always and Kubernetes rejects the manifest. Which correction addresses the workload controller requirement?

  1. Use an allowed Job pod restart policy such as Never or OnFailure and keep the controller's retry/backoff settings consistent.
  2. Use Kubernetes Job TTL-after-finished or a governed cleanup policy for completed work and associated Pods.
  3. Change only the container image tag and assume a networking or policy failure is repaired.
  4. Use a public LoadBalancer Service for an internal-only issue instead of fixing its actual boundary.

Explanation

Correct Answer

A:

Kubernetes Jobs are designed for finite work and have restart-policy restrictions that differ from Deployment Pods.

Incorrect Answers

B:

Changing an unrelated Pod setting leaves the stated cloud feature unresolved. The case instead depends on the Kubernetes workload or scheduling control. The appropriate action here is: Use an allowed Job pod restart policy such as Never or OnFailure and keep the controller's retry/backoff settings consistent.

C:

Network settings and service or application controls must be distinguished. It leaves the Kubernetes workload or scheduling control unaddressed. The appropriate action here is: Use an allowed Job pod restart policy such as Never or OnFailure and keep the controller's retry/backoff settings consistent.

D:

This changes a neighboring Kubernetes feature, not the stated control. The specific requirement concerns the Kubernetes workload or scheduling control.

Question 446

A DaemonSet agent for log collection runs only on some nodes because newer managed node pools have extra taints. What should the operator examine?

  1. Review DaemonSet tolerations, node selectors and intended eligible pools before allowing deployment to those nodes.
  2. Track model token quotas, concurrent sessions and downstream tool rate limits alongside runtime resource metrics.
  3. Give the agent project Owner instead of configuring its supported runtime identity and tool access.
  4. Make every agent tool publicly callable to avoid the required access-policy configuration.

Explanation

Correct Answer

A:

DaemonSets schedule per eligible node; taints and selectors can prevent an agent from covering all required nodes.

Incorrect Answers

B:

The suggested action changes another component without meeting the main requirement. It leaves the managed agent feature or authorization unaddressed. The appropriate action here is: Review DaemonSet tolerations, node selectors and intended eligible pools before allowing deployment to those nodes.

C:

Project Owner broadens authorization and is not an appropriate substitute for the named control. The specific requirement concerns the managed agent feature or authorization.

D:

Public access expands exposure without meeting the requested scoped-control requirement. The necessary distinction is the managed agent feature or authorization.

Question 447

A cluster reaches storage quota because completed Jobs retain thousands of successful pods for months. What housekeeping should be enabled?

  1. Choose an appropriate CronJob concurrencyPolicy and starting deadline behavior for the workload's expected duration.
  2. Use a public LoadBalancer Service for an internal-only issue instead of fixing its actual boundary.
  3. Disable the cluster health checks and treat missing readiness as a successful deployment.
  4. Use Kubernetes Job TTL-after-finished or a governed cleanup policy for completed work and associated Pods.

Explanation

Correct Answer

D:

Completed Job history can accumulate controller and pod objects unless lifecycle cleanup is configured.

Incorrect Answers

A:

This changes a neighboring Kubernetes feature, not the stated control. The specific requirement concerns the Kubernetes workload or scheduling control. The appropriate action here is: Use Kubernetes Job TTL-after-finished or a governed cleanup policy for completed work and associated Pods.

B:

This changes a neighboring Kubernetes feature, not the stated control. The necessary distinction is the Kubernetes workload or scheduling control. The appropriate action here is: Use Kubernetes Job TTL-after-finished or a governed cleanup policy for completed work and associated Pods.

C:

Deploying a separate workload does not automatically configure the existing feature. The case instead depends on the Kubernetes workload or scheduling control. The appropriate action here is: Use Kubernetes Job TTL-after-finished or a governed cleanup policy for completed work and associated Pods.

Question 448

A production service's ingress returns 404 for one route after a manifest change, but direct Pod requests work. Which configuration should be checked?

  1. Enable a supported application-layer secret encryption approach with Cloud KMS keys where required and verify key accessibility.
  2. Change only the container image tag and assume a networking or policy failure is repaired.
  3. Grant the GKE node service account project Owner to bypass the workload-specific issue.
  4. Verify Ingress/HTTPRoute host and path matching and backend service references, then redeploy the reviewed routing rule.

Explanation

Correct Answer

D:

Layer-7 ingress rules select backends by host and path; backend health alone cannot fix mismatched route configuration.

Incorrect Answers

A:

This changes a neighboring Kubernetes feature, not the stated control. The necessary distinction is the intended ingress boundary.

B:

Network settings and service or application controls must be distinguished. The case instead depends on the intended ingress boundary.

C:

Project Owner broadens authorization and is not an appropriate substitute for the named control. It leaves the intended ingress boundary unaddressed.

Question 449

An API rollout needs every new Pod to have enough resources before a Deployment scales down old pods, but it currently causes an outage at each upgrade. What rollout settings matter?

  1. Review deprecation insights and migrate manifests/controllers to supported APIs before the control-plane upgrade.
  2. Recreate the node pool without preserving the necessary workload identity or configuration.
  3. Configure a safe Deployment rollingUpdate strategy with suitable maxSurge/maxUnavailable and health probes.
  4. Use a public LoadBalancer Service for an internal-only issue instead of fixing its actual boundary.

Explanation

Correct Answer

C:

Rolling-update capacity and readiness settings govern how many serving replicas remain during a version change.

Incorrect Answers

A:

This changes a neighboring Kubernetes feature, not the stated control. The case instead depends on the Kubernetes workload or scheduling control. The appropriate action here is: Configure a safe Deployment rollingUpdate strategy with suitable maxSurge/maxUnavailable and health probes.

B:

Changing node pools alone cannot substitute for the specified workload-level control. It leaves the Kubernetes workload or scheduling control unaddressed.

D:

This changes a neighboring Kubernetes feature, not the stated control. The specific requirement concerns the Kubernetes workload or scheduling control. The appropriate action here is: Configure a safe Deployment rollingUpdate strategy with suitable maxSurge/maxUnavailable and health probes.

Question 450

A GKE cluster's control plane is reachable publicly despite a requirement that administrator access use authorized network boundaries. What should be configured?

  1. Validate controller compatibility against the supported Kubernetes release channel and pin a supported controller version before changes.
  2. Disable the cluster health checks and treat missing readiness as a successful deployment.
  3. Grant the GKE node service account project Owner to bypass the workload-specific issue.
  4. Set an approved control-plane authorized-network or private endpoint access path under the supported GKE networking mode.

Explanation

Correct Answer

D:

Kubernetes API access needs its own network and IAM protection; private workload subnets alone do not secure the control-plane endpoint.

Incorrect Answers

A:

This changes a neighboring Kubernetes feature, not the stated control. It leaves the Kubernetes workload or scheduling control unaddressed.

B:

Deploying a separate workload does not automatically configure the existing feature. The specific requirement concerns the Kubernetes workload or scheduling control. The appropriate action here is: Set an approved control-plane authorized-network or private endpoint access path under the supported GKE networking mode.

C:

Project Owner broadens authorization and is not an appropriate substitute for the named control. The necessary distinction is the Kubernetes workload or scheduling control.

Associate Cloud Engineer Practice Tests