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 79

Question 780

A GKE Pod can read Cloud Storage from one namespace but not another although both use a KSA with the same name. What access distinction matters?

  1. The new namespace/Kubernetes ServiceAccount forms a different workload principal; recreate the approved identity or update its scoped IAM binding.
  2. Reuse the default Compute Engine service account for every unrelated workload.
  3. Allow tokens from any issuer without verifying audience, signature or mapped principal.
  4. Bind IAM permissions to the specific namespace-qualified workload principal rather than assuming a KSA name is globally unique.

Explanation

Correct Answer

D:

Kubernetes ServiceAccount names are namespace-scoped; equal names in different namespaces represent different workload identities.

Incorrect Answers

A:

The suggestion does not establish the required issuer, principal or permission boundary. The necessary distinction is the required Cloud Storage behavior.

B:

The suggestion does not establish the required issuer, principal or permission boundary. The case instead depends on the required Cloud Storage behavior.

C:

The suggestion does not establish the required issuer, principal or permission boundary. It leaves the required Cloud Storage behavior unaddressed.

Question 781

A Secret Manager secret in project vault can be read by every Kubernetes ServiceAccount in a GKE workload identity pool. Only Pod processor in namespace finance should read it. Which IAM change reduces exposure?

  1. Keep the pool-wide Secret Accessor grant and rely on each Pod owner to avoid reading the secret.
  2. Move the secret into a public Cloud Storage bucket so that only one Kubernetes namespace needs to handle authentication.
  3. Remove the broad principalSet grant and bind Secret Accessor on the secret to the exact approved finance/processor federated principal.
  4. Grant the node service account Secret Manager Admin across the organization because all Pods share the same GKE node.

Explanation

Correct Answer

C:

Remove the broad principalSet grant and bind Secret Accessor on the secret to the exact approved finance/processor federated principal. Workload Identity Federation for GKE supports namespace- and KSA-specific principals. Binding only that principal at the secret resource stops granting access to other KSAs in the pool.

Incorrect Answers

A:

Keep the pool-wide Secret Accessor grant and rely on each Pod owner to avoid reading the secret. A pool-wide principalSet binding remains effective for unrelated workloads; voluntary behavior is not an IAM authorization boundary.

B:

Move the secret into a public Cloud Storage bucket so that only one Kubernetes namespace needs to handle authentication. Public object storage would reduce confidentiality and is unrelated to least-privilege Secret Manager access.

D:

Grant the node service account Secret Manager Admin across the organization because all Pods share the same GKE node. Node-wide Secret Manager Admin expands privileges far beyond one secret and defeats workload-level isolation.

Question 782

A Pod runs with the intended KSA, but its Google Cloud IAM binding refers to a Google service account without the needed impersonation grant. What should be aligned?

  1. Remove the now-unneeded workload-to-Google-service-account impersonation role binding after verifying the direct federated permissions and dependencies.
  2. Grant Organization Owner to the caller rather than validating the intended identity binding.
  3. Allow tokens from any issuer without verifying audience, signature or mapped principal.
  4. Grant the authorized KSA principal the appropriate service-account Workload Identity User impersonation right or use direct resource principal grants as designed.

Explanation

Correct Answer

D:

GKE federation and Google service-account impersonation are distinct supported modes with different IAM bindings.

Incorrect Answers

A:

The suggestion does not establish the required issuer, principal or permission boundary. It leaves the correct runtime principal and its bindings unaddressed. The appropriate action here is: Grant the authorized KSA principal the appropriate service-account Workload Identity User impersonation right or use direct resource principal grants as designed.

B:

Organization Owner is excessive privilege and cannot repair an unrelated configuration fault. The specific requirement concerns the correct runtime principal and its bindings. The appropriate action here is: Grant the authorized KSA principal the appropriate service-account Workload Identity User impersonation right or use direct resource principal grants as designed.

C:

The suggestion does not establish the required issuer, principal or permission boundary. The necessary distinction is the correct runtime principal and its bindings. The appropriate action here is: Grant the authorized KSA principal the appropriate service-account Workload Identity User impersonation right or use direct resource principal grants as designed.

Question 783

A GKE application uses a KSA annotation pointing to the wrong Google service account, so its requests run under an unrelated identity. What should be corrected?

  1. Update the KSA annotation and associated approved impersonation IAM policy to the intended Google service account.
  2. Grant the authorized KSA principal the appropriate service-account Workload Identity User impersonation right or use direct resource principal grants as designed.
  3. Disable service-account audit logging and assume the credential issue is resolved.
  4. Grant Organization Owner to the caller rather than validating the intended identity binding.

Explanation

Correct Answer

A:

Kubernetes-to-Google-service-account mappings determine which cloud identity the Pod can act as when impersonation mode is used.

Incorrect Answers

B:

The suggestion does not establish the required issuer, principal or permission boundary. The specific requirement concerns the correct runtime principal and its bindings. The appropriate action here is: Update the KSA annotation and associated approved impersonation IAM policy to the intended Google service account.

C:

Changing audit collection cannot grant a denied permission or fix service behavior. The necessary distinction is the correct runtime principal and its bindings. The appropriate action here is: Update the KSA annotation and associated approved impersonation IAM policy to the intended Google service account.

D:

Organization Owner is excessive privilege and cannot repair an unrelated configuration fault. The case instead depends on the correct runtime principal and its bindings. The appropriate action here is: Update the KSA annotation and associated approved impersonation IAM policy to the intended Google service account.

Question 784

A developer rotates a Kubernetes ServiceAccount name in a Deployment but forgets to update the IAM principal binding for a Pub/Sub subscription. Which update is needed?

  1. Reconcile the renamed workload principal in Pub/Sub IAM and validate only the new KSA can consume messages.
  2. Remove Pub/Sub Admin and grant roles/pubsub.publisher on topic stock-events to that specific federated Kubernetes workload principal.
  3. Grant Organization Owner to the caller rather than validating the intended identity binding.
  4. Rename the service account but leave the old principal and role bindings unchanged.

Explanation

Correct Answer

A:

ServiceAccount renaming changes the federated identity that resource IAM evaluates, even if the application image is unchanged.

Incorrect Answers

B:

The suggestion does not establish the required issuer, principal or permission boundary. The necessary distinction is the workload's intended identity and permissions. The appropriate action here is: Reconcile the renamed workload principal in Pub/Sub IAM and validate only the new KSA can consume messages.

C:

Organization Owner is excessive privilege and cannot repair an unrelated configuration fault. The case instead depends on the workload's intended identity and permissions.

D:

Renaming a resource does not alter the actual effective configuration. It leaves the workload's intended identity and permissions unaddressed. The appropriate action here is: Reconcile the renamed workload principal in Pub/Sub IAM and validate only the new KSA can consume messages.

Question 785

A GKE workload identity only sends messages to existing Pub/Sub topic stock-events. Its federated principal currently has project-level Pub/Sub Admin. Which authorization should replace it?

  1. Give the Pod Pub/Sub Viewer on the entire project; the viewer role provides message publishing.
  2. Remove Pub/Sub Admin and grant roles/pubsub.publisher on topic stock-events to that specific federated Kubernetes workload principal.
  3. Bind Storage Object Creator on the project; Pub/Sub topics accept Cloud Storage object-create permissions as publish authorization.
  4. Keep the project-wide Admin grant and restrict only the Kubernetes namespace, because Kubernetes namespace constraints reduce Google Cloud IAM permissions.

Explanation

Correct Answer

B:

Remove Pub/Sub Admin and grant roles/pubsub.publisher on topic stock-events to that specific federated Kubernetes workload principal. The topic-scoped Pub/Sub Publisher role authorizes publishing without allowing topic creation, deletion, or subscription administration.

Incorrect Answers

A:

Give the Pod Pub/Sub Viewer on the entire project; the viewer role provides message publishing. Viewer is a read-only role; it does not supply the publish permission the Pod needs.

C:

Bind Storage Object Creator on the project; Pub/Sub topics accept Cloud Storage object-create permissions as publish authorization. Cloud Storage IAM governs object operations and does not grant Pub/Sub message publishing on a topic.

D:

Keep the project-wide Admin grant and restrict only the Kubernetes namespace, because Kubernetes namespace constraints reduce Google Cloud IAM permissions. Kubernetes namespaces and Google Cloud IAM resource grants are separate layers; the existing project Admin would remain broad if left in place.

Question 786

A team uses a static service-account JSON file on a GKE node to give all Pods the same permissions, ignoring Kubernetes per-workload identities. What migration improves separation?

  1. Use the Pod's Kubernetes ServiceAccount with GKE Workload Identity Federation and grant its mapped principal only the required bucket permissions.
  2. Use distinct Kubernetes ServiceAccounts mapped to scoped federated Google Cloud permissions for individual workloads.
  3. Grant Organization Owner to the caller rather than validating the intended identity binding.
  4. Grant a new billing role instead of adjusting the actual token or impersonation permission.

Explanation

Correct Answer

B:

Node-wide static credentials are shared by colocated applications and undermine per-Pod least-privilege boundaries.

Incorrect Answers

A:

Changing an unrelated Pod setting leaves the stated cloud feature unresolved. It leaves the workload's intended identity and permissions unaddressed. The appropriate action here is: Use distinct Kubernetes ServiceAccounts mapped to scoped federated Google Cloud permissions for individual workloads.

C:

Organization Owner is excessive privilege and cannot repair an unrelated configuration fault. The specific requirement concerns the workload's intended identity and permissions. The appropriate action here is: Use distinct Kubernetes ServiceAccounts mapped to scoped federated Google Cloud permissions for individual workloads.

D:

The suggestion does not establish the required issuer, principal or permission boundary. The necessary distinction is the workload's intended identity and permissions. The appropriate action here is: Use distinct Kubernetes ServiceAccounts mapped to scoped federated Google Cloud permissions for individual workloads.

Question 787

A GKE cluster is recreated in a different Google Cloud project and its Pods now use the new project's workload identity pool. The metadata server returns a federated token, but a protected bucket still authorizes only the old project's namespace/KSA principal. Which change fixes the access boundary?

  1. Enable an extra GPU node pool; bucket IAM always derives its identity from the physical GPU node pool.
  2. Give the new project's default Compute Engine node service account Storage Admin on every bucket in the organization.
  3. Copy the old cluster's Kubernetes ServiceAccount YAML without changing the bucket's IAM principal bindings.
  4. Update the bucket IAM binding to the intended new-project workload pool and exact namespace/KSA principal, then verify the old binding is retired.

Explanation

Correct Answer

D:

Update the bucket IAM binding to the intended new-project workload pool and exact namespace/KSA principal, then verify the old binding is retired. The new cluster/project has a different workload identity pool. Resource IAM must authorize the new qualified principal identity and remove obsolete old-project access.

Incorrect Answers

A:

Enable an extra GPU node pool; bucket IAM always derives its identity from the physical GPU node pool. GPU scheduling does not determine the Google Cloud federated IAM principal accepted by a bucket.

B:

Give the new project's default Compute Engine node service account Storage Admin on every bucket in the organization. A broad default node identity adds unnecessary rights and does not repair the intended per-workload IAM principal mapping.

C:

Copy the old cluster's Kubernetes ServiceAccount YAML without changing the bucket's IAM principal bindings. YAML may preserve the KSA name, but a federated principal includes the project-bound workload identity pool and cannot be assumed identical across projects.

Question 788

An application Pod in GKE sets hostNetwork: true. Unlike normal Pods, its metadata requests reach the Compute Engine metadata server instead of the GKE workload identity metadata server. Which documented exception explains this?

  1. The Pod is missing an organization-level IAM Owner grant; granting Owner switches host-networked Pods to GKE metadata.
  2. All Kubernetes Pods always use the GKE metadata server, including host-networked workloads, so this observation is impossible.
  3. Pods using the host network bypass the standard Workload Identity Federation for GKE metadata interception path; use a supported non-host-network design or documented exception path.
  4. The Pod's Secret Manager permissions are too narrow; that causes the metadata server to reroute all credential requests to Compute Engine.

Explanation

Correct Answer

C:

Pods using the host network bypass the standard Workload Identity Federation for GKE metadata interception path; use a supported non-host-network design or documented exception path. The host-network setting changes how metadata requests are routed. A workload expecting KSA federation should avoid relying on unsupported host-network behavior or use its documented supported configuration.

Incorrect Answers

A:

The Pod is missing an organization-level IAM Owner grant; granting Owner switches host-networked Pods to GKE metadata. Owner IAM permissions are not what selects the node versus GKE metadata endpoint for a host-networked Pod.

B:

All Kubernetes Pods always use the GKE metadata server, including host-networked workloads, so this observation is impossible. Google explicitly documents a hostNetwork exception; not every Pod follows the same metadata interception behavior.

D:

The Pod's Secret Manager permissions are too narrow; that causes the metadata server to reroute all credential requests to Compute Engine. Secret authorization occurs after credential acquisition and does not choose the metadata server that handles the Pod's HTTP request.

Question 789

An application needs identity across multiple GKE clusters but an IAM binding trusts one cluster-specific principal identifier only. What should the team verify?

  1. Rebind resource IAM to the current authorized workload identity pool and Kubernetes principal identifiers.
  2. Grant Organization Owner to the caller rather than validating the intended identity binding.
  3. Map supported principal identity attributes and trust scopes for each authorized cluster without accidentally granting unrelated workloads access.
  4. Reuse the default Compute Engine service account for every unrelated workload.

Explanation

Correct Answer

C:

Workload identity principal identifiers can reflect cluster/project pool context; multi-cluster access requires explicit trustworthy matching.

Incorrect Answers

A:

The suggestion does not establish the required issuer, principal or permission boundary. The case instead depends on the workload's intended identity and permissions. The appropriate action here is: Map supported principal identity attributes and trust scopes for each authorized cluster without accidentally granting unrelated workloads access.

B:

Organization Owner is excessive privilege and cannot repair an unrelated configuration fault. It leaves the workload's intended identity and permissions unaddressed. The appropriate action here is: Map supported principal identity attributes and trust scopes for each authorized cluster without accidentally granting unrelated workloads access.

D:

The suggestion does not establish the required issuer, principal or permission boundary. The specific requirement concerns the workload's intended identity and permissions. The appropriate action here is: Map supported principal identity attributes and trust scopes for each authorized cluster without accidentally granting unrelated workloads access.

Question 790

A GKE cluster is moved to a different project, and old workload identity IAM bindings keep referencing the former project's pool identifier. What must be updated?

  1. Map supported principal identity attributes and trust scopes for each authorized cluster without accidentally granting unrelated workloads access.
  2. Grant a new billing role instead of adjusting the actual token or impersonation permission.
  3. Allow tokens from any issuer without verifying audience, signature or mapped principal.
  4. Rebind resource IAM to the current authorized workload identity pool and Kubernetes principal identifiers.

Explanation

Correct Answer

D:

The pool and resource path identify the cloud trust boundary; an unchanged KSA name doesn't preserve a deleted or moved pool identity.

Incorrect Answers

A:

The suggestion does not establish the required issuer, principal or permission boundary. It leaves the workload's intended identity and permissions unaddressed. The appropriate action here is: Rebind resource IAM to the current authorized workload identity pool and Kubernetes principal identifiers.

B:

The suggestion does not establish the required issuer, principal or permission boundary. The specific requirement concerns the workload's intended identity and permissions. The appropriate action here is: Rebind resource IAM to the current authorized workload identity pool and Kubernetes principal identifiers.

C:

The suggestion does not establish the required issuer, principal or permission boundary. The necessary distinction is the workload's intended identity and permissions. The appropriate action here is: Rebind resource IAM to the current authorized workload identity pool and Kubernetes principal identifiers.

Associate Cloud Engineer Practice Tests