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 25

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.

Question 241

A Pod starts quickly but needs a minute to warm its local cache before serving requests. The team wants it excluded from Service endpoints until it is ready, without restarting it during warmup. Which probe is appropriate?

  1. Configure a liveness probe that fails throughout the normal warmup period.
  2. Configure only a liveness probe that checks whether the process exists.
  3. Configure a readiness probe that succeeds only after the application can serve traffic.
  4. Add a DNS TXT record containing ready.

Explanation

Correct Answer

C:

Readiness gates endpoint availability independently from container liveness, preventing premature request routing.

Incorrect Answers

A:

Repeated liveness failures cause restarts, potentially trapping the container in a restart loop.

B:

A liveness probe can restart a process but does not keep an unready yet-running Pod out of Service endpoints during cache warmup.

D:

DNS metadata is not evaluated by the Pod readiness controller.

Question 242

A container sometimes deadlocks while the process remains running and its Pod looks healthy at the operating-system level. Operators want Kubernetes to restart the failed container when an internal health endpoint remains unresponsive. Which probe is appropriate?

  1. Use a readiness probe only and expect it to restart the container.
  2. Configure a liveness probe against the application health condition.
  3. Add a Cloud DNS CNAME for the Pod.
  4. Use only a readiness probe while the application deadlocks after becoming ready.

Explanation

Correct Answer

B:

Liveness probe failures instruct kubelet to restart a container, recovering certain deadlock or stuck-process failures.

Incorrect Answers

A:

Readiness failures remove traffic eligibility but do not by themselves force container restart.

C:

DNS aliases do not detect deadlocks or trigger kubelet restarts.

D:

Readiness removes traffic from an unhealthy Pod but does not restart a deadlocked container; a liveness probe supplies restart detection.

Question 243

An application needs to receive non-sensitive feature toggles and endpoint settings as environment variables or mounted files, without rebuilding its image. Which Kubernetes resource should hold those settings?

  1. Store the ordinary configuration in a ConfigMap and reference it from the Pod specification.
  2. Store the feature toggles in the project's IAM role bindings.
  3. Put the non-sensitive settings into an immutable container image and rebuild for each toggle.
  4. Create a LoadBalancer Service for each configuration value.

Explanation

Correct Answer

A:

ConfigMaps decouple non-secret application configuration from container images and can be mounted or exposed as environment variables.

Incorrect Answers

B:

IAM policies are for resource access authorization, not arbitrary application configuration.

C:

Rebuilding images for configuration changes is unnecessary when a ConfigMap can externalize supported non-secret settings for deployment reuse.

D:

Services route traffic rather than hold application settings.

Question 244

A GKE Pod needs a database password provided through a Kubernetes resource rather than a plaintext ConfigMap; secret storage and access controls will be configured appropriately. Which resource type is intended?

  1. Put the password in a Kubernetes ConfigMap with base64-encoded data.
  2. Embed the database password as a literal value in the Deployment manifest.
  3. Store the password only as an unencrypted Kubernetes annotation on the Pod.
  4. Create a Kubernetes Secret and reference it from the Pod securely.

Explanation

Correct Answer

D:

Secrets are Kubernetes resources intended for confidential configuration, though encryption, RBAC and handling still need protection.

Incorrect Answers

A:

Encoding a ConfigMap value does not make it a Secret; the configuration remains an ordinary non-secret resource with different security expectations.

B:

Hard-coding credentials in a workload manifest increases exposure in deployment artifacts and bypasses the Secret resource required by the scenario.

C:

Annotations are workload metadata rather than Secret references and may be widely readable through Kubernetes object inspection.

Question 245

A Kubernetes Deployment already has capacity on its GKE nodes, but incoming requests increase per-Pod CPU utilization. The application is stateless and needs additional Pod replicas as demand rises. Which autoscaling component should be configured?

  1. Only increase the number of GKE nodes without changing Pod replica count.
  2. Change the Cloud Storage lifecycle policy.
  3. Horizontal Pod Autoscaler based on a supported CPU utilization metric and target.
  4. Configure a fixed Deployment replica count without a CPU metric target.

Explanation

Correct Answer

C:

HPA adjusts the number of Pod replicas in response to metrics while cluster node capacity is handled separately.

Incorrect Answers

A:

Additional nodes do not cause a fixed-size Deployment to schedule more application Pods.

B:

Cloud Storage lifecycle actions change objects, whereas additional Kubernetes application replicas require a Deployment replica adjustment driven by HPA.

D:

Static replicas do not respond automatically when CPU utilization rises; HPA changes Pod replica count based on a supported metric.

Question 246

A long-running Kubernetes application frequently requests too little memory and is evicted or OOM-killed. The team wants recommendations for suitable Pod resource requests based on observed usage. Which GKE capability fits?

  1. Increase Horizontal Pod Autoscaler replica count without adjusting the Pod memory request.
  2. Use Vertical Pod Autoscaler in an appropriate recommendation or update mode.
  3. Set the number of replicas to one regardless of per-Pod memory needs.
  4. Use Cluster Autoscaler to add more nodes but leave every Pod’s memory sizing unchanged.

Explanation

Correct Answer

B:

VPA analyzes supported resource usage and can recommend or update CPU and memory requests for Kubernetes Pods.

Incorrect Answers

A:

HPA scales the number of Pods; it does not fix an insufficient memory request or limit inside each individual Pod.

C:

Replica count is a horizontal scale factor, not a recommendation for individual Pod memory allocation.

D:

Additional node capacity helps scheduling; the Pod can still be OOM-killed when its own configured resources do not match memory usage.

Question 247

A GKE Autopilot workload is being rejected or adjusted because its Pod resource requests fall outside supported resource constraints. What specification should developers inspect?

  1. The Pod's CPU, memory and ephemeral storage requests against Autopilot's workload-class rules.
  2. The company's public DNS TTL.
  3. Inspect only the Pod's memory usage after admission rather than its resource requests.
  4. The name of the Cloud Storage logging bucket.

Explanation

Correct Answer

A:

Autopilot manages nodes and requires valid workload resource requests so it can provision appropriate compute capacity.

Incorrect Answers

B:

DNS caching does not validate Kubernetes resource requests.

C:

Autopilot admission and scheduling consider declared CPU/memory/ephemeral storage requests, not merely later consumption measurements.

D:

Storage names cannot determine valid Pod CPU and memory allocations.

Question 248

A GKE workload fails to pull a private container image from Artifact Registry with an authorization error. The image path exists, and networking works. Which identity permission should the operator check?

  1. Make the registry completely public to every internet user.
  2. Change the Pod's CPU request to zero.
  3. Give the Pod only a Kubernetes Role allowing it to read Kubernetes Secrets.
  4. Grant the appropriate Artifact Registry Reader access to the identity used for pulling images, scoped to the repository as supported.

Explanation

Correct Answer

D:

Image pulls require registry permissions for the relevant node or workload identity, independent of the Pod manifest's image name.

Incorrect Answers

A:

Public access is unnecessary and violates the private-image requirement.

B:

Compute requests do not fix registry IAM authorization.

C:

Kubernetes RBAC governs API objects inside the cluster; pulling private Artifact Registry images also requires Google Cloud registry access for the image-pull identity.

Question 249

A GKE Standard cluster has multiple node pools and an administrator must upgrade one pool's nodes while minimizing disruption, rather than forcing a whole-cluster rebuild. Which operation is appropriate?

  1. Delete the entire GKE cluster and recreate it.
  2. Modify only the cluster DNS suffix.
  3. Run a supported node-pool upgrade with appropriate surge or rollout settings.
  4. Change the GKE control plane version and assume every node pool upgrades automatically at once.

Explanation

Correct Answer

C:

Node-pool upgrades replace or update eligible worker nodes and can be controlled to preserve application availability.

Incorrect Answers

A:

Whole-cluster deletion is unnecessarily disruptive for an individual pool upgrade.

B:

DNS naming does not change node software versions.

D:

Control plane version management is separate from targeted node pool upgrade operations; the selected pool needs an appropriate rollout.

Question 250

A team must manually retire a GKE Standard node and wants eligible non-DaemonSet Pods rescheduled elsewhere before the node is shut down. Which Kubernetes operation belongs in the drain procedure?

  1. Run kubectl cordon only, then immediately power off the node without evicting current Pods.
  2. Cordon and drain the node using kubectl drain with appropriate eviction and disruption considerations.
  3. Delete the node immediately and rely on the scheduler to move stateful Pods safely.
  4. Lower the node pool minimum size without draining this particular node.

Explanation

Correct Answer

B:

Draining marks the node unavailable for new Pods and evicts eligible workloads to support controlled node maintenance.

Incorrect Answers

A:

Cordon prevents new scheduling but does not move existing eligible Pods or respect their eviction and disruption constraints.

C:

Abrupt node removal can violate disruption budgets or interrupt workloads; cordon/drain coordinates eligible eviction before retirement.

D:

Changing pool scale limits does not safely evict and relocate workloads from the specific node being retired.