mcAfee Secure Website
23

Google Associate Cloud Engineer Bundle

Exam Code: Associate Cloud Engineer

Exam Name Associate Cloud Engineer

Certification Provider: Google

Corresponding Certification: Associate Cloud Engineer

Associate Cloud Engineer Training Materials $44.99

Reliable & Actual Study Materials for Associate Cloud Engineer Exam Success

The Latest Associate Cloud Engineer Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    Associate Cloud Engineer Questions & Answers

    391 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • 25
    Associate Cloud Engineer Video Course

    Associate Cloud Engineer Training Course

    234 Video Lectures

    Based on Real Life Scenarios which you will encounter in exam and learn by working with real equipment.

  • exam =30
    Study Guide

    Associate Cloud Engineer Study Guide

    849 PDF Pages

    Study Guide developed by industry experts who have written exams in the past. They are technology-specific IT certification researchers with at least a decade of experience at Fortune 500 companies.

exam =32

Associate Cloud Engineer Practice Tests

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Google Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    391 Questions

    $124.99
    exam =35
  • exam =37
    Associate Cloud Engineer Video Course

    Training Course

    234 Video Lectures

    $39.99
  • exam =36
    Study Guide

    Study Guide

    849 PDF Pages

    $29.99

Google Associate Cloud Engineer Practice Test 24

Question 230

A running Linux VM needs more capacity on a supported Persistent Disk. The cloud-side disk resize succeeds, but the guest filesystem still shows the old size. What additional step is required?

  1. Stop and start the VM without extending the guest partition or filesystem.
  2. Extend the relevant partition and filesystem in the guest using supported OS tools.
  3. Create a second persistent disk snapshot rather than resizing the guest filesystem.
  4. Change the disk’s Performance or IOPS setting without running guest filesystem growth tools.

Explanation

Correct Answer

B:

Increasing the block device capacity does not always automatically grow the filesystem that applications mount.

Incorrect Answers

A:

A reboot alone does not necessarily grow the filesystem to consume newly provisioned block-device capacity.

C:

A snapshot preserves a point-in-time disk copy and does not expand the running guest partition and filesystem.

D:

Disk performance settings do not update partition tables or filesystem metadata after a capacity increase.

Question 231

An engineer has a validated Persistent Disk snapshot and wants a separate recovery disk for forensic inspection without overwriting the live disk. Which operation is appropriate?

  1. Create a new Persistent Disk from the snapshot and attach it to an inspection VM where supported.
  2. Mount the snapshot directly as a writable NFS file share.
  3. Delete the original disk before creating the recovery volume.
  4. Attach the snapshot resource directly to a VM as if it were a writable disk.

Explanation

Correct Answer

A:

A snapshot can be used as the source for a separately provisioned disk, preserving the original data volume.

Incorrect Answers

B:

A Compute Engine disk snapshot is not itself a live NFS file server.

C:

Deleting production storage is unnecessary and risks irreversible loss.

D:

A snapshot is a recovery artifact, not an attachable block volume; a new Persistent Disk must be created from it first.

Question 232

An organization has approved a newer golden VM image and wants provisioning tools to recognize that an older custom image should no longer be selected for new instances. What image lifecycle setting should be considered?

  1. Delete every VM that was previously built from that image.
  2. Delete the legacy custom image immediately without informing image consumers.
  3. Change the default VPC route.
  4. Deprecate the outdated custom image, with replacement metadata as applicable.

Explanation

Correct Answer

D:

Deprecation communicates lifecycle status to provisioning clients without requiring an immediate destructive deletion of historical image data.

Incorrect Answers

A:

Existing instances need not be deleted merely because the source image is deprecated.

B:

Deletion may break dependencies still referencing the image; deprecation signals an approved replacement while supporting a controlled transition.

C:

Networking routes do not mark an image as deprecated.

Question 233

A troubleshooting team wants a reusable recovery artifact capturing a VM's configuration and multiple attached disk contents together, rather than merely copying one disk snapshot. Which Compute Engine artifact is most relevant?

  1. Create a single data disk snapshot and assume it contains all VM metadata and other disks.
  2. Store the VM hostname in Cloud DNS only.
  3. Create a machine image of the supported VM configuration and disks.
  4. Create a disk-only snapshot of one attached disk and assume it preserves all VM configuration.

Explanation

Correct Answer

C:

Machine images capture an instance-oriented configuration and multiple disk data sources for later restoration workflows.

Incorrect Answers

A:

One snapshot captures a disk's contents, not the full multi-disk instance configuration.

B:

DNS naming is not an instance backup artifact.

D:

One disk snapshot omits instance settings and other disks; a machine image captures a broader supported instance recovery state.

Question 234

One VM in a managed instance group has an unrecoverable local configuration problem, but the other group members remain healthy. The instance template is known good. What targeted operation replaces only the bad member?

  1. Delete the entire managed instance group and rebuild all members.
  2. Recreate the affected MIG instance from the current group template.
  3. Change the DNS TTL of the group's public name.
  4. Patch the broken managed-instance-group VM manually and treat it as permanent.

Explanation

Correct Answer

B:

MIG recreation rebuilds a selected member using the group's intended template without requiring a group-wide replacement.

Incorrect Answers

A:

Whole-group deletion is unnecessarily disruptive for a single-instance defect.

C:

DNS caching does not repair the guest configuration of a VM.

D:

MIG reconciliation can recreate instances from its template and discard manual fixes; recreating one instance from the template restores declared state.

Question 235

A GKE administrator sees an application warning and needs to enumerate Pods in a specific namespace, including each Pod's current phase and readiness summary. Which Kubernetes query is most direct?

  1. Run kubectl get pods -n <namespace> against the correct cluster context.
  2. Run kubectl get nodes without specifying the application namespace.
  3. Inspect only the VPC routes table.
  4. Create a new Cloud Storage bucket.

Explanation

Correct Answer

A:

The Pod list shows the namespace's running and pending workload objects and their high-level status.

Incorrect Answers

B:

Node inventory shows cluster hosts, not the Pods in the named application namespace or their scheduling statuses.

C:

Network routes do not list Kubernetes Pods or phases.

D:

Object storage creation cannot query the cluster workload inventory.

Question 236

A Pod is stuck Pending in GKE, and operators suspect a scheduler placement constraint rather than an application exception. Which command shows placement conditions and recent scheduling events?

  1. Query application HTTP access logs from the Pod that never started.
  2. Inspect only the Pod's container image digest in Artifact Registry.
  3. Edit the project's display name.
  4. Use kubectl describe pod for the Pending Pod and inspect conditions and Events.

Explanation

Correct Answer

D:

Pod description exposes scheduler failures such as insufficient resources, taints or unsatisfied affinities.

Incorrect Answers

A:

An unscheduled Pod might have no running application process to emit access logs.

B:

The image digest establishes which build was deployed; Pending placement failures are exposed through Pod scheduling conditions and events instead.

C:

Resource naming does not explain Pod placement events.

Question 237

A Pod's container repeatedly restarts, and the current container starts too briefly to expose the previous failure. What Kubernetes diagnostic command can retrieve logs for the earlier container instance?

  1. Run kubectl delete namespace to generate new logs.
  2. Read the currently running container logs without requesting its previous instance.
  3. Run kubectl logs <pod> --previous for the relevant container.
  4. Query Cloud DNS TXT records for the Pod name.

Explanation

Correct Answer

C:

The previous flag retrieves logs retained for the prior terminated container instance, useful for CrashLoopBackOff investigation.

Incorrect Answers

A:

Deleting the namespace destroys workload context rather than reading failure evidence.

B:

If the container has restarted, its current logs may omit the crash; `--previous` retrieves the prior terminated container's logs where available.

D:

DNS records do not contain container crash logs.

Question 238

A Kubernetes Deployment update introduced an invalid container image, and its previous ReplicaSet revision was healthy. The team wants to reverse the Deployment rollout. Which operation is intended?

  1. Delete the entire GKE cluster.
  2. Use kubectl rollout undo deployment/<name> for the affected Deployment.
  3. Run a fresh kubectl rollout restart and keep the defective image revision.
  4. Change the Service's DNS suffix alone.

Explanation

Correct Answer

B:

Deployment rollout history can restore a previous Pod template revision when available.

Incorrect Answers

A:

Cluster deletion is unnecessary and destructive for one Deployment revision problem.

C:

Restarting Pods against the same bad Deployment template repeats the failure; rollout undo selects a known earlier ReplicaSet revision.

D:

Service naming cannot roll back the container image in the Deployment's Pod template.

Question 239

A clustered database's Kubernetes replicas require stable names, persistent storage identities and predictable ordered rollout behavior. Which workload controller suits these stateful requirements?

  1. Use a StatefulSet with suitable persistent volume claim templates.
  2. Use a Deployment with only ephemeral scratch storage and assume stable Pod names.
  3. Create a Cloud DNS public zone for every database row.
  4. Use a Deployment with randomly named Pods and ephemeral volumes as the database's identity layer.

Explanation

Correct Answer

A:

StatefulSets preserve ordinal Pod identities and stable storage association across Pod replacement for supported stateful applications.

Incorrect Answers

B:

Deployments do not promise stable Pod identities and ephemeral storage is unsuitable for required state continuity.

C:

DNS naming does not implement Kubernetes stateful workload identity.

D:

Deployment Pods and ephemeral volumes do not provide the stable network identifiers and persistent volume claim identity needed for clustered stateful nodes.

Question 240

An operations team wants exactly one eligible log collector Pod scheduled on each GKE Standard worker node, including future nodes added to the pool. Which Kubernetes controller is intended for this pattern?

  1. Use a single-replica Deployment and assume one Pod appears on every node.
  2. Deploy one Deployment replica and enable a readiness probe on it.
  3. Give the collector an external IP without a workload controller.
  4. Deploy a DaemonSet with appropriate node constraints and permissions.

Explanation

Correct Answer

D:

A DaemonSet manages node-level Pod placement across eligible cluster nodes as nodes are added or removed.

Incorrect Answers

A:

A Deployment replica count does not track the number of nodes or guarantee node-by-node coverage.

B:

A Deployment's replica count is not the mechanism that schedules one eligible collector on every node; DaemonSet handles node-based placement.

C:

Public addressing does not place an agent on each node.