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 1

Question 1

A contractor needs read-only inventory access to the Compute Engine VMs in project atlas. An existing Viewer grant at the shared analytics folder also exposes sibling projects. Which change restricts access to the one authorized project?

  1. Give the contractor the Viewer role at the organization instead of the analytics folder.
  2. Remove the folder-level Viewer binding and grant only the required Compute Engine inventory permissions on project atlas.
  3. Leave the folder grant and add a second, narrower Viewer binding on project atlas.
  4. Create a new folder named atlas without moving the project or changing the existing role bindings.

Explanation

Correct Answer

B:

Remove the folder-level Viewer binding and grant only the required Compute Engine inventory permissions on project atlas. An allow-policy binding made at the folder flows to its descendant projects. Removing that inherited grant and assigning the minimum inventory role in atlas keeps the intended visibility while excluding siblings.

Incorrect Answers

A:

Give the contractor the Viewer role at the organization instead of the analytics folder. A grant at the organization would inherit into even more projects. It broadens the scope of a contractor who is authorized to inspect only atlas.

C:

Leave the folder grant and add a second, narrower Viewer binding on project atlas. IAM allow grants are additive. The existing folder-level binding would still provide access to every descendant; another project binding does not subtract those privileges.

D:

Create a new folder named atlas without moving the project or changing the existing role bindings. An empty folder changes neither the ancestry of atlas nor the parent role binding. Effective access remains inherited from the existing analytics folder.

Question 2

A deleted service account was replaced with a newly created account using the same email address. Its applications receive permission denied, and IAM still lists a deleted principal. What restores the intended access to the new account?

  1. Assume the deleted account's previous IAM role bindings automatically apply to the replacement because the emails match.
  2. Identify the replacement service account, grant its approved roles explicitly and clean up stale deleted-principal bindings.
  3. Change the replacement account's display name to exactly match the deleted account and retry without updating IAM.
  4. Grant the replacement service account organization-level Owner so that its old project bindings are no longer relevant.

Explanation

Correct Answer

B:

Identify the replacement service account, grant its approved roles explicitly and clean up stale deleted-principal bindings. Google documents that a recreated account is a separate principal even when it has the same address. The replacement needs fresh, reviewed role bindings; stale deleted-principal entries should not be treated as authorization.

Incorrect Answers

A:

Assume the deleted account's previous IAM role bindings automatically apply to the replacement because the emails match. IAM distinguishes the deleted principal from a new account using a unique numeric identity. Reusing an email string does not restore its former resource role assignments.

C:

Change the replacement account's display name to exactly match the deleted account and retry without updating IAM. Changing the display name cannot change the new account's unique identity, and IAM authorization checks will still not use the deleted principal's former binding.

D:

Grant the replacement service account organization-level Owner so that its old project bindings are no longer relevant. A project workload should not receive sweeping organization permissions to compensate for missing resource roles. This creates excessive access without correctly reconstructing approved entitlements.

Question 3

An organization-level IAM deny policy blocks a production administrator from a permission. They add a project-level allow-role binding for that same permission. What is the result if the deny rule applies to this principal?

  1. The project allow always overrides the deny because it is closer to the protected resource.
  2. The applicable deny still blocks the permission; an approved policy exception or deny-rule change is required.
  3. The permission becomes available only after the principal signs out and refreshes the browser.
  4. Granting the project Owner role automatically suppresses all inherited deny policies.

Explanation

Correct Answer

B:

The applicable deny still blocks the permission; an approved policy exception or deny-rule change is required. A deny policy attached at the organization is inherited down the hierarchy. When it matches the principal and permission, another allow-role binding cannot make the operation succeed.

Incorrect Answers

A:

The project allow always overrides the deny because it is closer to the protected resource. The Google IAM evaluation order is not simply nearest binding wins. A matching deny rule takes precedence over an allow grant, including one on the target project.

C:

The permission becomes available only after the principal signs out and refreshes the browser. An expired identity token can affect authentication, but refreshing a session does not change the effective policy decision imposed by an applicable deny rule.

D:

Granting the project Owner role automatically suppresses all inherited deny policies. Basic Owner grants broad permissions but does not override explicit IAM deny policies. Escalating the allow role would not remove the denied permission.

Question 4

An engineer needs project-scoped deployment permission for three days. The role supports IAM Conditions, and security requires automatic expiration without manual revocation. What should the administrator configure?

  1. Grant the selected role permanently and create a calendar reminder to revoke it in three days.
  2. Bind the selected role at the project with a request.time expiration condition for the approved cutoff.
  3. Assign the basic Editor role without a condition because project-level grants expire when the deployment ends.
  4. Add the engineer to a permanent organization-level Owner group for the duration of the deployment ticket.

Explanation

Correct Answer

B:

Bind the selected role at the project with a request.time expiration condition for the approved cutoff. IAM Conditions support time-based expressions on eligible non-basic-role bindings. Access checks stop granting the conditional role after the configured request-time cutoff.

Incorrect Answers

A:

Grant the selected role permanently and create a calendar reminder to revoke it in three days. A reminder does not enforce the cutoff. If the manual step is missed, the principal retains the role after the authorized period.

C:

Assign the basic Editor role without a condition because project-level grants expire when the deployment ends. A project binding does not inherit a deployment-task expiration. Basic roles such as Editor also cannot be granted with IAM Conditions in this configuration.

D:

Add the engineer to a permanent organization-level Owner group for the duration of the deployment ticket. Organization Owner would grant much broader access and membership would remain until removed. It neither enforces a three-day expiry nor least privilege.

Question 5

Two project owners disagree whether an organization-level role still applies after assigning a narrower role inside one project. How should effective access be assessed?

  1. Check only the role most recently added directly to the project.
  2. Evaluate project and inherited ancestor grants, then apply any applicable deny rules.
  3. Assume the new narrower project grant replaces the organization grant.
  4. Remove the user from the project to revoke all organization permissions.

Explanation

Correct Answer

B:

IAM allow bindings are additive across a resource hierarchy. The effective access calculation includes grants attached to the project and its ancestors; a narrower project role does not cancel a broader inherited one. Applicable deny policies must also be evaluated.

Incorrect Answers

A:

A recent project binding does not describe effective access inherited from its organization or folders.

C:

Adding a limited role cannot subtract an existing broader grant. Both grants may still apply.

D:

Project membership changes cannot independently revoke a role granted at a parent organization.

Question 6

A security auditor must distinguish IAM grants attached directly to project atlas from role bindings inherited from its parent folder. Which review captures both sources of effective permission?

  1. Open only the project's local allow-policy bindings and assume all inherited roles are copied into that policy.
  2. Search project labels because labels contain the identity of every user with inherited IAM access.
  3. Inspect the billing account's administrators, because billing account roles define access to project resources.
  4. Inspect the project's effective IAM access together with the separate allow bindings attached to its folder and organization ancestors.

Explanation

Correct Answer

D:

Inspect the project's effective IAM access together with the separate allow bindings attached to its folder and organization ancestors. Google Cloud resource hierarchy lets role bindings flow from organizations and folders to descendants. Reading the effective policy plus ancestor bindings distinguishes inherited access from directly assigned roles.

Incorrect Answers

A:

Open only the project's local allow-policy bindings and assume all inherited roles are copied into that policy. Direct project bindings alone omit the parent bindings that still apply to descendant resources. Reading only the local allow policy produces an incomplete view of effective access.

B:

Search project labels because labels contain the identity of every user with inherited IAM access. Labels classify cloud resources but are not a list of principals and inherited role bindings; they do not answer which IAM grant came from the folder.

C:

Inspect the billing account's administrators, because billing account roles define access to project resources. Cloud Billing IAM controls cost and account administration separately. It does not reconstruct the set of resource IAM roles inherited from the project's ancestors.

Question 7

A developer changes a role in one project and expects employees' access across three peer projects to change immediately. Which resource hierarchy rule invalidates that assumption?

  1. Wait for the role change to propagate from the first project to its siblings.
  2. Copy the new role definition to every project; bindings are shared automatically.
  3. Grant the role at the billing account because it is the parent of all billed projects.
  4. Make a common-ancestor binding if all three projects need access; a project grant does not cover sibling projects.

Explanation

Correct Answer

D:

Allow policies inherit down the organization and folder tree. A role granted on one project applies to that project and descendants, not its peers. Bind at an authorized common folder or organization only when the same access is required across all three.

Incorrect Answers

A:

Propagation applies to a binding within its scope, not to unrelated sibling projects.

B:

Defining a role does not assign it to principals in other projects. Each relevant binding needs an authorized scope.

C:

A billing account controls payment administration and is not the IAM ancestry of a project.

Question 8

An app operator attaches the primitive Owner role to a telemetry export job that only writes objects into one bucket. How should access be corrected?

  1. Replace Owner with Storage Admin at the organization level for the same service account.
  2. Remove Owner and grant a suitable object-creation role on only the destination bucket.
  3. Keep Owner until the next quarterly review and add a bucket-level Viewer role for the exporter.
  4. Replace Owner with project Editor, which is restricted to storage writes.

Explanation

Correct Answer

B:

An export process that only creates objects should receive a narrowly scoped storage role on its destination. Removing project Owner eliminates broad administration capabilities, and the bucket-level binding limits access to the intended data location.

Incorrect Answers

A:

Storage administration at organization scope still grants more privileges and resources than the exporter needs.

C:

Adding a narrower grant does not reduce existing Owner permissions. The workload would retain excessive access until Owner is removed.

D:

Editor remains a broad project role; it is not a storage-only permission set.

Question 9

A Google Cloud project is moved to a new folder and suddenly a service account gains an inherited ability to read sibling telemetry resources. What should security review first?

  1. Compare only the service account key creation dates before and after the move.
  2. Check whether Cloud Billing changed when the project was assigned a new folder.
  3. Inspect IAM grants on the new parent path and compare them with the old folder hierarchy.
  4. Check the project's local IAM bindings only and assume the move did not change inherited access.

Explanation

Correct Answer

C:

Moving a project changes its ancestor chain. Grants bound at the new folder or organization can become effective in the project, while old inherited grants can disappear. Comparing both ancestor paths pinpoints the permission change before editing policies.

Incorrect Answers

A:

A service account key rotation does not explain a role newly inherited from a folder.

B:

Billing association does not account for the newly observed authorization to read data.

D:

Local bindings alone omit folder and organization grants that can change when a project moves.

Question 10

A department wants to remove an inherited permission from one child project without removing the legitimate parent role for other children. Which access-control control should it evaluate?

  1. Attach a narrower project Viewer role; it automatically supersedes the inherited role.
  2. Remove the parent grant, even if other child projects still need it.
  3. Use a project label named deny-permissions to negate inherited IAM roles.
  4. Evaluate a scoped IAM deny policy or restructure the parent grant for this one project.

Explanation

Correct Answer

D:

A targeted deny rule can prevent a permission within a defined scope, subject to supported permissions and principal rules. Alternatively, reorganize the inherited allow grant so it excludes the exceptional child. Neither approach relies on a child allow binding to subtract access.

Incorrect Answers

A:

IAM allow roles add access; a narrower local role cannot remove permissions granted by an ancestor.

B:

Deleting the shared parent grant would disrupt legitimate access in the other descendant projects.

C:

Labels classify resources; a label does not function as an authorization deny rule.

Associate Cloud Engineer Practice Tests