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 78

Question 770

An organization's external deployment pipeline uses Workload Identity Federation and impersonates a Google service account. An audit must identify the original external workload behind a suspicious API call. Which evidence is relevant?

  1. Correlate available STS and IAM Credentials audit events with service-account delegation information, mapped external subject attributes and target-resource logs.
  2. Examine only the service account's display name; it always encodes the full original external workload and request chain.
  3. Query Cloud Billing budgets; threshold alerts include external token claims and an authenticated delegation chain.
  4. Compare Cloud Storage bucket locations; cross-region replication history identifies the external pipeline actor.

Explanation

Correct Answer

A:

Correlate available STS and IAM Credentials audit events with service-account delegation information, mapped external subject attributes and target-resource logs. Federation and impersonation can involve multiple authenticated principals. Audit records and principal mapping help reconstruct their relationship when logging is available.

Incorrect Answers

B:

Examine only the service account's display name; it always encodes the full original external workload and request chain. A service-account name is static and shared across requests, so it cannot distinguish the external principal that generated an individual token.

C:

Query Cloud Billing budgets; threshold alerts include external token claims and an authenticated delegation chain. Budget notifications contain cost state, not the identity assertions and IAM Credentials actor relationships required for this audit.

D:

Compare Cloud Storage bucket locations; cross-region replication history identifies the external pipeline actor. Bucket placement and replication do not reveal which identity requested service-account credentials through a federated STS flow.

Question 771

An identity pool is deleted while its workloads still rely on its credential configuration files. What migration must happen first?

  1. Rebind resource IAM to the current authorized workload identity pool and Kubernetes principal identifiers.
  2. Issue a long-lived service-account JSON key instead of repairing short-lived workload credentials.
  3. Allow tokens from any issuer without verifying audience, signature or mapped principal.
  4. Provision a replacement trusted pool/provider and migrate approved workload credential sources and IAM bindings before decommissioning.

Explanation

Correct Answer

D:

Removing a federation provider breaks future token exchanges for every workload still configured to use it.

Incorrect Answers

A:

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: Provision a replacement trusted pool/provider and migrate approved workload credential sources and IAM bindings before decommissioning.

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: Provision a replacement trusted pool/provider and migrate approved workload credential sources and IAM bindings before decommissioning.

C:

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: Provision a replacement trusted pool/provider and migrate approved workload credential sources and IAM bindings before decommissioning.

Question 772

A federation principal is granted a project-wide Editor role merely to upload one Artifact Registry image. What should the least-privilege fix target?

  1. Replace broad Editor grants with reviewed minimum roles, ideally using a dedicated application service account for these VMs.
  2. Allow tokens from any issuer without verifying audience, signature or mapped principal.
  3. Grant a new billing role instead of adjusting the actual token or impersonation permission.
  4. Grant only the necessary Artifact Registry writer permissions at the intended repository and revoke broad project editing rights.

Explanation

Correct Answer

D:

Workload federation establishes who acts, while per-resource IAM should restrict what the external identity may change.

Incorrect Answers

A:

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: Grant only the necessary Artifact Registry writer permissions at the intended repository and revoke broad project editing rights.

B:

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: Grant only the necessary Artifact Registry writer permissions at the intended repository and revoke broad project editing rights.

C:

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: Grant only the necessary Artifact Registry writer permissions at the intended repository and revoke broad project editing rights.

Question 773

An external identity provider temporarily issues malformed signing keys during rotation, causing intermittent federation failures. What should platform operations validate?

  1. The approved issuer URI, token audience, JWKS/discovery endpoint and mapped attributes; update provider trust only after confirming the new issuer is authorized.
  2. Verify supported JWKS key rotation, cached discovery metadata and token signature validation rather than bypassing issuer verification.
  3. Grant Organization Owner to the caller rather than validating the intended identity binding.
  4. Disable service-account audit logging and assume the credential issue is resolved.

Explanation

Correct Answer

B:

Federation cryptographic validation depends on current trusted signing key material and must not be disabled to restore access.

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: Verify supported JWKS key rotation, cached discovery metadata and token signature validation rather than bypassing issuer verification.

C:

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: Verify supported JWKS key rotation, cached discovery metadata and token signature validation rather than bypassing issuer verification.

D:

Changing audit collection cannot grant a denied permission or fix service behavior. The specific requirement concerns the workload's intended identity and permissions.

Question 774

A workload identity configuration accepts claims containing a generic environment label but the source CI platform lets anyone set that label. What is the threat?

  1. Use environment-specific reviewed workload identity provider configuration and validate production issuer, audience and mapped claims.
  2. Grant Organization Owner to the caller rather than validating the intended identity binding.
  3. Grant a new billing role instead of adjusting the actual token or impersonation permission.
  4. Use trusted immutable issuer claims or protected CI environment attestations instead of untrusted user-controlled attributes for production authorization.

Explanation

Correct Answer

D:

Attribute conditions are only as trustworthy as the issuer's claim-generation and workload protection controls.

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: Use trusted immutable issuer claims or protected CI environment attestations instead of untrusted user-controlled attributes for production authorization.

B:

Organization Owner is excessive privilege and cannot repair an unrelated configuration fault. The specific requirement concerns the workload's intended identity and permissions.

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: Use trusted immutable issuer claims or protected CI environment attestations instead of untrusted user-controlled attributes for production authorization.

Question 775

An organization replaces GitHub with a second CI service and attempts to reuse a provider configured exclusively for GitHub OIDC tokens. What should it do?

  1. Map and require the exact approved repository or environment attributes in the workload identity provider's attribute condition.
  2. Rename the service account but leave the old principal and role bindings unchanged.
  3. Create an approved provider for the new CI issuer with its own attribute mapping and restrict resource grants to that provider.
  4. Issue a long-lived service-account JSON key instead of repairing short-lived workload credentials.

Explanation

Correct Answer

C:

OIDC trust configuration identifies a specific issuer; credentials from a different identity provider require independent verification.

Incorrect Answers

A:

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: Create an approved provider for the new CI issuer with its own attribute mapping and restrict resource grants to that provider.

B:

Renaming a resource does not alter the actual effective configuration. The necessary distinction is the workload's intended identity and permissions. The appropriate action here is: Create an approved provider for the new CI issuer with its own attribute mapping and restrict resource grants to that provider.

D:

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: Create an approved provider for the new CI issuer with its own attribute mapping and restrict resource grants to that provider.

Question 776

A Pod on a GKE cluster stores a Google service-account JSON key in a Kubernetes Secret to read objects from one Cloud Storage bucket. Workload Identity Federation for GKE is enabled. What credential design avoids the static key?

  1. Use a longer-lived JSON key in the same Secret; longer expiry eliminates the credential-rotation burden.
  2. Use the Pod's Kubernetes ServiceAccount with GKE Workload Identity Federation and grant its mapped principal only the required bucket permissions.
  3. Grant Cloud Storage anonymous access and remove the Kubernetes Secret; all buckets should be public when running on GKE.
  4. Copy the service-account key into an image layer so it is available before the container starts.

Explanation

Correct Answer

B:

Use the Pod's Kubernetes ServiceAccount with GKE Workload Identity Federation and grant its mapped principal only the required bucket permissions. GKE Workload Identity Federation can provide supported metadata-server credentials for Kubernetes workload identity with narrowly scoped resource IAM roles.

Incorrect Answers

A:

Use a longer-lived JSON key in the same Secret; longer expiry eliminates the credential-rotation burden. A persistent key remains a theft risk in a Secret; increasing its lifetime only increases the exposure window.

C:

Grant Cloud Storage anonymous access and remove the Kubernetes Secret; all buckets should be public when running on GKE. Public access abandons the protected bucket requirement and is unnecessary for keyless workload authentication.

D:

Copy the service-account key into an image layer so it is available before the container starts. Baking credentials into a container image makes the secret harder to rotate and risks distribution through image registries and caches.

Question 777

A Pod using Workload Identity Federation for GKE gets PERMISSION_DENIED on a bucket after its Kubernetes namespace is renamed. What identity binding needs review?

  1. Update the IAM principal mapping to the new namespace and Kubernetes ServiceAccount identity, then verify bucket-level read rights.
  2. Use the Pod's Kubernetes ServiceAccount with GKE Workload Identity Federation and grant its mapped principal only the required bucket permissions.
  3. Issue a long-lived service-account JSON key instead of repairing short-lived workload credentials.
  4. Reuse the default Compute Engine service account for every unrelated workload.

Explanation

Correct Answer

A:

GKE federated workload principals include Kubernetes identity components such as namespace, which change across namespace migrations.

Incorrect Answers

B:

Changing an unrelated Pod setting leaves the stated cloud feature unresolved. The case instead depends on the workload's intended identity and permissions.

C:

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: Update the IAM principal mapping to the new namespace and Kubernetes ServiceAccount identity, then verify bucket-level read rights.

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: Update the IAM principal mapping to the new namespace and Kubernetes ServiceAccount identity, then verify bucket-level read rights.

Question 778

A Kubernetes Deployment omits serviceAccountName and therefore runs under the namespace's default KSA, which lacks required Secret Manager read access. What should be set?

  1. Specify the intended Kubernetes ServiceAccount in the Pod template and grant only that KSA principal the required secret permissions.
  2. Set the CronJob Pod template to its approved workload KSA and corresponding IAM grants independently of the Deployment.
  3. Grant a new billing role instead of adjusting the actual token or impersonation permission.
  4. Issue a long-lived service-account JSON key instead of repairing short-lived workload credentials.

Explanation

Correct Answer

A:

The Pod identity follows serviceAccountName; omission can silently select a default account rather than the reviewed workload identity.

Incorrect Answers

B:

Changing an unrelated Pod setting leaves the stated cloud feature unresolved. It leaves the workload's intended identity and permissions unaddressed.

C:

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: Specify the intended Kubernetes ServiceAccount in the Pod template and grant only that KSA principal the required secret permissions.

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: Specify the intended Kubernetes ServiceAccount in the Pod template and grant only that KSA principal the required secret permissions.

Question 779

In a GKE Standard cluster, Pods using Workload Identity Federation for GKE are scheduled to a node pool still configured for the Compute Engine metadata server instead of the GKE metadata server. Which cluster configuration must be corrected?

  1. Enable the GKE metadata server for that eligible Standard node pool and verify the cluster workload identity setting.
  2. Put one service-account private key in every Pod; this is required whenever a cluster has WIF enabled.
  3. Change Cloud Billing account ownership for the cluster; billing permissions select the metadata server used by the nodes.
  4. Add Kubernetes ClusterRole cluster-admin to the Pods; Kubernetes RBAC silently activates the GKE metadata server on existing nodes.

Explanation

Correct Answer

A:

Enable the GKE metadata server for that eligible Standard node pool and verify the cluster workload identity setting. Standard GKE node pools must be configured to use the GKE metadata server for federated Pod identity. A node pool left on GCE metadata does not provide the intended interception for these Pods.

Incorrect Answers

B:

Put one service-account private key in every Pod; this is required whenever a cluster has WIF enabled. Static keys are not a prerequisite for Workload Identity Federation and would undermine its keyless purpose.

C:

Change Cloud Billing account ownership for the cluster; billing permissions select the metadata server used by the nodes. Billing access affects charges, not the metadata-server mode used for Pod credential requests.

D:

Add Kubernetes ClusterRole cluster-admin to the Pods; Kubernetes RBAC silently activates the GKE metadata server on existing nodes. Kubernetes RBAC and node-pool workload metadata configuration are separate. Cluster-admin does not switch a node pool to the GKE metadata server.

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.

Associate Cloud Engineer Practice Tests