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 74

Question 730

A release job can mint a token for a service account with broad production rights but the job only deploys to staging. What grant should be removed?

  1. Rotate the staging job credentials but leave its production Token Creator delegation intact.
  2. Remove production Token Creator delegation from the staging pipeline and use a separate staging deployment identity.
  3. Rename the service account but leave the old principal and role bindings unchanged.
  4. Issue a long-lived service-account JSON key instead of repairing short-lived workload credentials.

Explanation

Correct Answer

B:

Service-account impersonation can indirectly grant all resource permissions of the target account; excessive delegation is high risk.

Incorrect Answers

A:

Credential rotation does not revoke the production account impersonation grant available to staging.

C:

Renaming a resource does not alter the actual effective configuration. The specific requirement concerns the permitted service-account delegation.

D:

The suggestion does not establish the required issuer, principal or permission boundary. The necessary distinction is the permitted service-account delegation. The appropriate action here is: Remove production Token Creator delegation from the staging pipeline and use a separate staging deployment identity.

Question 731

A project admin creates an account with all required resource roles but a newly added Cloud Run deployer cannot use it at deployment time. What should be granted to the deployer?

  1. Assign the necessary scoped storage role to the newly attached Cloud Run runtime service account.
  2. Disable service-account audit logging and assume the credential issue is resolved.
  3. Grant a new billing role instead of adjusting the actual token or impersonation permission.
  4. Grant the supported service-account usage (actAs) permission on that runtime account to the authorized deployer.

Explanation

Correct Answer

D:

The deployer needs permission to attach the runtime identity even if the runtime identity itself has correct API roles.

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: Grant the supported service-account usage (actAs) permission on that runtime account to the authorized deployer.

B:

Changing audit collection cannot grant a denied permission or fix service behavior. The necessary distinction is the workload's intended identity and permissions.

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: Grant the supported service-account usage (actAs) permission on that runtime account to the authorized deployer.

Question 732

A contractor needs to invoke one protected API using a production service account but engineers offer them a downloaded JSON private key. What safer route should be considered?

  1. Use a Google workload identity pool provider for the approved Azure identity and obtain scoped short-lived Google credentials without a private key.
  2. Grant a new billing role instead of adjusting the actual token or impersonation permission.
  3. Reuse the default Compute Engine service account for every unrelated workload.
  4. Use short-lived audited impersonation credentials with a scoped time-bound grant rather than handing out a reusable private key.

Explanation

Correct Answer

D:

Ephemeral delegated credentials can avoid distributing a long-lived account secret to an external user.

Incorrect Answers

A:

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: Use short-lived audited impersonation credentials with a scoped time-bound grant rather than handing out a reusable private key.

B:

The suggestion does not establish the required issuer, principal or permission boundary. The case instead depends on the correct runtime principal and its bindings. The appropriate action here is: Use short-lived audited impersonation credentials with a scoped time-bound grant rather than handing out a reusable private key.

C:

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: Use short-lived audited impersonation credentials with a scoped time-bound grant rather than handing out a reusable private key.

Question 733

An audit reviewer sees an API action attributed to a service account, but needs to identify the developer who impersonated it to issue the short-lived credential. Which records can help recover the delegation chain?

  1. Inspect the relevant Cloud Audit Logs delegation information and IAM Credentials token-generation events where those records are supported and enabled.
  2. Use only Cloud Billing cost exports; their SKU fields contain the identity of every user who minted a service-account token.
  3. Read the service account display name; that name includes an immutable identifier for the most recent impersonating user.
  4. Query Cloud DNS A records for the service account; DNS logs are the authoritative caller history for token issuance.

Explanation

Correct Answer

A:

Inspect the relevant Cloud Audit Logs delegation information and IAM Credentials token-generation events where those records are supported and enabled. Service-account impersonation can produce logs containing both the target identity and initiating principal. IAM Credentials Data Access audit logs may need to be enabled.

Incorrect Answers

B:

Use only Cloud Billing cost exports; their SKU fields contain the identity of every user who minted a service-account token. Cost exports measure resource charges, not authenticated IAM delegation actors. They cannot replace IAM audit evidence for a token request.

C:

Read the service account display name; that name includes an immutable identifier for the most recent impersonating user. A service account can be impersonated by multiple approved callers. Its display name cannot identify the principal behind a particular token.

D:

Query Cloud DNS A records for the service account; DNS logs are the authoritative caller history for token issuance. DNS lookups resolve names and do not record the IAM Credentials actor or service-account delegation chain for a Google API call.

Question 734

A developer has Service Account Token Creator permission on a target service account, but gcloud impersonation fails because iamcredentials.googleapis.com is disabled in the authorized project. Which independent prerequisite is missing?

  1. Grant Cloud Storage Object Viewer; read access on a bucket automatically enables the IAM Credentials API.
  2. Increase the Cloud Run request concurrency setting; token minting depends on how many web requests a revision handles.
  3. Change the account's display name; the IAM Credentials API is enabled when service-account metadata is renamed.
  4. Have an authorized administrator enable the Service Account Credentials API in the relevant project, then verify token-creation permissions.

Explanation

Correct Answer

D:

Have an authorized administrator enable the Service Account Credentials API in the relevant project, then verify token-creation permissions. Google documents the Service Account Credentials API as a prerequisite for supported impersonation workflows; IAM permission and API activation are separate checks.

Incorrect Answers

A:

Grant Cloud Storage Object Viewer; read access on a bucket automatically enables the IAM Credentials API. Storage permissions govern bucket data access and cannot activate a disabled Google API for the project.

B:

Increase the Cloud Run request concurrency setting; token minting depends on how many web requests a revision handles. Cloud Run request concurrency is unrelated to whether the IAM Credentials API is enabled for token minting.

C:

Change the account's display name; the IAM Credentials API is enabled when service-account metadata is renamed. Display-name updates do not invoke Service Usage enablement for IAM Credentials.

Question 735

A service account is permitted to impersonate another account, but administrators accidentally create a delegation cycle among three highly privileged accounts. What should security review?

  1. Remove production Token Creator delegation from the staging pipeline and use a separate staging deployment identity.
  2. Audit and break unnecessary service-account impersonation chains so each delegation has an approved one-way purpose.
  3. Rename the service account but leave the old principal and role bindings unchanged.
  4. Grant Organization Owner to the caller rather than validating the intended identity binding.

Explanation

Correct Answer

B:

Chained impersonation can expand effective privilege and obscure ownership; identities should not form circular or excessive delegation graphs.

Incorrect Answers

A:

Deploying a separate workload does not automatically configure the existing feature. The specific requirement concerns workload impersonation authorization.

C:

Renaming a resource does not alter the actual effective configuration. The necessary distinction is workload impersonation authorization.

D:

Organization Owner is excessive privilege and cannot repair an unrelated configuration fault. The case instead depends on workload impersonation authorization.

Question 736

An operator tries to mint an ID token and use it as a Bearer token for an API expecting OAuth 2.0 access tokens. Why does authorization fail?

  1. Mint or acquire a supported OIDC ID token with the protected Cloud Run service as its intended audience.
  2. Rename the service account but leave the old principal and role bindings unchanged.
  3. Allow tokens from any issuer without verifying audience, signature or mapped principal.
  4. Use the appropriate OAuth access token for Google Cloud API scopes rather than a service-targeted OIDC ID token.

Explanation

Correct Answer

D:

ID tokens attest caller identity and intended audience, while OAuth access tokens authorize supported API operations.

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: Use the appropriate OAuth access token for Google Cloud API scopes rather than a service-targeted OIDC ID token.

B:

Renaming a resource does not alter the actual effective configuration. The case instead depends on the workload's intended identity and permissions. The appropriate action here is: Use the appropriate OAuth access token for Google Cloud API scopes rather than a service-targeted OIDC ID token.

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: Use the appropriate OAuth access token for Google Cloud API scopes rather than a service-targeted OIDC ID token.

Question 737

A client uses an OAuth access token to call an OIDC-protected Cloud Run endpoint that requires an audience-bearing identity token. What should it obtain?

  1. Mint or acquire a supported OIDC ID token with the protected Cloud Run service as its intended audience.
  2. Use the appropriate OAuth access token for Google Cloud API scopes rather than a service-targeted OIDC ID token.
  3. Reuse the default Compute Engine service account for every unrelated workload.
  4. Allow tokens from any issuer without verifying audience, signature or mapped principal.

Explanation

Correct Answer

A:

Authenticated Cloud Run HTTP invocation expects compatible identity tokens, not arbitrary API OAuth access tokens.

Incorrect Answers

B:

A token type must match the consuming API and the configured identity trust. 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: Mint or acquire a supported OIDC ID token with the protected Cloud Run service as its intended audience.

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: Mint or acquire a supported OIDC ID token with the protected Cloud Run service as its intended audience.

Question 738

An ID token has the right service-account identity but the wrong audience string for the target endpoint. What must be corrected?

  1. Use the appropriate OAuth access token for Google Cloud API scopes rather than a service-targeted OIDC ID token.
  2. Generate the ID token with the exact accepted target audience and validate endpoint authentication configuration.
  3. Grant a new billing role instead of adjusting the actual token or impersonation permission.
  4. Disable service-account audit logging and assume the credential issue is resolved.

Explanation

Correct Answer

B:

Audience checks prevent a token issued for one service from being replayed as authorization to another.

Incorrect Answers

A:

A token type must match the consuming API and the configured identity trust. 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: Generate the ID token with the exact accepted target audience and validate endpoint authentication configuration.

D:

Changing audit collection cannot grant a denied permission or fix service behavior. The necessary distinction is the workload's intended identity and permissions. The appropriate action here is: Generate the ID token with the exact accepted target audience and validate endpoint authentication configuration.

Question 739

A delegated service account can call Cloud Storage but fails to create a Compute Engine VM because only Storage roles were assigned to the target account. What is the correct distinction?

  1. Update the KSA annotation and associated approved impersonation IAM policy to the intended Google service account.
  2. Grant the target service account the minimal required Compute permissions if approved, not more impersonation rights to the caller.
  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:

Impersonation controls who may act as an identity; resource IAM controls what that identity may do once assumed.

Incorrect Answers

A:

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: Grant the target service account the minimal required Compute permissions if approved, not more impersonation rights to the caller.

C:

Organization Owner is excessive privilege and cannot repair an unrelated configuration fault. The necessary distinction is the correct runtime principal and its bindings.

D:

The suggestion does not establish the required issuer, principal or permission boundary. The case instead depends on the correct runtime principal and its bindings. The appropriate action here is: Grant the target service account the minimal required Compute permissions if approved, not more impersonation rights to the caller.

Question 740

An automated access policy grants every engineer Token Creator on a high-privilege production account for convenience. Which control most directly reduces exposure?

  1. Remove production Token Creator delegation from the staging pipeline and use a separate staging deployment identity.
  2. Disable service-account audit logging and assume the credential issue is resolved.
  3. Limit impersonation to an approved deployment group or workflow and revoke the broad token-generation grant.
  4. Rename the service account but leave the old principal and role bindings unchanged.

Explanation

Correct Answer

C:

Token Creator can mint credentials acting as the target identity, so widespread delegation undermines least privilege.

Incorrect Answers

A:

Deploying a separate workload does not automatically configure the existing feature. The necessary distinction is the permitted service-account delegation.

B:

Changing audit collection cannot grant a denied permission or fix service behavior. The case instead depends on the permitted service-account delegation.

D:

Renaming a resource does not alter the actual effective configuration. It leaves the permitted service-account delegation unaddressed. The appropriate action here is: Limit impersonation to an approved deployment group or workflow and revoke the broad token-generation grant.

Associate Cloud Engineer Practice Tests