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 8

Question 70

A user claims they have been removed from a group but still sees resources through a separate direct IAM role. What should investigation include?

  1. Assume group removal immediately erases every direct role on the user.
  2. Restore the group membership so the access path becomes predictable.
  3. Remove the user's access in just one project without checking inherited bindings from the parent folder.
  4. Inspect direct, group-based, and inherited IAM bindings that may still grant the same permission.

Explanation

Correct Answer

D:

Effective permissions may be supplied by several independent bindings. Check the user’s direct grants and any other group or ancestor grants, then remove only unauthorized access paths and allow for propagation.

Incorrect Answers

A:

Removing a group membership does not revoke a separate direct IAM grant.

B:

Adding the user back to the group restores an access path instead of fixing excessive permission.

C:

A folder-level or organization-level role may still provide access in that same project after local cleanup.

Question 71

A managed Cloud Identity employee account is suspected of compromise. Security must prevent new sign-ins but preserve company email and documents for investigation. Which identity action matches both requirements?

  1. Delete the user permanently and then request that all historical data be recreated from future log events.
  2. Remove the employee from one project Viewer group only; every other Google service sign-in is thereby disabled.
  3. Suspend the managed user account through the organization's identity administration controls.
  4. Change the display name of the user; the Google login session is revoked automatically by any name change.

Explanation

Correct Answer

C:

Suspend the managed user account through the organization's identity administration controls. Google Workspace administration supports suspending users, blocking access while retaining email, documents, calendars, and other account data.

Incorrect Answers

A:

Delete the user permanently and then request that all historical data be recreated from future log events. Permanent deletion is contrary to the requirement to preserve the managed account and its data, and restoration may not be possible.

B:

Remove the employee from one project Viewer group only; every other Google service sign-in is thereby disabled. Changing one Google Cloud group removes that permission path, not all identity sign-ins or other existing application access.

D:

Change the display name of the user; the Google login session is revoked automatically by any name change. A display-name change is not an account suspension or security-response action to prevent further authentication.

Question 72

An organization must add outside collaborators to one project without giving them membership in a broad internal employee group. Which access model should it use?

  1. Grant the external collaborator only the required project-level role, subject to the organization’s external-sharing controls.
  2. Add the collaborator to the all-employees group to make the new access inherit broadly.
  3. Set the project Owner role for the collaborator because outside identities need extra permissions.
  4. Grant the external collaborator organization Viewer and rely on project names for segregation.

Explanation

Correct Answer

A:

An IAM binding scoped to the requested project can authorize a specific external principal without adding it to broad internal groups. Confirm that the organization permits the external identity and that the role is limited to the actual collaboration task.

Incorrect Answers

B:

Internal employee groups can carry permissions unrelated to the one external project.

C:

The Owner role greatly exceeds typical collaboration needs and is not inherently required for outside users.

D:

Organization-wide grants expose unrelated projects, regardless of how those projects are named.

Question 73

A role binding grants data access to a group, but one newly hired user's membership has not propagated. What should the team investigate?

  1. Give the user an organization Owner role as a workaround for pending membership.
  2. Recreate the resource project because a group membership cannot change later.
  3. Disable all IAM Conditions on the folder and immediately retry.
  4. Check the directory membership update and propagation state before modifying the project’s group binding.

Explanation

Correct Answer

D:

The project binding grants access to the group, not directly to the new employee. Confirm that the directory recognizes the user’s membership and that the change has propagated before changing resource permissions that already work for other members.

Incorrect Answers

A:

A broad role would bypass least privilege and conceal the actual lifecycle issue.

B:

Groups and IAM can reflect membership changes; project recreation is unnecessary.

C:

Conditions are not shown to cause the missing membership in this scenario.

Question 74

A cloud administrator uses a personal Gmail login for regulated projects where company-owned identity administration is mandatory. What identity correction is appropriate?

  1. Keep the personal account and add a corporate display name to its profile.
  2. Use a company-managed Cloud Identity or Workspace account with centrally administered policies.
  3. Give the personal account project Owner and require written approval for every login.
  4. Link the personal Gmail account to the corporate billing account as the sole remediation.

Explanation

Correct Answer

B:

An enterprise-managed account supports controlled provisioning, sign-in policies, suspension and account recovery. Migrating regulated project access to the managed identity supports the stated compliance requirement without relying on personally administered credentials.

Incorrect Answers

A:

A display name does not place a consumer account under corporate identity governance.

C:

More IAM privileges do not provide centralized identity lifecycle control.

D:

Billing linkage does not convert a personal login into a company-managed identity.

Question 75

Security must investigate privileges assigned through supported nested Google Groups, not just IAM bindings that name individual employees. What evidence gives the complete access picture?

  1. Check only the direct user addresses listed in project IAM bindings.
  2. Trace the relevant group and nested-group membership, then combine it with effective IAM bindings.
  3. Inspect only the root group's membership and ignore nested members included in its effective membership.
  4. Assume a group binding grants access only to the group administrator.

Explanation

Correct Answer

B:

The audit must connect resource-role bindings to the membership graph of the granted groups, including eligible nested members. Resolve the effective principal set and scope before concluding who can perform a privileged operation.

Incorrect Answers

A:

Direct user bindings omit permissions inherited through groups and potentially nested membership.

C:

A direct-members-only list can omit identities authorized through supported nested-group membership.

D:

A group principal is not a proxy for its administrator alone; authorized membership can confer its bound permissions.

Question 76

A workforce member needs interactive console access from an external corporate IdP without creating a Google-managed password for each person. What capability is relevant?

  1. Create a shared Google account and distribute its password to the workforce.
  2. Create a service account per employee and have users share service-account keys.
  3. Grant the external IdP organization Owner without configuring Google Cloud trust.
  4. Configure Workforce Identity Federation with the approved corporate IdP and scoped IAM grants.

Explanation

Correct Answer

D:

Workforce Identity Federation accepts supported external identity assertions and maps users to Google Cloud workforce principals. Administrators can then grant the relevant resources to those principals without issuing a separate Google-managed password to each person.

Incorrect Answers

A:

A shared password removes accountability and cannot preserve per-user identity or least privilege.

B:

Service-account keys are workload credentials, not a suitable substitute for interactive user federation.

C:

An unrelated role grant cannot establish a trusted IdP-to-workforce identity mapping.

Question 77

An external engineer successfully signs in using Workforce Identity Federation but receives permission denied when listing project atlas resources. The workforce provider is valid. Which authorization step is missing?

  1. Assign the engineer to the corporate Cloud Billing Administrator group; billing grants are a substitute for all project IAM.
  2. Grant the minimum resource IAM role on atlas to the correct workforce principal or principal set and verify its identifier.
  3. Rename the workforce pool to atlas so Google Cloud automatically grants resource permissions to its members.
  4. Enable another SAML authentication flow; successful authentication inherently authorizes every project in that organization.

Explanation

Correct Answer

B:

Grant the minimum resource IAM role on atlas to the correct workforce principal or principal set and verify its identifier. Federation proves identity, not project authorization. Google documents workforce principal identifiers for IAM allow bindings to target resources.

Incorrect Answers

A:

Assign the engineer to the corporate Cloud Billing Administrator group; billing grants are a substitute for all project IAM. Billing permissions are separate from the IAM permissions required to list project resources; this is not a payment administration failure.

C:

Rename the workforce pool to atlas so Google Cloud automatically grants resource permissions to its members. A pool display name does not become a project resource role binding and cannot replace a grant to the authenticated principal.

D:

Enable another SAML authentication flow; successful authentication inherently authorizes every project in that organization. Repeating authentication cannot create a missing IAM allow binding. Authentication and authorization are separate enforcement steps.

Question 78

A workforce identity pool maps the assertion attribute department. Only external users with department=finance may view a billing report. How should the IAM binding limit the audience?

  1. Grant the scoped report role to a workforce principalSet restricted to the validated department=finance attribute value.
  2. Grant the role to principalSet for the entire workforce pool and rely on each employee to read only their own department.
  3. Grant the role to allUsers because an external workforce identity is not represented as an IAM principal.
  4. Change the report dataset name to finance; names automatically filter workforce authentication claims.

Explanation

Correct Answer

A:

Grant the scoped report role to a workforce principalSet restricted to the validated department=finance attribute value. Mapped workforce attributes can form principalSet identifiers. Binding to the finance value limits which federated identities receive the approved role.

Incorrect Answers

B:

Grant the role to principalSet for the entire workforce pool and rely on each employee to read only their own department. A pool-wide principalSet includes all eligible users regardless of department and would expose the report to unrelated teams.

C:

Grant the role to allUsers because an external workforce identity is not represented as an IAM principal. Federated workforce users have supported IAM principal identifiers. Public access would evade the intended department restriction.

D:

Change the report dataset name to finance; names automatically filter workforce authentication claims. Renaming a resource has no effect on the identity provider's claims or the IAM principal selector used for access.

Question 79

A workforce identity token is accepted from an unapproved tenant because the provider trust rules are overly broad. What must be fixed?

  1. Increase the lifetime of all workforce identity tokens to avoid sign-in failures.
  2. Restrict the trusted issuer or tenant and enforce a provider attribute condition for approved identities.
  3. Assign project Editor to every external subject so the token can be evaluated.
  4. Disable audit logging for the workforce pool until the tenant list is repaired.

Explanation

Correct Answer

B:

An external IdP can sometimes use a shared issuer across tenants. The federation provider must validate issuer-related trust and tenant-specific assertion attributes, so an approved tenant can sign in while an unapproved tenant is rejected.

Incorrect Answers

A:

Longer-lived tokens do not determine which source tenants are trusted and would increase exposure.

C:

IAM grants authorize resource access after identity verification; they cannot fix an overly permissive federation trust boundary.

D:

Disabling audit evidence hides the problem without restricting which identities may authenticate.

Question 80

A user successfully signs in through the enterprise IdP but a Google Cloud session is denied due to a missing workforce federation mapping. What component should be inspected?

  1. Grant all federated users organization Owner so the provider mapping is optional.
  2. Update a project IAM binding to refer to an unrecognized workforce subject string without fixing mapping.
  3. Inspect the workforce provider’s claim mappings and the principal identifiers used by IAM bindings.
  4. Create a user-managed service account key and have employees sign in with it.

Explanation

Correct Answer

C:

Successful IdP authentication is only part of federation. Google Cloud must map the IdP’s assertions into the expected workforce subject or attribute identifiers and match those principals to resource IAM bindings.

Incorrect Answers

A:

Broad resource permissions cannot replace a valid mapping from external assertions to workforce principals.

B:

A principal that does not match the provider's actual mapped identity will not fix the authorization mismatch.

D:

Service-account keys are workload credentials and do not repair a missing interactive-user mapping.

Associate Cloud Engineer Practice Tests