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 23

Question 220

A Terraform plan creates managed credentials. The team marks outputs sensitive and concludes its remote state may be made public because the CLI hides those output values. What security control is still required?

  1. Make the state object publicly readable to simplify debugging.
  2. Store the state in a public Cloud DNS record.
  3. Disable all CI audit logs so nobody can see state activity.
  4. Protect Terraform state storage and access because sensitive values can still appear in the state data.

Explanation

Correct Answer

D:

The sensitive output flag masks displays but does not universally remove secret values from persisted state; backend permissions remain essential.

Incorrect Answers

A:

Public state access can leak credentials or internal infrastructure details.

B:

DNS is neither confidential nor a suitable state backend.

C:

Removing logs does not protect stored state and reduces accountability.

Question 221

A platform team deploys the same Kubernetes service to development and production with different replicas, images and ingress values. They want parameterized reusable Kubernetes manifests, not hand-edited copies. Which package format fits?

  1. Maintain two separate hard-coded Kubernetes manifest trees with no reusable values.
  2. A Google Cloud IAM role binding for each YAML line.
  3. A Helm chart with environment-specific values files.
  4. A public DNS TXT record with a copy of the entire Pod spec.

Explanation

Correct Answer

C:

Helm charts template and package Kubernetes resource definitions while values parameterize differences between deployments.

Incorrect Answers

A:

Duplicating complete manifests makes environment-specific drift likely; one Helm chart with values files separates shared definitions from deliberate differences.

B:

IAM controls identity authorization and cannot template Kubernetes objects.

D:

DNS records are not a managed Kubernetes release package.

Question 222

An upgraded Helm release deployed broken Kubernetes manifests, and the team needs to restore the chart's prior recorded release revision rather than manually reconstruct old YAML files. Which operation fits?

  1. Run terraform destroy on the cluster.
  2. Use helm rollback on the release to a known prior revision.
  3. Delete the application's Artifact Registry repository.
  4. Apply kubectl rollout undo to the Deployment without examining the Helm release history.

Explanation

Correct Answer

B:

Helm records release history and can reapply a prior chart revision's Kubernetes resources.

Incorrect Answers

A:

Destroy would remove infrastructure rather than restore one application release.

C:

Deleting images risks breaking rollback and does not restore the Helm release.

D:

A Kubernetes rollout undo acts on a Deployment revision and may not revert the Helm-managed chart values and all release resources to the prior Helm revision.

Question 223

A GKE team already uses Kubernetes GitOps and wants supported Google Cloud infrastructure, such as service accounts or buckets, represented declaratively as Kubernetes custom resources. Which tool is designed for that model?

  1. Config Connector with its supported resource CRDs and appropriate identity permissions.
  2. Manage Google Cloud resources only through ConfigMaps holding informal configuration text.
  3. A public Cloud DNS zone containing Terraform state.
  4. VM Manager patch deployments for Kubernetes YAML.

Explanation

Correct Answer

A:

Config Connector reconciles supported Google Cloud resources from Kubernetes manifests using Kubernetes-native APIs.

Incorrect Answers

B:

ConfigMaps do not reconcile Google Cloud APIs as Kubernetes custom resources; Config Connector CRDs and a controller provide that integration.

C:

DNS storage does not reconcile Google Cloud resources.

D:

Guest OS patching cannot turn infrastructure CRDs into cloud resources.

Question 224

A Config Connector custom resource is applied but the corresponding Google Cloud object hasn't reached its desired state. Where should an operator inspect the controller's reported readiness and errors?

  1. Inspect only the generated Kubernetes resource name without its status conditions.
  2. Rename the Kubernetes namespace and assume that fixes the resource.
  3. Run a Cloud DNS MX lookup for the controller.
  4. Inspect the Kubernetes custom resource's status and reconciliation conditions or events.

Explanation

Correct Answer

D:

Config Connector exposes reconciliation results on managed Kubernetes resources, helping distinguish pending, failed and ready states.

Incorrect Answers

A:

A name confirms object submission but cannot tell whether Config Connector successfully reconciled the requested external Google Cloud resource.

B:

Namespace naming does not reveal or resolve the failing cloud API condition.

C:

Mail DNS is not the source of Config Connector readiness conditions.

Question 225

A cloud platform team wants to start from Google's supported infrastructure-as-code building blocks and opinionated foundation automation rather than hand-craft every landing-zone module. Which approach should it evaluate?

  1. A Cloud Storage lifecycle Delete policy for every account.
  2. A single public DNS zone named foundation.
  3. Google Cloud Foundation Fabric and its FAST reference automation patterns, adapting them under review.
  4. Grant every developer Organization Administrator.

Explanation

Correct Answer

C:

Cloud Foundation Fabric provides reusable Terraform-based cloud foundation modules and FAST patterns that can accelerate reviewed landing-zone deployments.

Incorrect Answers

A:

Object cleanup rules cannot provision a standardized platform foundation.

B:

DNS naming does not define an enterprise landing-zone resource architecture.

D:

Broad privileges do not implement versioned repeatable platform infrastructure.

Question 226

A production engineer needs to locate every Compute Engine VM in a project, including instances in zones outside the currently configured default zone. Which command or view should be used?

  1. Describe only one instance in the active zone.
  2. List Compute Engine instances for the project across zones, filtering and formatting the output as needed.
  3. List Cloud Storage buckets instead.
  4. Run a zonal-only instance list against the administrator's previous active zone.

Explanation

Correct Answer

B:

The instance list API and gcloud compute instances list can return project VM inventory without assuming only the default zone.

Incorrect Answers

A:

Inspecting a single VM cannot establish the project's complete instance inventory.

C:

Buckets are storage resources and do not enumerate virtual machine instances.

D:

A single-zone list can miss instances elsewhere in the project; the requirement is inventory across all zones in the selected project.

Question 227

A Linux Compute Engine VM does not respond to SSH after an OS configuration change. The instance's initial boot messages may explain whether the guest reached networking. What diagnostic evidence should be viewed?

  1. Inspect the VM's serial-port output through an authorized Compute Engine interface.
  2. Read Cloud Monitoring CPU utilization metrics as the only guest boot-failure evidence.
  3. Change only the guest OS SSH key metadata and assume all boot failures are identity failures.
  4. Rely on Cloud Logging application logs even if the guest never completed agent startup.

Explanation

Correct Answer

A:

Serial output can contain early boot errors and kernel or init messages even when the guest network stack is unavailable.

Incorrect Answers

B:

CPU time series show workload activity but may not expose early boot errors and login configuration failures visible in the serial console output.

C:

SSH-key changes cannot explain whether the kernel booted or the network stack initialized; serial output exposes earlier boot progress.

D:

Guest log shipping may not run during a failed boot, whereas instance serial output can retain early boot and kernel messages.

Question 228

A test VM must stop consuming its running vCPU and RAM allocation overnight but retain its persistent disks and instance configuration for tomorrow. Which operation fits, and what remains billable?

  1. Delete the entire project and expect disks to remain.
  2. Suspend the VM but assume all attached disk and reservation charges stop automatically.
  3. Disable Cloud Logging to eliminate all VM charges.
  4. Stop the VM; attached persistent disks and some reserved resources can continue incurring charges.

Explanation

Correct Answer

D:

Stopping releases runtime compute usage while preserving eligible attached resources, which are billed separately.

Incorrect Answers

A:

Project deletion is destructive and does not preserve the stated environment.

B:

Suspension changes execution state but persistent disks and some other allocated resources continue billing; it is not equivalent to eliminating all charges.

C:

Log configuration does not stop vCPU usage or disk storage billing.

Question 229

A Compute Engine VM is completely unresponsive, including its guest shutdown mechanisms, and an operator is authorized to hard-restart it. What operation differs from a graceful stop and start?

  1. Create a Cloud Storage bucket named reset.
  2. Issue an ordinary SSH reboot command despite the guest being fully unresponsive.
  3. Reset the instance, understanding it resembles a hard power cycle and may lose unwritten in-memory data.
  4. Change only the VM label and expect a reset.

Explanation

Correct Answer

C:

A reset forcibly restarts the guest instead of waiting for a graceful shutdown path.

Incorrect Answers

A:

Bucket creation does not change VM power state.

B:

Guest-initiated reboot requires a functioning guest pathway; a Compute Engine reset operates through the control plane when the OS is hung.

D:

Metadata changes do not perform an instance reset.

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.