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 2

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.

Question 11

Two administrators modify the same IAM allow policy concurrently. Which update procedure prevents one administrator from silently overwriting the other's change?

  1. Read the latest policy, modify that version and submit the update with its current etag; reread and retry if the etag conflicts.
  2. Remove the etag to make IAM prefer the most recently submitted full policy document.
  3. Upload the entire policy repeatedly until one request succeeds, without rereading current bindings.
  4. Increase API quotas because concurrent policy writes are resolved by the quota allocation.

Explanation

Correct Answer

A:

Read the latest policy, modify that version and submit the update with its current etag; reread and retry if the etag conflicts. The etag implements optimistic concurrency control on IAM allow-policy updates. A stale etag causes a conflict instead of overwriting a newer policy, so the editor must reread and retry the change.

Incorrect Answers

B:

Remove the etag to make IAM prefer the most recently submitted full policy document. Omitting concurrency protection exposes the read-modify-write race: the later full-policy write can erase bindings added by the other administrator.

C:

Upload the entire policy repeatedly until one request succeeds, without rereading current bindings. Blind retries can keep submitting the same stale bindings. Correct recovery requires a fresh read and reapplication of the intended edit to that newer version.

D:

Increase API quotas because concurrent policy writes are resolved by the quota allocation. Write conflicts are about concurrent state versions, not consumed service quota. A larger request allowance does not stop lost updates.

Question 12

A developer is in the Google Group [email protected]. The group has a Viewer role on project atlas, but the developer's individual email is absent from its IAM binding list. What explains how access is granted?

  1. Google Cloud requires a separate individual Viewer binding for every member of a group before they can read project resources.
  2. A Cloud Billing account automatically mirrors all IAM group members as individual project resource administrators.
  3. An IAM binding can name a group principal; eligible current group members inherit the granted permissions without individual bindings.
  4. Every member of a role-bearing group receives the project Owner role regardless of the role named in the binding.

Explanation

Correct Answer

C:

An IAM binding can name a group principal; eligible current group members inherit the granted permissions without individual bindings. The binding grants its named role to the group principal. A member's effective permissions can therefore include the group's Viewer role even though the individual address does not appear as a separate binding.

Incorrect Answers

A:

Google Cloud requires a separate individual Viewer binding for every member of a group before they can read project resources. Group principals are a supported IAM member type. Direct individual bindings are not a prerequisite for group membership to confer a role.

B:

A Cloud Billing account automatically mirrors all IAM group members as individual project resource administrators. Billing access is a separate permission surface and does not create project resource IAM membership on behalf of group principals.

D:

Every member of a role-bearing group receives the project Owner role regardless of the role named in the binding. Group membership conveys the role actually bound to the group; a Viewer binding does not escalate its members to Owner.

Question 13

A project owner confuses payment responsibility with the cloud resource hierarchy and assumes a billing account is the parent of a project. How should this be corrected?

  1. Create a new Cloud Billing account and use it as the parent of the project.
  2. Move the project beneath a billing account in the resource hierarchy.
  3. Keep the organization/folder/project hierarchy and link the project to its paying Cloud Billing account.
  4. Grant Billing Account Viewer to every project Editor to make the parent relationship appear.

Explanation

Correct Answer

C:

The project remains under its existing organization or folder for governance. Its billing association determines which approved account pays for consumption without changing IAM inheritance, location or resource ancestry.

Incorrect Answers

A:

Billing accounts pay charges but are not parent nodes in the Cloud Resource Manager tree.

B:

The resource hierarchy contains organizations, folders and projects. Billing links are separate associations, not moves.

D:

Viewer permissions affect cost visibility; they do not change the project’s parent or billing association.

Question 14

A new production project is configured to deploy Cloud Run. The deployment fails because the project has no active Cloud Billing account; the Cloud Run API is already enabled. Which prerequisite fixes the stated blocker?

  1. Grant the developer Billing Account Viewer and leave the project without any paying billing association.
  2. Link the project to an active, approved Cloud Billing account with the required billing association permissions.
  3. Increase the Cloud Run request timeout so billing can become active after the container starts.
  4. Enable Cloud Logging sinks in the project to supply the missing payment authorization.

Explanation

Correct Answer

B:

Link the project to an active, approved Cloud Billing account with the required billing association permissions. Cloud Run has billable resources, so a supported active billing association is required. Enabling the API alone does not supply the project payment link.

Incorrect Answers

A:

Grant the developer Billing Account Viewer and leave the project without any paying billing association. Billing Account Viewer controls financial visibility and does not itself assign a paying account to a project. The stated failure is a missing billing link.

C:

Increase the Cloud Run request timeout so billing can become active after the container starts. Request timeout applies to execution of HTTP requests after a service exists. It cannot activate project billing for a blocked deployment.

D:

Enable Cloud Logging sinks in the project to supply the missing payment authorization. Log routing stores or exports operational events. It does not authorize charges or attach a Cloud Billing account to the new project.

Question 15

One company operates under a single Google Cloud organization, but two legal entities must pay independently for their respective project usage. Which billing structure meets that requirement?

  1. Create two additional Google Cloud organizations because an organization can link to only one billing account.
  2. Use labels on all resources but keep both entities on a single billing account, claiming labels change the payer.
  3. Give both finance teams Billing Account Viewer on one account and expect IAM visibility to split legal payment ownership.
  4. Use separate Cloud Billing accounts and link each entity's projects to its approved paying account while retaining the organization hierarchy.

Explanation

Correct Answer

D:

Use separate Cloud Billing accounts and link each entity's projects to its approved paying account while retaining the organization hierarchy. Each project can link to one active billing account, and a billing account can pay for multiple projects. Different legal entities can each own an account without changing the organization tree.

Incorrect Answers

A:

Create two additional Google Cloud organizations because an organization can link to only one billing account. A Google Cloud organization is a governance hierarchy; it can contain projects linked to different billing accounts. Separate legal payers do not require separate organizations.

B:

Use labels on all resources but keep both entities on a single billing account, claiming labels change the payer. Labels provide reporting or allocation dimensions but do not transfer charges to a separate paying account. The legal payers would still share an invoice source.

C:

Give both finance teams Billing Account Viewer on one account and expect IAM visibility to split legal payment ownership. Billing Account Viewer changes reporting visibility, not the payment responsibility of the projects already linked to that billing account.

Question 16

An invoice analyst needs itemized Google Cloud charges across every project paid by the same billing account, grouped by project and SKU. Which source should be queried?

  1. The Compute Engine instance inventory from only the project where the analyst currently has Viewer access.
  2. Cloud Audit Logs from one production project, filtered to IAM policy changes.
  3. The Cloud Billing detailed usage cost export to BigQuery for the paying billing account, grouped by project and SKU.
  4. The Cloud Billing budget alert-email history, assuming it contains every billable line item.

Explanation

Correct Answer

C:

The Cloud Billing detailed usage cost export to BigQuery for the paying billing account, grouped by project and SKU. Cloud Billing usage exports include charges for projects paid by the selected billing account. Querying the exported BigQuery table enables grouping by project and supported SKU/cost columns.

Incorrect Answers

A:

The Compute Engine instance inventory from only the project where the analyst currently has Viewer access. Instance inventory lists compute resources rather than account-wide usage and billed charges. It omits other project services and does not provide the billing SKU ledger.

B:

Cloud Audit Logs from one production project, filtered to IAM policy changes. Audit logs record administrative and data events, not a complete account-wide cost export. IAM changes are unrelated to the requested invoice breakdown.

D:

The Cloud Billing budget alert-email history, assuming it contains every billable line item. Budget emails report thresholds and spending summaries. They do not replace the line-item billing data needed for a SKU-level reconciliation.

Question 17

A newly created project is accidentally billed to a development cost center while its production workload uses a different payment account. Which controlled action changes cost attribution?

  1. Rename the development cost-center label but keep the development paying account attached.
  2. Transfer the VM instances between zones and assume charges switch payer accounts.
  3. Relink the project to the approved production Cloud Billing account using authorized billing management permissions.
  4. Grant production employees Billing Account Viewer on the development account.

Explanation

Correct Answer

C:

The linked billing account determines who pays future project usage. Change the association through the authorized billing workflow, then reconcile charges before and after the transfer date with finance.

Incorrect Answers

A:

Labels may help reporting but do not change which billing account pays for the project.

B:

Zone placement is unrelated to a project’s linked paying account and cannot change invoice ownership.

D:

A viewing role changes access to reports, not the project’s billing association.

Question 18

A finance analyst expects a linked project to be able to receive invoice-level account-wide billing data just because its service is running. What should be done instead?

  1. Run the application under a service account with Compute Instance Admin permissions.
  2. Grant the approved Cloud Billing reporting role or provide governed access to a centrally managed billing export.
  3. Enable a resource label called invoice-reader on the running project.
  4. Create a project-level VPC peering connection to the billing account.

Explanation

Correct Answer

B:

Cloud Billing account permissions control account-level financial access separately from project resource IAM. Give the analyst a suitable least-privilege billing role or scoped access to authorized export data instead of relying on the workload’s deployment identity.

Incorrect Answers

A:

Compute administration authorizes VM operations but does not convey account-wide cost or invoice visibility.

C:

Labels help allocate costs but cannot authorize access to billing reports.

D:

A billing account is not a VPC peer and networking does not govern financial authorization.

Question 19

A services team wants to add a different cost center code to individual resources without changing their billing account. Which mechanism is appropriate?

  1. Move every resource to a separate billing account matching its department.
  2. Use a Cloud Monitoring metric label as the only source for monthly invoice allocation.
  3. Change each project’s display name to the new cost-center code.
  4. Apply supported resource or project labels and analyze the corresponding labeled usage in billing exports.

Explanation

Correct Answer

D:

Supported billing labels can attribute covered costs to teams while leaving the Cloud Billing account unchanged. Standardize label keys and validate the actual exported usage fields, since not all services expose identical labels.

Incorrect Answers

A:

The requirement explicitly keeps one paying account; separate billing associations would change payment responsibility.

B:

Monitoring labels classify telemetry, not necessarily the billable resource label fields in Cloud Billing data.

C:

Project display names do not reliably identify cost-center allocations for individual resources.

Question 20

A deployment uses the standard project-level Service Usage workflow. The Pub/Sub API is enabled in sandbox, but the production project has neither its own enablement nor an inherited hierarchical service activation policy. What is needed before using Pub/Sub in production?

  1. Assume the API is enabled in production because sandbox and production share a billing account.
  2. Enable the required API for the production project using an authorized Service Usage operation, or establish an approved inherited policy.
  3. Grant production project Editor to the deployer because IAM automatically enables every Google service.
  4. Configure a new production VPC subnet because API enablement is controlled by subnet routing.

Explanation

Correct Answer

B:

Enable the required API for the production project using an authorized Service Usage operation, or establish an approved inherited policy. Normal Service Usage operations enable services for the selected project. Google also documents a Preview hierarchical activation model; this stem explicitly states that production has no inherited enablement, so it must be enabled through an authorized supported path.

Incorrect Answers

A:

Assume the API is enabled in production because sandbox and production share a billing account. A common billing account does not convey a service enablement state to unrelated projects. The production effective service policy must permit the API.

C:

Grant production project Editor to the deployer because IAM automatically enables every Google service. A role grant controls authorization; it does not by itself activate Pub/Sub. Enabling services requires the appropriate Service Usage permissions and policy state.

D:

Configure a new production VPC subnet because API enablement is controlled by subnet routing. VPC configuration affects packet routing, not whether the Pub/Sub API is enabled for the consuming project. Creating a subnet cannot resolve service-disabled responses.

Associate Cloud Engineer Practice Tests