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 18

Question 170

A VM needs to survive occasional host maintenance events with minimal interruption but is configured to terminate on host maintenance. What policy should be reviewed?

  1. Leave the VM set to TERMINATE; the platform will migrate it automatically anyway.
  2. Increase the network bandwidth to prevent infrastructure maintenance.
  3. Review the instance’s on-host-maintenance and automatic-restart settings and choose supported behavior for its machine type.
  4. Move the VM’s billing account whenever Google announces maintenance.

Explanation

Correct Answer

C:

Where the machine configuration supports live migration, set on-host-maintenance behavior accordingly and verify the separate automatic-restart requirement. Some VM types cannot live-migrate, so recovery planning must reflect actual support.

Incorrect Answers

A:

A terminate-on-maintenance setting does not by itself request the lower-interruption migration behavior.

B:

Network throughput cannot prevent planned infrastructure maintenance or alter the host scheduling policy.

D:

Billing account association has no effect on how a VM responds to host maintenance.

Question 171

A batch worker can tolerate termination and restart, and the team wants discounted compute. Which instance option fits the interruption tolerance?

  1. Use Spot VMs with durable checkpoints, retry-aware processing and handling for preemption notices.
  2. Use sole-tenant nodes to guarantee the cheapest interrupted capacity.
  3. Use a permanent VM with no retry policy; compute billing will automatically apply Spot rates.
  4. Put uncheckpointed batch state only on the instance’s ephemeral local storage.

Explanation

Correct Answer

A:

Spot VMs are suitable when jobs can be interrupted and resumed at lower-cost capacity. Preserve checkpoints outside the VM and make retries idempotent so lost capacity does not discard completed work.

Incorrect Answers

B:

Sole-tenancy is an isolation and placement choice, not the discounted, deliberately interruptible instance model requested.

C:

A standard on-demand VM does not become Spot by adding a restart policy.

D:

Local-only uncheckpointed state could vanish on termination and defeat the job’s interruption tolerance.

Question 172

A single stateful payment ledger VM must remain available without arbitrary capacity reclaim. It was launched as a Spot VM and is periodically preempted. Which compute choice better fits the requirement?

  1. Keep the Spot VM and disable its application logs; logging is the condition that triggers Spot preemption.
  2. Increase the Spot VM boot disk size because disk capacity guarantees protection against Spot reclamation.
  3. Grant the Spot VM service account Compute Admin to prevent Google from reclaiming excess capacity.
  4. Run the critical ledger on an appropriate standard, non-Spot VM design with backup and high-availability provisions.

Explanation

Correct Answer

D:

Run the critical ledger on an appropriate standard, non-Spot VM design with backup and high-availability provisions. Standard VM provisioning avoids Spot reclaim risk. Independent data resilience is still required to address normal infrastructure failures.

Incorrect Answers

A:

Keep the Spot VM and disable its application logs; logging is the condition that triggers Spot preemption. Google can reclaim Spot instances to recover capacity, independent of the application's logging configuration.

B:

Increase the Spot VM boot disk size because disk capacity guarantees protection against Spot reclamation. Disk size does not change a VM's provisioning model. A larger Spot boot disk does not prevent arbitrary preemption.

C:

Grant the Spot VM service account Compute Admin to prevent Google from reclaiming excess capacity. IAM roles govern requests and resource access, not the platform's preemption scheduling for Spot capacity.

Question 173

An app needs 6 vCPUs and a nonstandard memory ratio absent from the standard machine-size menu. What should be evaluated?

  1. Choose the next largest fixed shape even if it wastes memory, because custom shapes are never supported.
  2. Request arbitrary fractional vCPU and memory values without checking the machine-family rules.
  3. Evaluate an eligible custom machine type matching the required vCPU count and allowed memory-per-vCPU range.
  4. Increase the boot disk size, which also changes the memory-to-vCPU ratio.

Explanation

Correct Answer

C:

Select a supported custom machine type, verify that six vCPUs and the requested memory satisfy the selected series’ constraints, and compare performance and price before rollout.

Incorrect Answers

A:

A larger preset may work, but it unnecessarily ignores the custom-shape capability in eligible machine families.

B:

Custom configurations still have minimums, increments, ratios and supported machine-series restrictions.

D:

Boot disk capacity is storage; it does not increase RAM or alter machine CPU ratios.

Question 174

An instance's memory pressure rises under a steady load but CPU remains low, and administrators plan to add CPU only. What sizing check matters?

  1. Double vCPUs, since low CPU utilization proves the VM needs more processor capacity.
  2. Resize the VM for its measured working-set memory need, possibly using a supported custom shape.
  3. Add a second static external IP address to eliminate guest memory pressure.
  4. Disable monitoring so memory utilization no longer appears in the dashboard.

Explanation

Correct Answer

B:

Review guest memory, swapping and application working set; choose a compatible machine with enough RAM, test the change and retain headroom. CPU and memory need not scale in the same proportion.

Incorrect Answers

A:

Increasing only vCPUs leaves the measured memory bottleneck unresolved, unless the selected shape also provides sufficient RAM.

C:

An additional external address changes connectivity, not the capacity of the guest operating system’s memory.

D:

Removing telemetry hides the condition without giving the application more memory.

Question 175

A VM's boot disk is too small for updated system packages, and the team wants to retain the existing guest OS. What storage operation is appropriate?

  1. Detach and delete the boot disk, then boot the same operating system without storage.
  2. Increase the VM’s CPU quota so the guest file system expands automatically.
  3. Attach another disk and assume the boot partition instantly expands onto it.
  4. Resize the supported boot disk and extend its guest partition/filesystem after checking backups.

Explanation

Correct Answer

D:

Increase the virtual disk allocation, then expand the partition and filesystem with the guest-OS procedure. Verify backups and the filesystem’s supported resize steps so added cloud capacity becomes usable inside the VM.

Incorrect Answers

A:

Deleting the boot device destroys the guest OS installation rather than preserving it.

B:

CPU quota governs compute allocation, not guest disk partition growth.

C:

A second disk adds a separate volume; it does not automatically extend the existing root filesystem.

Question 176

A stateful service runs on a Compute Engine VM in us-central1-a. Its data must remain stored after a single-zone failure in the same region, and the recovery runbook can reattach a replicated disk in zone b. Which disk design supports this?

  1. Use a supported Regional Persistent Disk with two-zone synchronous replication and an application-specific VM/disk failover plan.
  2. Use a zonal Persistent Disk in us-central1-a, since the disk automatically survives every zone-wide outage without a replica.
  3. Create two unrelated zonal disks with the same name in zones a and b; their content is synchronized by their matching names.
  4. Store a local SSD on the VM and assume its data automatically reattaches to a new VM after the original zone fails.

Explanation

Correct Answer

A:

Use a supported Regional Persistent Disk with two-zone synchronous replication and an application-specific VM/disk failover plan. Regional Persistent Disk replicates blocks synchronously between two zones in one region. The stated recovery runbook is necessary because storage replication does not itself move or restart the application VM.

Incorrect Answers

B:

Use a zonal Persistent Disk in us-central1-a, since the disk automatically survives every zone-wide outage without a replica. Zonal disks are tied to their zone. A complete zone outage can prevent access to that disk until the zone recovers.

C:

Create two unrelated zonal disks with the same name in zones a and b; their content is synchronized by their matching names. Matching disk names do not create replication. Independent disks would diverge unless the application or storage system explicitly synchronized them.

D:

Store a local SSD on the VM and assume its data automatically reattaches to a new VM after the original zone fails. Local SSD is ephemeral to its VM and does not provide a failover-ready replicated block volume when the attached VM fails.

Question 177

A database VM was provisioned with very high IOPS demands but a standard Persistent Disk throughput ceiling. What class should be assessed?

  1. Use a smaller standard Persistent Disk and expect its IOPS ceiling to increase.
  2. Increase only the network interface count, because disk performance is never constrained by storage class.
  3. Move the database to a Cloud Storage bucket mounted as its primary block device.
  4. Evaluate a supported Hyperdisk type with provisioned performance and confirm VM-level limits.

Explanation

Correct Answer

D:

Hyperdisk types can provide performance controls suited to demanding block workloads. Choose a supported class, configure IOPS/throughput where available and verify that the selected VM and volume combination can deliver those targets.

Incorrect Answers

A:

A smaller standard disk will not reliably meet a high-IOPS requirement; capacity and class both affect performance.

B:

NIC count does not substitute for storage IOPS or throughput entitlement.

C:

Object storage is not a drop-in block-device replacement for a database volume.

Question 178

A team expects attaching a regional disk to a VM in another region to provide easy recovery. What condition invalidates the plan?

  1. Attach the regional disk directly to any VM worldwide because its name is globally unique.
  2. Enable Cloud NAT in the recovery region to transport disk attachment requests.
  3. Attach to an eligible VM in a disk-replica zone, or restore a backup/copy in the other region.
  4. Change the regional disk’s labels to the destination region without creating a copy.

Explanation

Correct Answer

C:

A regional disk has replicas in selected zones within one region and can attach only in eligible replica zones. Cross-region recovery requires a separately supported snapshot, backup or replication design with storage in the destination region.

Incorrect Answers

A:

Regional replication covers zones within a region; it does not make that block disk directly attachable across arbitrary regions.

B:

NAT affects network address translation and cannot change disk replication or attach scope.

D:

Changing metadata does not move physical disk replicas to another region.

Question 179

A batch engineer must keep an immutable point-in-time copy of a VM data disk for later recovery. The copy does not need to be mounted or to accept writes while it is retained. What artifact should the engineer create?

  1. Add a second writable zonal disk and keep it attached to the running VM as the archival copy.
  2. Create a second VM that mounts the original disk read-write and assume the extra VM itself is a durable restore point.
  3. Enlarge the original disk without making a separate copy, because added capacity provides a historical data state.
  4. Create a Persistent Disk snapshot and retain it under the required backup policy.

Explanation

Correct Answer

D:

Create a Persistent Disk snapshot and retain it under the required backup policy. A disk snapshot captures the disk state at a point in time and can later serve as the source for a restored disk.

Incorrect Answers

A:

Add a second writable zonal disk and keep it attached to the running VM as the archival copy. An attached writable disk is a live mutable storage device, not an immutable point-in-time recovery artifact.

B:

Create a second VM that mounts the original disk read-write and assume the extra VM itself is a durable restore point. Another VM does not create an independent recoverable historical state; it can also introduce conflicting writes and attachment restrictions.

C:

Enlarge the original disk without making a separate copy, because added capacity provides a historical data state. Resizing changes the live volume size but preserves no earlier contents to restore after accidental changes.

Question 180

A team has a successful Persistent Disk snapshot named data-before-migration and wants to use its contents as a read/write data volume attached to a replacement VM. What step is required?

  1. Mount the snapshot resource directly using the normal Linux block-device mount command; no disk must exist.
  2. Rename the snapshot to the replacement VM name; Google Cloud automatically converts its snapshot into that VM's writable disk.
  3. Create a compatible new Persistent Disk with that snapshot as the source, attach it to the replacement VM, and mount the restored filesystem.
  4. Change the snapshot retention policy to zero; making it expire converts the snapshot into an active writable Persistent Disk.

Explanation

Correct Answer

C:

Create a compatible new Persistent Disk with that snapshot as the source, attach it to the replacement VM, and mount the restored filesystem. The documented restore flow creates a new disk from the snapshot; only that disk can be attached and mounted as writable storage.

Incorrect Answers

A:

Mount the snapshot resource directly using the normal Linux block-device mount command; no disk must exist. A snapshot is a backup resource, not a block device available for direct mounting by a running guest OS.

B:

Rename the snapshot to the replacement VM name; Google Cloud automatically converts its snapshot into that VM's writable disk. Changing a name does not restore disk data or attach a storage volume to an instance.

D:

Change the snapshot retention policy to zero; making it expire converts the snapshot into an active writable Persistent Disk. Retention controls backup lifecycle, not disk restoration or attachment. Deleting the only recovery point would make the situation worse.

Associate Cloud Engineer Practice Tests