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 20

Question 190

An operator groups web VMs in an unmanaged instance group but expects it to recreate failed VMs automatically. What change supplies managed autohealing behavior?

  1. Add a Cloud Billing alert for network spend; the alert automatically replaces failed unmanaged VMs.
  2. Set the group's display name to managed; an unmanaged group acquires autohealing from a naming convention.
  3. Migrate the fleet to an appropriately configured managed instance group with an instance template and autohealing health check.
  4. Enable serial console access and manually reboot each failed VM without changing the unmanaged group.

Explanation

Correct Answer

C:

Migrate the fleet to an appropriately configured managed instance group with an instance template and autohealing health check. Managed instance groups can monitor application health and recreate members. Unmanaged instance groups do not provide that automated repair behavior.

Incorrect Answers

A:

Add a Cloud Billing alert for network spend; the alert automatically replaces failed unmanaged VMs. Billing alerts provide financial notifications, not an instance-group repair controller.

B:

Set the group's display name to managed; an unmanaged group acquires autohealing from a naming convention. Management type is a group architecture and resource control feature, not a string in the group name.

D:

Enable serial console access and manually reboot each failed VM without changing the unmanaged group. Manual reboot may recover one VM but does not fulfill the requirement for automatic replacement when members become unhealthy.

Question 191

An autoscaled MIG cannot add instances because a service account in its template lacks permission to read its startup artifacts. What should be changed?

  1. Grant the template’s VM service account access to the required startup artifacts, then test a newly created instance.
  2. Increase the autoscaler maximum replicas; permission errors disappear once it can request more VMs.
  3. Change only the load balancer health check interval and leave the missing artifact permission.
  4. Grant everyone public read access to all project startup buckets.

Explanation

Correct Answer

A:

New instances use the template’s configured runtime identity and need authorized access to scripts and files. Add the minimum read permissions for the specific artifacts, confirm network paths and validate one replacement VM before scaling up.

Incorrect Answers

B:

A larger desired group size does not repair an IAM denial during bootstrap.

C:

Health checks may reveal failures but do not grant the VM access to its startup dependencies.

D:

Broad public sharing violates the least-privilege requirement and unnecessarily exposes deployment assets.

Question 192

An organization wants non-root SSH access to Linux Compute Engine VMs controlled by IAM rather than project metadata SSH keys. Which configuration supports that model?

  1. Disable OS Login and keep all SSH public keys in shared project metadata for every engineer.
  2. Grant OS Admin Login to every developer even though only ordinary shell access is required.
  3. Enable OS Login on the VMs and grant eligible operators the minimum appropriate OS Login IAM permissions.
  4. Grant a storage-object Viewer role and assume it also permits SSH login to any Compute Engine instance.

Explanation

Correct Answer

C:

Enable OS Login on the VMs and grant eligible operators the minimum appropriate OS Login IAM permissions. OS Login integrates supported Linux SSH sign-in with IAM and uses Google-managed identity information. A narrowly scoped OS Login role is suitable for operators who do not need administrator privileges.

Incorrect Answers

A:

Disable OS Login and keep all SSH public keys in shared project metadata for every engineer. Disabling OS Login restores the metadata-key pattern the company wants to replace; the SSH authorization remains distributed through project settings.

B:

Grant OS Admin Login to every developer even though only ordinary shell access is required. OS Admin Login is intended for privileged operating-system login, not ordinary non-root access. It exceeds the stated requirement.

D:

Grant a storage-object Viewer role and assume it also permits SSH login to any Compute Engine instance. Cloud Storage read permissions authorize object access, not login to a VM operating system. They cannot replace OS Login IAM roles.

Question 193

An approved engineer can SSH to an OS Login-enabled Compute Engine VM but receives a permissions error when attempting sudo. Which role distinction should administrators check?

  1. Grant the approved maintainer OS Admin Login (roles/compute.osAdminLogin) where appropriate; OS Login alone does not include sudo.
  2. Add a Cloud Billing Administrator role, because all billing administrators receive root login on their VMs.
  3. Turn off Cloud Logging for the VM; audit logs are the cause of Linux sudo authorization failure.
  4. Rename the SSH public key to admin; key file names override OS Login role permissions automatically.

Explanation

Correct Answer

A:

Grant the approved maintainer OS Admin Login (roles/compute.osAdminLogin) where appropriate; OS Login alone does not include sudo. Google distinguishes OS Login for ordinary SSH access from OS Admin Login for administrative sudo access. The grant should be scoped to the authorized maintainer.

Incorrect Answers

B:

Add a Cloud Billing Administrator role, because all billing administrators receive root login on their VMs. Billing account administration does not supply VM operating system privilege elevation under OS Login.

C:

Turn off Cloud Logging for the VM; audit logs are the cause of Linux sudo authorization failure. Disabling log collection does not grant the Linux privilege managed by OS Login and would degrade investigation evidence.

D:

Rename the SSH public key to admin; key file names override OS Login role permissions automatically. A key file name does not confer sudo permission. The OS Login IAM role and guest account mapping are relevant to elevation.

Question 194

A Linux VM has OS Login enabled. Its old project-level metadata SSH keys remain, and an engineer assumes those metadata keys still determine who may sign in. Which rule applies?

  1. Project metadata SSH keys continue to override IAM OS Login for every account on a VM after enabling OS Login.
  2. OS Login manages the supported SSH sign-in flow using IAM-based identity and authorization instead of the metadata SSH-key mechanism.
  3. Enabling Cloud Billing API access automatically converts metadata SSH keys into valid OS Login roles.
  4. A VM firewall allow rule grants Linux account authorization without requiring a user identity or OS Login entitlement.

Explanation

Correct Answer

B:

OS Login manages the supported SSH sign-in flow using IAM-based identity and authorization instead of the metadata SSH-key mechanism. Google's OS Login flow uses IAM role eligibility and the user identity for SSH access. Metadata-based authorized key distribution is not the primary access control after OS Login is enabled.

Incorrect Answers

A:

Project metadata SSH keys continue to override IAM OS Login for every account on a VM after enabling OS Login. When OS Login is enabled, SSH-key authorization is no longer based on the project or instance metadata key list for the supported path.

C:

Enabling Cloud Billing API access automatically converts metadata SSH keys into valid OS Login roles. Billing configuration has no role in converting SSH metadata entries into login privileges for operating-system accounts.

D:

A VM firewall allow rule grants Linux account authorization without requiring a user identity or OS Login entitlement. Network access to TCP port 22 is separate from OS authentication. An allowed packet does not automatically authorize an SSH user.

Question 195

A private VM has no external IP address, but engineers need a controlled interactive SSH path from outside its VPC. Which access technique should be considered?

  1. Assign a public IP temporarily and permit SSH from the entire internet.
  2. Turn on Cloud NAT and expect it to accept inbound SSH sessions to a private VM.
  3. Use IAP TCP forwarding with required IAM and source firewall permissions, or another approved private route.
  4. Add the SSH user to Billing Account Viewer to enable the VM’s private tunnel.

Explanation

Correct Answer

C:

IAP TCP forwarding can provide identity-controlled SSH access to eligible private instances. Verify the principal’s IAP permissions, VM login rights and a correctly scoped firewall rule, and keep direct public SSH closed.

Incorrect Answers

A:

A public endpoint creates exposure contrary to the no-external-IP constraint.

B:

Cloud NAT provides outbound internet connectivity; it is not an SSH ingress gateway for unsolicited sessions.

D:

Billing visibility does not authorize tunneling or guest operating-system login.

Question 196

Security wants a centralized view of missing OS patches across supported Compute Engine VMs without opening an SSH session to each machine. Which Google Cloud capability provides patch compliance data?

  1. Use Cloud Billing budget alerts, which calculate missing operating-system CVEs from SKU charges.
  2. Use VM Manager patch compliance reporting with the supported OS Config agent and inventory prerequisites.
  3. Enable VPC Flow Logs; packet counts list all missing guest OS package updates.
  4. Create a new managed instance group name; instance-group naming automatically audits each Linux package version.

Explanation

Correct Answer

B:

Use VM Manager patch compliance reporting with the supported OS Config agent and inventory prerequisites. VM Manager Patch provides compliance reporting for supported Linux and Windows VMs, with required management/agent prerequisites.

Incorrect Answers

A:

Use Cloud Billing budget alerts, which calculate missing operating-system CVEs from SKU charges. Billing spend records do not describe guest OS packages or whether critical security updates are missing.

C:

Enable VPC Flow Logs; packet counts list all missing guest OS package updates. Flow logs observe network activity, not installed guest packages or patch compliance states.

D:

Create a new managed instance group name; instance-group naming automatically audits each Linux package version. A group name is resource metadata and does not enable guest patch inventory or compliance scans.

Question 197

A patch deployment succeeded on some VMs but failed on machines missing the required management agent. What prerequisite should be corrected?

  1. Ignore agent status and send the patch job repeatedly until all instances reboot.
  2. Install or repair the required guest/VM Manager agents, verify OS support and rerun the patch job.
  3. Grant an external IP to every VM because the management agent is unrelated to patch operations.
  4. Increase the patch job timeout without checking that the missing agent can execute instructions.

Explanation

Correct Answer

B:

OS patch management requires supported guest prerequisites and agent connectivity. Identify affected machines, correct agent installation and service status, then rerun on a test subset before reattempting the wider fleet.

Incorrect Answers

A:

Retries do not fix missing execution components and can produce inconsistent maintenance outcomes.

C:

An external IP may be unnecessary and does not itself install the required agent.

D:

A longer timeout cannot turn a missing agent into a functioning patch executor.

Question 198

A company needs recurring security patching every Sunday at 03:00 for supported VMs with environment=staging, while leaving production untouched. Which managed job setup matches this requirement?

  1. Create a VM Manager patch deployment with a recurring schedule, an instance filter selecting staging VMs, and reviewed reboot settings.
  2. Manually apply updates to the first staging VM and assume its package state is inherited by every other instance.
  3. Add an organization-level Editor grant to the patch operator; Editor automatically installs approved OS patches each week.
  4. Schedule Cloud Billing cost exports on Sundays, because the export service executes Linux and Windows guest updates.

Explanation

Correct Answer

A:

Create a VM Manager patch deployment with a recurring schedule, an instance filter selecting staging VMs, and reviewed reboot settings. VM Manager patch deployments support recurring schedules and filters evaluated when each job runs. Appropriate instance targeting avoids patching production.

Incorrect Answers

B:

Manually apply updates to the first staging VM and assume its package state is inherited by every other instance. A manual action on one VM is not fleet patching and does not propagate its package updates to independent guest operating systems.

C:

Add an organization-level Editor grant to the patch operator; Editor automatically installs approved OS patches each week. An IAM role permits API operations but does not create a recurring patch job or define maintenance windows.

D:

Schedule Cloud Billing cost exports on Sundays, because the export service executes Linux and Windows guest updates. Cloud Billing exports provide usage and charge records, not guest OS package update execution.

Question 199

VM Manager reports installed packages on a legacy Linux VM, but its vulnerability report is unavailable for that exact OS release. What should operators verify before treating the VM as covered by vulnerability scanning?

  1. Check the supported OS/version list and VM Manager vulnerability-source coverage, then use a supported upgrade or separately approved scanner for gaps.
  2. Assume any VM that reports an installed package is automatically supported for CVE assessment in every OS release.
  3. Increase VM vCPU count because CVE report eligibility is determined by available compute cores.
  4. Grant the VM an organization Owner role so VM Manager can invent vendor vulnerability feeds for unsupported distributions.

Explanation

Correct Answer

A:

Check the supported OS/version list and VM Manager vulnerability-source coverage, then use a supported upgrade or separately approved scanner for gaps. VM Manager inventory data and vulnerability reporting have distinct support conditions. The exact OS and advisory feed must be supported before the report can be relied upon.

Incorrect Answers

B:

Assume any VM that reports an installed package is automatically supported for CVE assessment in every OS release. Package inventory proves some guest data is collected; it does not guarantee vendor vulnerability metadata coverage for that OS release.

C:

Increase VM vCPU count because CVE report eligibility is determined by available compute cores. A larger VM does not supply missing vendor advisories or add an unsupported OS version to the supported inventory matrix.

D:

Grant the VM an organization Owner role so VM Manager can invent vendor vulnerability feeds for unsupported distributions. IAM authorization cannot cause a vulnerability source to publish unsupported security data. Escalating privileges would create unnecessary exposure.

Question 200

A small team wants Kubernetes without provisioning or tuning node pools and prefers Google-managed capacity defaults. Which GKE mode fits?

  1. Use GKE Autopilot and specify supported Pod resource requests while Google manages the underlying node operations.
  2. Use GKE Standard without node pools and expect Kubernetes to create bare-metal capacity automatically.
  3. Create a standalone Compute Engine VM for each Pod to avoid Kubernetes infrastructure entirely.
  4. Use a Cloud Storage bucket as a Kubernetes control plane with automatic scheduling.

Explanation

Correct Answer

A:

Autopilot provides managed Kubernetes with automated node provisioning and many node lifecycle responsibilities handled by Google. The team still controls workloads and should specify appropriate Pod requests and policies.

Incorrect Answers

B:

Standard clusters normally require the operator to manage node-pool capacity and configuration, contrary to the stated preference.

C:

Individual VMs do not supply Kubernetes scheduling and service abstractions by themselves.

D:

Object storage stores files and does not provide Kubernetes node scheduling or a cluster control plane.

Associate Cloud Engineer Practice Tests