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 15

Question 140

A dedicated GKE node pool is tainted NoSchedule, and a trusted daemon must run there while general application Pods must remain excluded. What should the trusted daemon's Pod specification include?

  1. Use a nodeSelector matching the tainted nodes without a matching toleration.
  2. Add a public service load balancer to the daemon.
  3. Increase the Pod's logging verbosity.
  4. A matching toleration for the node taint, together with appropriate placement constraints where needed.

Explanation

Correct Answer

D:

The toleration allows scheduling onto tainted nodes; other Pods without it remain ineligible.

Incorrect Answers

A:

A node selector chooses candidate nodes, but the NoSchedule taint still prevents scheduling unless the trusted Pod tolerates that taint.

B:

Service exposure does not satisfy a NoSchedule taint.

C:

Application logs do not authorize scheduling on a tainted node.

Question 141

A GPU-bound Kubernetes Pod should run only on GKE nodes labeled accelerator=nvidia and fail scheduling rather than land on CPU-only nodes. What should the Pod manifest include?

  1. A Cloud DNS TXT record containing accelerator=nvidia.
  2. Specify the GPU node label only as a Kubernetes annotation on the Pod.
  3. Required node affinity or a nodeSelector matching accelerator=nvidia.
  4. A longer Pod termination grace period.

Explanation

Correct Answer

C:

The scheduler uses label-based placement constraints to keep the Pod on eligible node pools.

Incorrect Answers

A:

DNS data does not constrain Kubernetes Pod node placement.

B:

Annotations are not required node-placement selectors; without nodeSelector or required affinity, the scheduler may still place the Pod on non-GPU nodes.

D:

Grace periods affect shutdown handling, not eligibility for nodes with GPU labels.

Question 142

A Kubernetes application must be reachable through a load-balanced private IP from approved VPC clients, but should not have a public internet address. Which GKE Service exposure is appropriate?

  1. Use a public external LoadBalancer Service by default.
  2. Create an internal LoadBalancer Service using the supported internal-load-balancer annotation and network settings.
  3. Set the Pod's containerPort to 443 without a Service.
  4. Add only a Cloud Storage bucket policy.

Explanation

Correct Answer

B:

An internal GKE load balancer exposes the Service through a private address within allowed network paths.

Incorrect Answers

A:

An external service address would violate the private-only accessibility requirement.

C:

A container port alone does not provision a private load-balanced endpoint.

D:

Bucket IAM does not expose traffic to Kubernetes Pods.

Question 143

A small service receives sporadic HTTPS API requests. Developers provide a container image, need automatic request-driven scaling, and do not want to administer VMs or Kubernetes clusters. Which compute service is the direct fit?

  1. Deploy the container as a Cloud Run service.
  2. Use an unmanaged instance group without any autoscaling.
  3. Store the container image in Cloud Storage without deploying it.
  4. Run a Cloud SQL read replica as the HTTP handler.

Explanation

Correct Answer

A:

Cloud Run serves HTTPS traffic from containers and scales compute in response to requests without node management.

Incorrect Answers

B:

Unmanaged VMs require ongoing capacity and operating-system administration.

C:

An image object does not execute requests as a service.

D:

Database replicas do not serve arbitrary containerized HTTPS application logic.

Question 144

A nightly report generator should run a container until work finishes and exit. It does not need an always-on HTTP endpoint or request routing. Which Cloud Run execution model fits?

  1. Deploy a public HTTP Cloud Run service only to keep it polling itself all night.
  2. Store the report code in a Cloud DNS zone.
  3. Use a Cloud Run service and configure it to keep serving HTTP requests indefinitely.
  4. Deploy and schedule a Cloud Run job, with suitable retry and task settings.

Explanation

Correct Answer

D:

Cloud Run jobs execute finite container tasks to completion rather than responding to inbound web requests.

Incorrect Answers

A:

A service is request-driven and adds an unnecessary endpoint for this finite task.

B:

A DNS record points clients to an endpoint; it has no container execution lifecycle, task completion status, or scheduler semantics.

C:

A continuously serving HTTP service is unnecessary for a nightly finite task; Cloud Run jobs have completion and retry semantics for scheduled batch work.

Question 145

A Cloud Run API has very intermittent traffic but contractual latency measurements show excessive cold starts when the service has scaled to zero. What setting can keep some warm capacity available?

  1. Set the service's maximum instances to zero.
  2. Create a Cloud Storage Archive object each minute.
  3. Configure an appropriate minimum instance count for the Cloud Run service.
  4. Increase the DNS record TTL to a year.

Explanation

Correct Answer

C:

Minimum instances retain ready capacity during idle periods, reducing cold-start latency at an added cost.

Incorrect Answers

A:

Zero maximum capacity cannot provide warm request handlers.

B:

Object lifecycle and storage class do not keep application containers warm.

D:

DNS caching cannot keep Cloud Run container instances active.

Question 146

A Cloud Run service opens several database connections per instance. Sudden traffic spikes risk exhausting the database's connection limit, so the team needs an upper bound on the service's instance population. Which control is relevant?

  1. Increase Cloud Run concurrency without setting any maximum-instance bound.
  2. Configure a Cloud Run maximum instances limit and evaluate concurrency and downstream capacity.
  3. Configure only a minimum-instances setting to keep warm containers ready.
  4. Enable more CPU per Cloud Run instance without constraining total instance count.

Explanation

Correct Answer

B:

Instance limits constrain scale-out and can bound database connection demand, though requests may queue or fail under heavy load.

Incorrect Answers

A:

Higher concurrency may reduce instances but does not provide the explicit upper limit needed to protect downstream database connection capacity.

C:

Minimum instances controls the warm floor, not the upper number of instances that can open simultaneous database connections.

D:

More per-instance CPU does not impose a maximum instance count or guarantee that database connections stay below the database limit.

Question 147

A Cloud Run container processes memory-intensive requests and fails when too many simultaneous requests share one instance. The team wants to decrease simultaneous requests per container instance. What should it change?

  1. Reduce the Cloud Run service's per-instance concurrency setting.
  2. Change the public DNS record type from A to MX.
  3. Increase the maximum Cloud Run instance count without changing per-instance request concurrency.
  4. Change a Cloud SQL backup retention rule.

Explanation

Correct Answer

A:

Concurrency limits bound in-flight requests directed to each instance, helping protect memory-constrained handlers.

Incorrect Answers

B:

Mail DNS records have no effect on HTTP concurrency inside containers.

C:

Higher instance limits may increase fleet capacity but do not limit how many memory-intensive requests a single instance processes simultaneously.

D:

Backup policy does not affect how many requests Cloud Run dispatches concurrently.

Question 148

A legitimate Cloud Run HTTP request takes 11 minutes, but the service currently uses a shorter configured request timeout and returns an error before completion. What should be reviewed?

  1. Raise Cloud Run concurrency so more requests share each instance.
  2. Increase the minimum instance count to keep the service warm.
  3. Increase the container memory limit without changing request timeout.
  4. Increase the Cloud Run request timeout within supported limits or move long-running processing to a suitable asynchronous model.

Explanation

Correct Answer

D:

The request timeout bounds how long Cloud Run waits for a service response; the value must accommodate eligible request duration.

Incorrect Answers

A:

Concurrency controls simultaneous requests per instance and does not extend how long the platform permits an individual request to run.

B:

Warm instances reduce cold starts but cannot prevent the configured request timeout from terminating a valid eleven-minute request.

C:

More memory can avoid memory pressure, but it does not change the configured deadline that ends an eleven-minute HTTP request.

Question 149

An internal-only Cloud Run application must accept requests solely through supported private or internal routes, not directly from the public internet, while still using IAM authentication. Which service configuration is relevant?

  1. Allow unauthenticated access on the public endpoint.
  2. Add a public DNS A record as the primary restriction.
  3. Set the Cloud Run ingress restriction to the appropriate internal access mode.
  4. Require IAM authentication on an internet-reachable Cloud Run ingress endpoint.

Explanation

Correct Answer

C:

Ingress settings restrict permitted network sources; IAM authorization can then independently control who invokes the service.

Incorrect Answers

A:

Public invoker access would weaken the identity boundary and not restrict the network source.

B:

DNS publication cannot prevent direct requests from other networks.

D:

IAM controls who can invoke a service, but the requirement specifically restricts which network ingress routes can reach the service at all.

Question 150

A containerized Cloud Run application needs a database password stored centrally and rotated by security staff. Developers must not bake the password into the container image. What integration is appropriate?

  1. Put the password in a public Dockerfile ARG and rebuild the image.
  2. Configure Cloud Run to reference the approved Secret Manager secret as an environment variable or mounted volume.
  3. Store the password in a public Cloud DNS TXT record.
  4. Embed the database password in a Cloud Run environment variable in the deployment manifest.

Explanation

Correct Answer

B:

Secret Manager integration supplies secrets at runtime through service identity and configuration rather than embedding credentials in immutable images.

Incorrect Answers

A:

Build arguments or image layers can expose credentials and defeat secret rotation separation.

C:

Public DNS records reveal secrets to query clients.

D:

A plaintext secret in deployment configuration remains exposed through configuration management; Secret Manager integration retrieves a controlled secret version.