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 71

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.

Question 701

A scheduled Cloud Run automation uses the personal Google user credential of the employee who wrote it. When that employee account is disabled, the production job loses Google API access. Which long-term principal is appropriate?

  1. Re-enable the departed employee account indefinitely and put the password in Secret Manager as the standard runtime identity.
  2. Use a dedicated application service account attached to the workload, with only the permissions the recurring job requires.
  3. Give every employee organization Owner so the job can switch identities whenever a worker leaves.
  4. Make all resources public so the job never needs any Google Cloud credentials for its API operations.

Explanation

Correct Answer

B:

Use a dedicated application service account attached to the workload, with only the permissions the recurring job requires. An application service account gives the job an independently managed, non-human identity whose privileges can be reviewed and maintained.

Incorrect Answers

A:

Re-enable the departed employee account indefinitely and put the password in Secret Manager as the standard runtime identity. A personal account is coupled to employment and interactive sign-in lifecycle. Preserving it as a shared production credential is fragile and inappropriate.

C:

Give every employee organization Owner so the job can switch identities whenever a worker leaves. Broad organization access for humans does not provide a stable non-human runtime identity and greatly increases accidental privilege exposure.

D:

Make all resources public so the job never needs any Google Cloud credentials for its API operations. Anonymous resource access abandons the intended authorization model and creates unnecessary exposure rather than fixing credential lifecycle.

Question 702

A team reuses one service account for unrelated billing analysis and customer-facing workloads, making access reviews impossible. What identity separation is appropriate?

  1. Record workload owner, intended permissions, identity lifetime and credential strategy in the approved service-account inventory.
  2. Allow tokens from any issuer without verifying audience, signature or mapped principal.
  3. Create separate purpose-bound service accounts for the jobs and grant each only its required resource permissions.
  4. Rename the service account but leave the old principal and role bindings unchanged.

Explanation

Correct Answer

C:

Distinct workload identities make permissions, audit events and credential rotation attributable to the correct application.

Incorrect Answers

A:

The suggestion does not establish the required issuer, principal or permission boundary. It leaves the correct runtime principal and its bindings unaddressed.

B:

The suggestion does not establish the required issuer, principal or permission boundary. The specific requirement concerns the correct runtime principal and its bindings.

D:

Renaming a resource does not alter the actual effective configuration. The necessary distinction is the correct runtime principal and its bindings.

Question 703

A new service account exists but cannot read objects from a storage bucket, while an engineer believes its creation automatically grants data access. What must be configured?

  1. Grant the federated principal or its approved impersonated service account the necessary bucket-level read role.
  2. Reuse the default Compute Engine service account for every unrelated workload.
  3. Allow tokens from any issuer without verifying audience, signature or mapped principal.
  4. Bind the required storage-reading role at the authorized bucket scope to the service account principal.

Explanation

Correct Answer

D:

Creating a service account produces an identity, not automatic authorization to all Google Cloud resources.

Incorrect Answers

A:

The suggestion does not establish the required issuer, principal or permission boundary. The specific requirement concerns the correct runtime principal and its bindings. The appropriate action here is: Bind the required storage-reading role at the authorized bucket scope to the service account principal.

B:

The suggestion does not establish the required issuer, principal or permission boundary. The necessary distinction is the correct runtime principal and its bindings.

C:

The suggestion does not establish the required issuer, principal or permission boundary. The case instead depends on the correct runtime principal and its bindings.

Question 704

A producer runs under its own service account and must only publish messages to Pub/Sub topic invoice-events. It currently holds project Editor and does not need to create topics or manage subscriptions. Which replacement meets least privilege?

  1. Grant Pub/Sub Admin on the project and remove Editor; administrators can also change topic policies and delete subscriptions.
  2. Grant Pub/Sub Viewer on the project, because read-only access includes publishing messages.
  3. Keep Editor and add a separate Pub/Sub Publisher grant; the added role automatically cancels the larger one.
  4. Remove Editor and grant the service account roles/pubsub.publisher on topic invoice-events, assuming no other permissions are needed.

Explanation

Correct Answer

D:

Remove Editor and grant the service account roles/pubsub.publisher on topic invoice-events, assuming no other permissions are needed. The topic-scoped Publisher role supplies publish access without topic administration or project-wide editing permissions.

Incorrect Answers

A:

Grant Pub/Sub Admin on the project and remove Editor; administrators can also change topic policies and delete subscriptions. Pub/Sub Admin would still permit unrelated administration across the project and exceed the requirement to publish to a single topic.

B:

Grant Pub/Sub Viewer on the project, because read-only access includes publishing messages. Pub/Sub Viewer is not the publishing permission needed to send messages to a topic.

C:

Keep Editor and add a separate Pub/Sub Publisher grant; the added role automatically cancels the larger one. IAM allows are additive; adding a narrower Publisher role does not remove permissions from the existing Editor grant.

Question 705

A maintenance script needs to disable one service account but administrators plan to delete it permanently, despite uncertain dependencies. What is the safer step?

  1. Disable the account reversibly, inventory its workload consumers and validate impacts before permanent deletion.
  2. Remove the now-unneeded workload-to-Google-service-account impersonation role binding after verifying the direct federated permissions and dependencies.
  3. Disable service-account audit logging and assume the credential issue is resolved.
  4. Grant Organization Owner to the caller rather than validating the intended identity binding.

Explanation

Correct Answer

A:

Disabling can suspend a nonhuman identity's use while preserving a controlled recovery path and audit context.

Incorrect Answers

B:

The suggestion does not establish the required issuer, principal or permission boundary. The case instead depends on the correct runtime principal and its bindings. The appropriate action here is: Disable the account reversibly, inventory its workload consumers and validate impacts before permanent deletion.

C:

Changing audit collection cannot grant a denied permission or fix service behavior. It leaves the correct runtime principal and its bindings unaddressed.

D:

Organization Owner is excessive privilege and cannot repair an unrelated configuration fault. The specific requirement concerns the correct runtime principal and its bindings.

Question 706

A production service account is disabled, and a GKE application relying on it suddenly cannot access Secret Manager. What first control should be examined?

  1. Verify the intended service account's disabled state and approved re-enablement or replacement before modifying secret IAM.
  2. Remove the broad principalSet grant and bind Secret Accessor on the secret to the exact approved finance/processor federated principal.
  3. Rename the service account but leave the old principal and role bindings unchanged.
  4. Allow tokens from any issuer without verifying audience, signature or mapped principal.

Explanation

Correct Answer

A:

A disabled identity cannot perform authorized token-based operations even when its resource-role bindings still exist.

Incorrect Answers

B:

The suggestion does not establish the required issuer, principal or permission boundary. It leaves the correct runtime principal and its bindings unaddressed. The appropriate action here is: Verify the intended service account's disabled state and approved re-enablement or replacement before modifying secret IAM.

C:

Renaming a resource does not alter the actual effective configuration. The specific requirement concerns the correct runtime principal and its bindings.

D:

The suggestion does not establish the required issuer, principal or permission boundary. The necessary distinction is the correct runtime principal and its bindings. The appropriate action here is: Verify the intended service account's disabled state and approved re-enablement or replacement before modifying secret IAM.

Question 707

A service account was accidentally deleted and restoration is requested, but the team assumes creating another account with the same name restores its identity. What matters?

  1. Use the supported undelete process within its recovery window when possible and verify the original principal identity.
  2. Track the actual service-account principal identity, unique ID and workload bindings rather than informal display labels.
  3. Rename the service account but leave the old principal and role bindings unchanged.
  4. Grant a new billing role instead of adjusting the actual token or impersonation permission.

Explanation

Correct Answer

A:

A new service account with the same email/name may not have the same unique identity or existing access expectations.

Incorrect Answers

B:

The suggestion does not establish the required issuer, principal or permission boundary. The specific requirement concerns the correct runtime principal and its bindings. The appropriate action here is: Use the supported undelete process within its recovery window when possible and verify the original principal identity.

C:

Renaming a resource does not alter the actual effective configuration. The necessary distinction is the correct runtime principal and its bindings. The appropriate action here is: Use the supported undelete process within its recovery window when possible and verify the original principal identity.

D:

The suggestion does not establish the required issuer, principal or permission boundary. The case instead depends on the correct runtime principal and its bindings. The appropriate action here is: Use the supported undelete process within its recovery window when possible and verify the original principal identity.

Question 708

A project reaches its service-account creation quota because each short-lived task creates a new account, even when tasks share a stable duty. What design is preferable?

  1. Configure Google Cloud Workload Identity Federation for GitHub OIDC with trusted repository/environment attribute conditions and scoped resource or service-account access.
  2. Allow tokens from any issuer without verifying audience, signature or mapped principal.
  3. Use purpose-scoped reusable managed workload identities with per-job authorization rather than creating a new identity for every run.
  4. Grant Organization Owner to the caller rather than validating the intended identity binding.

Explanation

Correct Answer

C:

Service-account identity count should reflect durable trust boundaries; excessive throwaway identities complicate quotas and audits.

Incorrect Answers

A:

The suggestion does not establish the required issuer, principal or permission boundary. The necessary distinction is the workload's intended identity and permissions.

B:

The suggestion does not establish the required issuer, principal or permission boundary. The case instead depends on the workload's intended identity and permissions.

D:

Organization Owner is excessive privilege and cannot repair an unrelated configuration fault. It leaves the workload's intended identity and permissions unaddressed.

Question 709

A team generates service-account JSON keys for every container even though the containers run on Google Cloud with managed identity. What should be adopted?

  1. Use supported attached service accounts or workload identity token mechanisms instead of distributing downloaded private keys.
  2. Use the Pod's Kubernetes ServiceAccount with GKE Workload Identity Federation and grant its mapped principal only the required bucket permissions.
  3. Allow tokens from any issuer without verifying audience, signature or mapped principal.
  4. Rename the service account but leave the old principal and role bindings unchanged.

Explanation

Correct Answer

A:

Managed credential issuance reduces long-lived key exposure and centralizes identity lifetime and audit controls.

Incorrect Answers

B:

Changing an unrelated Pod setting leaves the stated cloud feature unresolved. The case instead depends on the correct runtime principal and its bindings. The appropriate action here is: Use supported attached service accounts or workload identity token mechanisms instead of distributing downloaded private keys.

C:

The suggestion does not establish the required issuer, principal or permission boundary. It leaves the correct runtime principal and its bindings unaddressed. The appropriate action here is: Use supported attached service accounts or workload identity token mechanisms instead of distributing downloaded private keys.

D:

Renaming a resource does not alter the actual effective configuration. The specific requirement concerns the correct runtime principal and its bindings. The appropriate action here is: Use supported attached service accounts or workload identity token mechanisms instead of distributing downloaded private keys.

Question 710

A service-account key is found in a public build log and the team merely deletes the log entry. What incident response is required?

  1. Revoke the exposed key and restore the approved metadata-based federated credential flow, removing the secret and its copies.
  2. Reuse the default Compute Engine service account for every unrelated workload.
  3. Revoke or delete the compromised key, rotate affected secrets and review audit use of that identity.
  4. Rename the service account but leave the old principal and role bindings unchanged.

Explanation

Correct Answer

C:

Removing a visible leak does not invalidate copies of a private key already exposed to unauthorized parties.

Incorrect Answers

A:

The suggestion does not establish the required issuer, principal or permission boundary. It leaves the workload's intended identity and permissions unaddressed.

B:

The suggestion does not establish the required issuer, principal or permission boundary. The specific requirement concerns the workload's intended identity and permissions.

D:

Renaming a resource does not alter the actual effective configuration. The necessary distinction is the workload's intended identity and permissions.

Associate Cloud Engineer Practice Tests