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 7

Question 60

A department creates a folder for delegated teams but grants only project-level permissions to its support operators. What is required to manage folder policies themselves?

  1. Grant a supported folder-management role with the needed policy permissions at the folder scope.
  2. Give users Compute Instance Admin on every project under the folder.
  3. Grant Billing Account Viewer on the account paying for these projects.
  4. Add the group to the first child project only, then inherit the role upward to the folder.

Explanation

Correct Answer

A:

The operation concerns the folder resource itself. Grant the least-privileged role that permits the intended folder policy update at that scope, rather than assuming descendant project permissions confer ancestor administration.

Incorrect Answers

B:

VM permissions do not include administration of parent Resource Manager folder policies.

C:

Reading billing data is independent of changing access on a resource folder.

D:

IAM policy inheritance flows downward from parents, not upward from child projects.

Question 61

A group wants new projects to automatically inherit restrictive logging policies from a parent without copying IAM rules to each project. Which design works?

  1. Copy every logging rule into each project as an isolated local setting.
  2. Apply the parent logging settings but omit the destination log bucket's retention configuration.
  3. Use billing labels as the only way to enforce retention on log buckets.
  4. Place the projects under the governed parent and configure the supported centralized logging controls for that scope.

Explanation

Correct Answer

D:

Use the shared ancestry to apply supported organization/folder-scoped logging settings, such as centralized log routing, and set the destination’s retention policy. Distinguish inheritable controls from service settings that must be configured on the target buckets.

Incorrect Answers

A:

Per-project copies can drift and do not fulfill the request for an inherited centralized baseline.

B:

Inherited routing and destination retention are distinct controls. A central routing setup alone cannot guarantee the required retention period.

C:

Billing labels do not impose log routing or retention requirements.

Question 62

A company already has an organization resource associated with its corporate Cloud Identity account. A team wants a second separate organization resource under that same identity account solely to isolate development projects. Which design follows the documented relationship?

  1. Create a second organization resource under the same Cloud Identity account; one identity account supports unlimited independent organization roots.
  2. Use a second Cloud Billing account and assume it becomes another organization resource with a separate IAM hierarchy.
  3. Rename an existing development project to the organization ID; changing a project name changes its resource root.
  4. Keep the identity account's existing organization resource and separate development with projects/folders, or provision distinct managed identity if a separate organization is truly required.

Explanation

Correct Answer

D:

Keep the identity account's existing organization resource and separate development with projects/folders, or provision distinct managed identity if a separate organization is truly required. Google documents a one-to-one mapping between each managed identity account and its organization resource. Folders and projects provide ordinary environment boundaries.

Incorrect Answers

A:

Create a second organization resource under the same Cloud Identity account; one identity account supports unlimited independent organization roots. Google associates one Cloud Identity or Workspace account with exactly one organization resource. Unlimited roots under one account are not supported.

B:

Use a second Cloud Billing account and assume it becomes another organization resource with a separate IAM hierarchy. Billing accounts determine who pays for project usage; creating another does not create a separate Resource Manager organization root.

C:

Rename an existing development project to the organization ID; changing a project name changes its resource root. Project names are mutable display metadata and cannot convert a child project into an organization resource.

Question 63

An enterprise creates projects under individual unmanaged Google accounts but expects a company-wide Google Cloud organization resource in the resource selector. What prerequisite should it verify?

  1. Verify that an appropriate Cloud Identity or Google Workspace domain is configured and that the caller can view its organization resource.
  2. Increase the corporate Cloud Billing budget, because the organization resource appears automatically when budget spending exceeds the threshold.
  3. Rename every project with the same company prefix; matching project names automatically create an organization resource.
  4. Grant project Editor to an employee; that permission changes the root resource hierarchy from no organization to an enterprise organization.

Explanation

Correct Answer

A:

Verify that an appropriate Cloud Identity or Google Workspace domain is configured and that the caller can view its organization resource. Google Cloud organizations are associated with a managed Cloud Identity or Workspace setup. Checking domain provisioning and access to the organization addresses the missing governance root.

Incorrect Answers

B:

Increase the corporate Cloud Billing budget, because the organization resource appears automatically when budget spending exceeds the threshold. Cloud Billing budgets monitor financial thresholds; they do not provision the administrative organization resource that owns the project hierarchy.

C:

Rename every project with the same company prefix; matching project names automatically create an organization resource. Names are labels, not domain provisioning. A naming convention cannot create a root organization in Resource Manager.

D:

Grant project Editor to an employee; that permission changes the root resource hierarchy from no organization to an enterprise organization. Project resource editing is scoped below the organization. A role grant on a project does not create an organization resource.

Question 64

A hierarchy audit requires only descendants of a newly formed subsidiary to inherit a distinct access baseline. Which mechanism avoids broad organization-wide grants?

  1. Give the subsidiary an organization-wide auditing role and depend on naming conventions for isolation.
  2. Grant every new subsidiary project its own unrelated organization-level Owner.
  3. Create one billing account for the subsidiary and assume it carries access roles to its projects.
  4. Create a subsidiary folder and bind baseline access there for only the intended principals.

Explanation

Correct Answer

D:

A folder boundary provides a common ancestor for subsidiary projects. Roles granted at that folder can be inherited by its descendants without extending the same grants to peer divisions elsewhere in the organization.

Incorrect Answers

A:

Organization-level access would also cover unrelated divisions even if their projects have different names.

B:

Broad ownership is unnecessary for establishing an inherited access baseline and weakens separation.

C:

A billing account is not the IAM hierarchy that passes role bindings to descendant resources.

Question 65

Two project administrators plan to create separate organization resources simply to separate staging and production traffic. What less disruptive configuration usually fits?

  1. Use separate firewall rules within a single shared project without revisiting access boundaries for the environments.
  2. Create an organization per environment, each linked to the same project.
  3. Treat two billing budgets as complete network segregation.
  4. Keep one organization, use separate projects or folders, and apply distinct network and access policies.

Explanation

Correct Answer

D:

Projects and folders provide governance boundaries beneath the enterprise organization, while VPC configurations and IAM policies establish actual network and access separation. Separate organization roots are usually unnecessary merely to distinguish staging from production.

Incorrect Answers

A:

Firewall isolation helps traffic segmentation, but a shared project may not meet the stated governance separation requirement.

B:

A single project belongs within one resource hierarchy; duplicating organizations does not create useful environment boundaries.

C:

Billing budgets monitor costs and cannot isolate traffic or permissions.

Question 66

An operator has two projects that display the name "production". Before using gcloud to delete a VM, which project identifier should be checked to avoid targeting the similarly named sandbox?

  1. The mutable project display name alone, since Cloud Resource Manager requires every display name to be globally unique.
  2. The current Cloud Billing budget title, since budgets are immutable identifiers for compute API requests.
  3. The project's folder display name, because the VM API always addresses projects by folder label.
  4. The verified immutable project ID or numeric project number, with the intended project explicitly selected in the command.

Explanation

Correct Answer

D:

The verified immutable project ID or numeric project number, with the intended project explicitly selected in the command. Project IDs are globally unique and permanent after creation; project numbers are also unique. Using the verified identifier prevents name confusion.

Incorrect Answers

A:

The mutable project display name alone, since Cloud Resource Manager requires every display name to be globally unique. Google permits duplicate project display names and lets them change. Such a name is not a safe target selector for a destructive API call.

B:

The current Cloud Billing budget title, since budgets are immutable identifiers for compute API requests. Budget names are financial administration labels and do not identify a project for Compute Engine resource operations.

C:

The project's folder display name, because the VM API always addresses projects by folder label. Folder labels describe hierarchy grouping, not the unique project identifier required by Google Cloud resource APIs.

Question 67

A contractor departs but remains authorized through a Cloud Identity group that grants project access. Where should the first access removal occur?

  1. Rename the contractor’s service accounts to mark them as inactive.
  2. Remove only the contractor's direct project binding while leaving the group's access grant intact.
  3. Remove the contractor from the access-granting group and verify there are no other active grants.
  4. Delete the project-wide role definition so other staff also lose access.

Explanation

Correct Answer

C:

The contractor receives effective access because the group is bound to a project role. Removing the member from that group addresses the source of this grant; also check direct or other inherited grants before confirming deprovisioning.

Incorrect Answers

A:

Renaming identities does not revoke access granted to the contractor’s user through group membership.

B:

The contractor can continue to obtain access through group membership even after a separate direct binding is removed.

D:

Deleting the shared role or binding would disrupt legitimate users and is not the least-disruptive offboarding action.

Question 68

A new employee is added to a Google Cloud role binding directly while the team manages permissions through Cloud Identity groups. What correction improves centralized lifecycle management?

  1. Duplicate the direct individual binding on all projects to make revocation easier.
  2. Keep direct access forever so the identity provider cannot remove it.
  3. Bind the appropriate role to a managed employee group and maintain membership through the lifecycle workflow.
  4. Use the employee’s display name as the only signal for access eligibility.

Explanation

Correct Answer

C:

Group-based IAM grants let a centrally managed group represent the job function. Provisioning and removal of membership can then control routine access without editing every project’s allow policy for each hire or departure.

Incorrect Answers

A:

Duplicating individual grants increases administrative work and makes offboarding harder.

B:

Permanent direct grants undermine central membership changes and may outlive employment.

D:

Display names are mutable and do not provide a reliable membership or authorization control.

Question 69

A team manually creates every user account while its identity provider already runs an automated employee lifecycle feed. Which integration should be assessed?

  1. Keep manual cloud accounts and disable the identity provider feed.
  2. Grant every incoming employee organization Owner until their real role is known.
  3. Use the identity provider’s reports as the sole authorization source without provisioning accounts.
  4. Integrate the enterprise directory’s supported automated provisioning and deprovisioning with managed identities.

Explanation

Correct Answer

D:

A supported automated identity provisioning workflow can synchronize hires, updates and departures with the managed identity system. Keep authorization separate: provision users first, then grant only the groups and roles needed for their jobs.

Incorrect Answers

A:

Ignoring the available lifecycle feed preserves the manual bottleneck and risks delayed offboarding.

B:

An organization-wide Owner grant is not a safe substitute for identity provisioning or role assignment.

C:

Directory reports do not actually create, suspend, or remove managed identities.

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.

Associate Cloud Engineer Practice Tests