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 70

Question 690

A team wants IAM access for a service limited by network location but attempts to use a condition attribute unsupported by that product. What secure alternative should be considered?

  1. Verify that the selected IAM condition attribute is supported for the target service, resource and permission type.
  2. Add another broad allow-role binding without checking inherited denies or restrictions.
  3. Move the project between billing accounts to bypass an IAM authorization decision.
  4. Use an approved supported access-context or network/service perimeter control together with IAM instead of assuming an invalid condition will enforce location.

Explanation

Correct Answer

D:

IAM Conditions have service/attribute limits; network provenance may require a distinct supported policy layer.

Incorrect Answers

A:

That action does not resolve the effective IAM permission and binding in this request. It leaves the effective access decision unaddressed. The appropriate action here is: Use an approved supported access-context or network/service perimeter control together with IAM instead of assuming an invalid condition will enforce location.

B:

That action does not resolve the effective IAM permission and binding in this request. The specific requirement concerns the effective access decision. The appropriate action here is: Use an approved supported access-context or network/service perimeter control together with IAM instead of assuming an invalid condition will enforce location.

C:

Billing changes payment responsibility, not the technical behavior of this workload. The necessary distinction is the effective access decision.

Question 691

A security incident involves a formerly trusted outside domain, but an organization policy now blocks adding its identities to new IAM bindings. What should be validated?

  1. Inspect the exact permission and resource with IAM policy analysis or Policy Troubleshooter and separately check the effective organization policy constraint.
  2. Grant the role at the organization root despite the request for a narrow resource scope.
  3. Check the effective allowed-identity-domain organization restriction and whether existing bindings require a separately approved remediation.
  4. Grant project Owner to the principal without checking the specific permission or effective policy.

Explanation

Correct Answer

C:

Organization policies can restrict which external identities may be granted roles independently of the role itself.

Incorrect Answers

A:

That action does not resolve the effective IAM permission and binding in this request. The specific requirement concerns the effective access decision. The appropriate action here is: Check the effective allowed-identity-domain organization restriction and whether existing bindings require a separately approved remediation.

B:

That action does not resolve the effective IAM permission and binding in this request. The necessary distinction is the effective access decision. The appropriate action here is: Check the effective allowed-identity-domain organization restriction and whether existing bindings require a separately approved remediation.

D:

Project Owner broadens authorization and is not an appropriate substitute for the named control. The case instead depends on the effective access decision. The appropriate action here is: Check the effective allowed-identity-domain organization restriction and whether existing bindings require a separately approved remediation.

Question 692

A project admin updates IAM through the console while another automation job is running, then sees a conflict message. What should the administrator do?

  1. Read the current policy with concurrency controls, modify only intended bindings and apply using etag-aware safe updates.
  2. Refresh the current policy and reapply only the intended change with an etag-compatible update.
  3. Move the project between billing accounts to bypass an IAM authorization decision.
  4. Remove audit logging and assume a missing permission will stop causing failures.

Explanation

Correct Answer

B:

IAM concurrent modification detection protects against losing unrelated changes; retrying a stale full policy can overwrite new bindings.

Incorrect Answers

A:

That action does not resolve the effective IAM permission and binding in this request. The necessary distinction is the effective access decision. The appropriate action here is: Refresh the current policy and reapply only the intended change with an etag-compatible update.

C:

Billing changes payment responsibility, not the technical behavior of this workload. The case instead depends on the effective access decision. The appropriate action here is: Refresh the current policy and reapply only the intended change with an etag-compatible update.

D:

Changing audit collection cannot grant a denied permission or fix service behavior. It leaves the effective access decision unaddressed.

Question 693

A contractor uses a personal external identity whose home provider account is disabled, but still appears in a Google Cloud role binding. What cleanup is needed?

  1. Remove stale IAM policy bindings and replace them with the intended active managed group after verifying membership and resource scope.
  2. Grant project Owner to the principal without checking the specific permission or effective policy.
  3. Remove audit logging and assume a missing permission will stop causing failures.
  4. Review and remove stale external principals from effective IAM bindings and test that no unauthorized alternate principal retains access.

Explanation

Correct Answer

D:

An obsolete IAM binding can remain after identity shutdown; periodic access reviews should reconcile grants with identity lifecycle.

Incorrect Answers

A:

That action does not resolve the effective IAM permission and binding in this request. The case instead depends on the effective access decision. The appropriate action here is: Review and remove stale external principals from effective IAM bindings and test that no unauthorized alternate principal retains access.

B:

Project Owner broadens authorization and is not an appropriate substitute for the named control. It leaves the effective access decision unaddressed. The appropriate action here is: Review and remove stale external principals from effective IAM bindings and test that no unauthorized alternate principal retains access.

C:

Changing audit collection cannot grant a denied permission or fix service behavior. The specific requirement concerns the effective access decision. The appropriate action here is: Review and remove stale external principals from effective IAM bindings and test that no unauthorized alternate principal retains access.

Question 694

A company uses two Cloud Identity domains and one engineer treats an identity from the other tenant as automatically trusted for project admin. What is missing?

  1. Verify the binding's exact group identifier and the user's actual Cloud Identity group membership and propagation.
  2. Explicitly verify the principal's actual federated or Google identity, domain policies and intended role binding at the project scope.
  3. Remove audit logging and assume a missing permission will stop causing failures.
  4. Grant the role at the organization root despite the request for a narrow resource scope.

Explanation

Correct Answer

B:

Similar email domains or shared parent company do not create automatic IAM trust between distinct identity tenants.

Incorrect Answers

A:

That action does not resolve the effective IAM permission and binding in this request. It leaves the effective access decision unaddressed. The appropriate action here is: Explicitly verify the principal's actual federated or Google identity, domain policies and intended role binding at the project scope.

C:

Changing audit collection cannot grant a denied permission or fix service behavior. The specific requirement concerns the effective access decision. The appropriate action here is: Explicitly verify the principal's actual federated or Google identity, domain policies and intended role binding at the project scope.

D:

That action does not resolve the effective IAM permission and binding in this request. The necessary distinction is the effective access decision. The appropriate action here is: Explicitly verify the principal's actual federated or Google identity, domain policies and intended role binding at the project scope.

Question 695

Developers in a sandbox project can impersonate a service account that also has production permissions. This creates an unintended path from development to production. Which IAM relationship should be narrowed?

  1. Remove excessive service-account impersonation/Token Creator bindings from sandbox principals and grant delegation only to reviewed production identities.
  2. Grant the production service account Owner on the sandbox; stronger target rights automatically block development impersonation.
  3. Add a Cloud Billing budget limit to production; it prevents any sandbox principal from calling IAM Credentials.
  4. Rename the shared service account; existing Token Creator grants can no longer refer to its numeric identity after a display-name change.

Explanation

Correct Answer

A:

Remove excessive service-account impersonation/Token Creator bindings from sandbox principals and grant delegation only to reviewed production identities. The ability to mint credentials for a privileged service account is granted to callers. Restricting that delegation closes the lateral-access path.

Incorrect Answers

B:

Grant the production service account Owner on the sandbox; stronger target rights automatically block development impersonation. Escalating the target service account does not restrict which untrusted principals may impersonate it and can increase impact.

C:

Add a Cloud Billing budget limit to production; it prevents any sandbox principal from calling IAM Credentials. Billing thresholds do not evaluate the permissions required for service-account impersonation or token minting.

D:

Rename the shared service account; existing Token Creator grants can no longer refer to its numeric identity after a display-name change. Service accounts have stable principal identities. Cosmetic renaming is not a reliable way to revoke existing delegation permissions.

Question 696

An operator uses gcloud projects get-iam-policy and sees no project-level role for an employee known to access the service. What else should be queried?

  1. Review the full effective IAM policy including organization/folder inherited bindings and remove or narrow the parent grant.
  2. Add another broad allow-role binding without checking inherited denies or restrictions.
  3. Inspect inherited folder/organization bindings and resource-level IAM grants relevant to the employee's request.
  4. Move the project between billing accounts to bypass an IAM authorization decision.

Explanation

Correct Answer

C:

Project-local policy output may not display inherited or individually scoped role bindings that still authorize a user.

Incorrect Answers

A:

That action does not resolve the effective IAM permission and binding in this request. The necessary distinction is the effective access decision. The appropriate action here is: Inspect inherited folder/organization bindings and resource-level IAM grants relevant to the employee's request.

B:

That action does not resolve the effective IAM permission and binding in this request. The case instead depends on the effective access decision. The appropriate action here is: Inspect inherited folder/organization bindings and resource-level IAM grants relevant to the employee's request.

D:

Billing changes payment responsibility, not the technical behavior of this workload. It leaves the effective access decision unaddressed. The appropriate action here is: Inspect inherited folder/organization bindings and resource-level IAM grants relevant to the employee's request.

Question 697

A local script uses an old OAuth token and fails even after its user receives a new role. What should be investigated?

  1. Refresh the authorized identity token and verify the underlying principal and effective roles against the API denial.
  2. Review and remove stale external principals from effective IAM bindings and test that no unauthorized alternate principal retains access.
  3. Add another broad allow-role binding without checking inherited denies or restrictions.
  4. Change only a user or project display name and expect IAM authorization to change.

Explanation

Correct Answer

A:

Role changes and cached access tokens are separate variables; stale or wrong-identity tokens can mislead IAM diagnosis.

Incorrect Answers

B:

That action does not resolve the effective IAM permission and binding in this request. The case instead depends on the effective access decision. The appropriate action here is: Refresh the authorized identity token and verify the underlying principal and effective roles against the API denial.

C:

That action does not resolve the effective IAM permission and binding in this request. It leaves the effective access decision unaddressed. The appropriate action here is: Refresh the authorized identity token and verify the underlying principal and effective roles against the API denial.

D:

Display names and labels identify resources; they do not enforce their runtime behavior. The specific requirement concerns the effective access decision. The appropriate action here is: Refresh the authorized identity token and verify the underlying principal and effective roles against the API denial.

Question 698

A least-privilege effort revokes an apparently unused permission, but a monthly background task fails because the previous review covered only one week. What evidence window is needed?

  1. Review workload access logs and scheduled job cycles over a representative period before permanently reducing permissions.
  2. Review and remove stale external principals from effective IAM bindings and test that no unauthorized alternate principal retains access.
  3. Move the project between billing accounts to bypass an IAM authorization decision.
  4. Change only a user or project display name and expect IAM authorization to change.

Explanation

Correct Answer

A:

An apparently unused permission in a short sample may be required by periodic or seasonal workflows.

Incorrect Answers

B:

That action does not resolve the effective IAM permission and binding in this request. It leaves the effective access decision unaddressed. The appropriate action here is: Review workload access logs and scheduled job cycles over a representative period before permanently reducing permissions.

C:

Billing changes payment responsibility, not the technical behavior of this workload. The specific requirement concerns the effective access decision. The appropriate action here is: Review workload access logs and scheduled job cycles over a representative period before permanently reducing permissions.

D:

Display names and labels identify resources; they do not enforce their runtime behavior. The necessary distinction is the effective access decision. The appropriate action here is: Review workload access logs and scheduled job cycles over a representative period before permanently reducing permissions.

Question 699

An organization-level custom IAM role will be retired, but it is currently referenced by bindings in many production projects. What migration control reduces outages and privilege gaps?

  1. Delete the custom role immediately; IAM converts every existing binding to the nearest predefined role automatically.
  2. Rename the old role to deprecated; a new title reassigns all bindings to a replacement permission set.
  3. Inventory every binding referencing the role, prepare reviewed replacement roles, migrate the principals and verify effective access before deletion.
  4. Replace the role with organization Owner for all members, because broad access is the required safe migration strategy.

Explanation

Correct Answer

C:

Inventory every binding referencing the role, prepare reviewed replacement roles, migrate the principals and verify effective access before deletion. A binding inventory and staged replacement preserve essential permissions while preventing accidental escalation before retirement.

Incorrect Answers

A:

Delete the custom role immediately; IAM converts every existing binding to the nearest predefined role automatically. Deleting a role without migrating bindings can remove permissions from dependent workloads; automatic conversion to another role must not be assumed.

B:

Rename the old role to deprecated; a new title reassigns all bindings to a replacement permission set. A role title change does not migrate principals or define which new permissions each production workload needs.

D:

Replace the role with organization Owner for all members, because broad access is the required safe migration strategy. Owner can overgrant large sets of permissions and would abandon the least-privilege intent of the custom role.

Question 700

A directory group is deleted but an inherited IAM binding still references its old principal identifier. What remediation is needed?

  1. Remove stale IAM policy bindings and replace them with the intended active managed group after verifying membership and resource scope.
  2. Verify the binding's exact group identifier and the user's actual Cloud Identity group membership and propagation.
  3. Change only a user or project display name and expect IAM authorization to change.
  4. Add another broad allow-role binding without checking inherited denies or restrictions.

Explanation

Correct Answer

A:

IAM policy objects can retain references to no-longer-active groups, creating access-review noise and possible future confusion.

Incorrect Answers

B:

That action does not resolve the effective IAM permission and binding in this request. The necessary distinction is the effective access decision. The appropriate action here is: Remove stale IAM policy bindings and replace them with the intended active managed group after verifying membership and resource scope.

C:

Display names and labels identify resources; they do not enforce their runtime behavior. The case instead depends on the effective access decision. The appropriate action here is: Remove stale IAM policy bindings and replace them with the intended active managed group after verifying membership and resource scope.

D:

That action does not resolve the effective IAM permission and binding in this request. It leaves the effective access decision unaddressed. The appropriate action here is: Remove stale IAM policy bindings and replace them with the intended active managed group after verifying membership and resource scope.

Associate Cloud Engineer Practice Tests