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 72

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.

Question 711

A legacy application needs one remaining user-managed service-account key during migration, but administrators never audit key age. What maintenance control should they use?

  1. Inspect the service account's managed key metadata and available Cloud Audit Logs for service-account key creation and deletion events.
  2. Inventory user-managed keys, establish rotation deadlines and migrate to keyless authentication where supported.
  3. Allow tokens from any issuer without verifying audience, signature or mapped principal.
  4. Grant a new billing role instead of adjusting the actual token or impersonation permission.

Explanation

Correct Answer

B:

Long-lived keys are persistent credentials and need explicit lifecycle management if they cannot yet be eliminated.

Incorrect Answers

A:

The suggestion does not establish the required issuer, principal or permission boundary. The specific requirement concerns the workload's intended identity and permissions. The appropriate action here is: Inventory user-managed keys, establish rotation deadlines and migrate to keyless authentication where supported.

C:

The suggestion does not establish the required issuer, principal or permission boundary. The necessary distinction is the workload's intended identity and permissions. The appropriate action here is: Inventory user-managed keys, establish rotation deadlines and migrate to keyless authentication where supported.

D:

The suggestion does not establish the required issuer, principal or permission boundary. The case instead depends on the workload's intended identity and permissions. The appropriate action here is: Inventory user-managed keys, establish rotation deadlines and migrate to keyless authentication where supported.

Question 712

A service-account key is rotated, but an old staging container continues using its cached key and fails authentication. What should be repaired?

  1. Remove production Token Creator delegation from the staging pipeline and use a separate staging deployment identity.
  2. Issue a long-lived service-account JSON key instead of repairing short-lived workload credentials.
  3. Update the staging deployment's credential reference to the approved new identity or key and redeploy it securely.
  4. Allow tokens from any issuer without verifying audience, signature or mapped principal.

Explanation

Correct Answer

C:

Revoking an old key invalidates consumers that still embed it; planned rotation requires controlled workload updates.

Incorrect Answers

A:

Deploying a separate workload does not automatically configure the existing feature. 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. The appropriate action here is: Update the staging deployment's credential reference to the approved new identity or key and redeploy it securely.

D:

The suggestion does not establish the required issuer, principal or permission boundary. It leaves the workload's intended identity and permissions unaddressed. The appropriate action here is: Update the staging deployment's credential reference to the approved new identity or key and redeploy it securely.

Question 713

An auditor needs the creation time of a user-managed service account JSON key. The team checks Cloud Run revision history but finds nothing relevant. Where should it look?

  1. At Cloud Billing budget threshold history; every JSON key creation is a line item in billing spend alerts.
  2. Only at the VM serial console; key management operations are always emitted as kernel boot messages.
  3. At the Cloud Storage object list, because service-account keys are automatically saved as bucket objects with their creation timestamps.
  4. Inspect the service account's managed key metadata and available Cloud Audit Logs for service-account key creation and deletion events.

Explanation

Correct Answer

D:

Inspect the service account's managed key metadata and available Cloud Audit Logs for service-account key creation and deletion events. IAM provides metadata for user-managed keys; audit entries can record the principal and time of related management actions when logging is available.

Incorrect Answers

A:

At Cloud Billing budget threshold history; every JSON key creation is a line item in billing spend alerts. Budget notifications do not list IAM key lifecycle events; spending records cannot establish the key creation time.

B:

Only at the VM serial console; key management operations are always emitted as kernel boot messages. Guest serial output describes machine activity. IAM key creation can occur without any VM operation and is not a kernel log event.

C:

At the Cloud Storage object list, because service-account keys are automatically saved as bucket objects with their creation timestamps. Service-account key resources are managed in IAM, not automatically copied into user Cloud Storage buckets.

Question 714

A legacy Compute Engine default service account still has the project Editor role granted years ago. New VM workloads only need limited reads from one Cloud Storage bucket. Which remediation follows least privilege?

  1. Leave Editor because the default service account role is enforced by Google and cannot be narrowed.
  2. Grant the default identity organization Owner; organization scope is safer because it makes the role consistent across projects.
  3. Disable service-account audit logging; monitoring the role is the cause of its excessive privileges.
  4. Replace broad Editor grants with reviewed minimum roles, ideally using a dedicated application service account for these VMs.

Explanation

Correct Answer

D:

Replace broad Editor grants with reviewed minimum roles, ideally using a dedicated application service account for these VMs. Distinct, minimal workload identities avoid unnecessary administration rights and let operators grant only the bucket access required by the VM application.

Incorrect Answers

A:

Leave Editor because the default service account role is enforced by Google and cannot be narrowed. Default service accounts do not inherently require Editor. Legacy automatic grants can be reviewed and removed where not needed.

B:

Grant the default identity organization Owner; organization scope is safer because it makes the role consistent across projects. Organization Owner is broader than project Editor and increases the impact of compromised VM credentials.

C:

Disable service-account audit logging; monitoring the role is the cause of its excessive privileges. Audit logs provide useful security evidence and do not expand a service account's IAM permissions.

Question 715

A managed instance group is supposed to attach service account billing-reader to each new VM, but the instance template still references the Compute Engine default service account. Which input should be changed?

  1. Rename the default service account to billing-reader; future VM credentials follow service-account display names.
  2. Create and roll out a corrected instance template specifying billing-reader as its attached service account, then inspect new instances.
  3. Grant the custom service account Cloud Storage permissions; the instance template automatically selects whichever account has a role.
  4. Change the MIG autoscaler minimum node count; autoscaling selects a new attached service account at the next scaling event.

Explanation

Correct Answer

B:

Create and roll out a corrected instance template specifying billing-reader as its attached service account, then inspect new instances. Instance templates govern the identity of new and recreated managed VMs. The corrected template must be applied to the instance group for future instances.

Incorrect Answers

A:

Rename the default service account to billing-reader; future VM credentials follow service-account display names. Renaming does not change which service-account identity a VM template references; the numeric and email principal mapping remains distinct.

C:

Grant the custom service account Cloud Storage permissions; the instance template automatically selects whichever account has a role. IAM roles describe permissions of a principal but do not automatically attach that principal to VM instances created with another configured identity.

D:

Change the MIG autoscaler minimum node count; autoscaling selects a new attached service account at the next scaling event. Autoscaler settings alter capacity, not template service-account selection. More default-account VMs can be created without a template update.

Question 716

A cloud operator changes roles on a service account itself and expects the account to gain access to BigQuery datasets. What two IAM relationships must be distinguished?

  1. Grant the service account resource access on the dataset separately from permissions controlling who may administer or impersonate that service account.
  2. Grant roles/iam.serviceAccountUser on that specific runtime service account to the authorized deployment operator.
  3. Grant a new billing role instead of adjusting the actual token or impersonation permission.
  4. Issue a long-lived service-account JSON key instead of repairing short-lived workload credentials.

Explanation

Correct Answer

A:

IAM policy on the service-account resource governs its use; IAM policy on the target dataset governs the account's data access.

Incorrect Answers

B:

Deploying a separate workload does not automatically configure the existing feature. 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. The appropriate action here is: Grant the service account resource access on the dataset separately from permissions controlling who may administer or impersonate that service account.

D:

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: Grant the service account resource access on the dataset separately from permissions controlling who may administer or impersonate that service account.

Question 717

An organization needs to restrict which identities can create service-account keys, but current project admins can generate keys freely. What governance should be evaluated?

  1. Apply the relevant organization policy that restricts service-account key creation and enforce approved exceptions.
  2. Inspect the service account's managed key metadata and available Cloud Audit Logs for service-account key creation and deletion events.
  3. Grant Organization Owner to the caller rather than validating the intended identity binding.
  4. Grant a new billing role instead of adjusting the actual token or impersonation permission.

Explanation

Correct Answer

A:

Organization policy can limit long-lived key creation as a preventive control independent of each service account's resource roles.

Incorrect Answers

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. The appropriate action here is: Apply the relevant organization policy that restricts service-account key creation and enforce approved exceptions.

C:

Organization Owner is excessive privilege and cannot repair an unrelated configuration fault. It leaves the workload's intended identity and permissions unaddressed. The appropriate action here is: Apply the relevant organization policy that restricts service-account key creation and enforce approved exceptions.

D:

The suggestion does not establish the required issuer, principal or permission boundary. The specific requirement concerns the workload's intended identity and permissions. The appropriate action here is: Apply the relevant organization policy that restricts service-account key creation and enforce approved exceptions.

Question 718

A team tries to deploy code from one project using a service account stored in another project and receives a policy error. What cross-project boundary should be checked?

  1. Check the effective organization policy and redesign the supported identity binding within approved trust boundaries.
  2. Grant a new billing role instead of adjusting the actual token or impersonation permission.
  3. Verify the applicable cross-project service-account usage organization policy and required role grants on the identity.
  4. Issue a long-lived service-account JSON key instead of repairing short-lived workload credentials.

Explanation

Correct Answer

C:

Service accounts are project-owned resources; cross-project attachment can be governed by organization policy and explicit usage permissions.

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. The appropriate action here is: Verify the applicable cross-project service-account usage organization policy and required role grants on the identity.

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: Verify the applicable cross-project service-account usage organization policy and required role grants on the identity.

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 applicable cross-project service-account usage organization policy and required role grants on the identity.

Question 719

An app's service account is renamed in documentation, but its immutable unique identifier and email used by running workloads remain unchanged. What should operators use for audit correlation?

  1. Use the supported undelete process within its recovery window when possible and verify the original principal identity.
  2. Rename the service account but leave the old principal and role bindings unchanged.
  3. Reuse the default Compute Engine service account for every unrelated workload.
  4. Track the actual service-account principal identity, unique ID and workload bindings rather than informal display labels.

Explanation

Correct Answer

D:

Human-readable descriptions don't change the principal that Google Cloud IAM evaluates for access.

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: Track the actual service-account principal identity, unique ID and workload bindings rather than informal display labels.

B:

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: Track the actual service-account principal identity, unique ID and workload bindings rather than informal display labels.

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. The appropriate action here is: Track the actual service-account principal identity, unique ID and workload bindings rather than informal display labels.

Question 720

A service account that was deleted months ago appears in an old IAM policy as a deleted principal. What should be cleaned up?

  1. Rebind resource IAM to the current authorized workload identity pool and Kubernetes principal identifiers.
  2. Grant a new billing role instead of adjusting the actual token or impersonation permission.
  3. Allow tokens from any issuer without verifying audience, signature or mapped principal.
  4. Remove obsolete deleted-principal bindings and replace them only with intentionally approved active identities.

Explanation

Correct Answer

D:

IAM policies can retain historical references; leaving stale bindings is misleading and doesn't restore authorization to a new identity.

Incorrect Answers

A:

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: Remove obsolete deleted-principal bindings and replace them only with intentionally approved active identities.

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: Remove obsolete deleted-principal bindings and replace them only with intentionally approved active identities.

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: Remove obsolete deleted-principal bindings and replace them only with intentionally approved active identities.

Associate Cloud Engineer Practice Tests