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 47

Question 460

A Cloud Run container's initialization takes longer than the configured startup probe and the platform restarts it before it can listen. What should change?

  1. Shift production traffic to the verified healthy revision A using Cloud Run traffic controls, while recording incident evidence.
  2. Change only the Cloud Run maximum instance count and assume all other service configuration follows.
  3. Increase Cloud Run memory alone while leaving the failing routing, identity or event setting unchanged.
  4. Align the startup probe timing and application initialization with supported Cloud Run readiness behavior.

Explanation

Correct Answer

D:

Aggressive probes can kill slow-starting healthy containers before initialization completes; increasing CPU alone may not repair probe semantics.

Incorrect Answers

A:

The change does not configure the Cloud Run runtime or traffic behavior at issue. The necessary distinction is the Cloud Run service setting. The appropriate action here is: Align the startup probe timing and application initialization with supported Cloud Run readiness behavior.

B:

The change does not configure the Cloud Run runtime or traffic behavior at issue. The case instead depends on the Cloud Run service setting. The appropriate action here is: Align the startup probe timing and application initialization with supported Cloud Run readiness behavior.

C:

Memory sizing may change capacity but cannot replace the specified platform feature. It leaves the Cloud Run service setting unaddressed.

Question 461

A service binds only to 127.0.0.1 inside its Cloud Run container and cannot accept platform health traffic. What should the container listen on?

  1. Align the startup probe timing and application initialization with supported Cloud Run readiness behavior.
  2. Deploy a new revision to all traffic without checking the intended rollout behavior.
  3. Delete the working revision before confirming that the replacement can serve requests.
  4. Bind the HTTP server to the configured PORT on all container interfaces rather than loopback only.

Explanation

Correct Answer

D:

Cloud Run's ingress sends requests to the container's listening port; a loopback-only listener cannot serve routed requests.

Incorrect Answers

A:

The change does not configure the Cloud Run runtime or traffic behavior at issue. The case instead depends on the Cloud Run service setting. The appropriate action here is: Bind the HTTP server to the configured PORT on all container interfaces rather than loopback only.

B:

The change does not configure the Cloud Run runtime or traffic behavior at issue. It leaves the Cloud Run service setting unaddressed. The appropriate action here is: Bind the HTTP server to the configured PORT on all container interfaces rather than loopback only.

C:

The change does not configure the Cloud Run runtime or traffic behavior at issue. The specific requirement concerns the Cloud Run service setting. The appropriate action here is: Bind the HTTP server to the configured PORT on all container interfaces rather than loopback only.

Question 462

A Cloud Run service worked during a developer's local test but receives a Google API permission-denied error after deployment. The developer's interactive credentials have the required role. Which identity should be checked for the application's outgoing API call?

  1. Grant the local developer organization Owner; Cloud Run always executes API calls as the latest user who ran gcloud deploy.
  2. Assign Cloud Run Invoker to arbitrary external users; inbound invocation automatically supplies outbound resource permissions.
  3. Inspect the deployed Cloud Run revision's runtime service account and grant that principal the required least-privilege target-resource permission.
  4. Change the service URL; the hostname determines which Google Cloud API IAM role the container uses.

Explanation

Correct Answer

C:

Inspect the deployed Cloud Run revision's runtime service account and grant that principal the required least-privilege target-resource permission. The runtime service account is the identity that receives application default credentials in Cloud Run. Granting its narrowly required role addresses a 403 on outbound calls.

Incorrect Answers

A:

Grant the local developer organization Owner; Cloud Run always executes API calls as the latest user who ran gcloud deploy. Cloud Run uses its configured service identity for application API calls, not the user's interactive developer credentials.

B:

Assign Cloud Run Invoker to arbitrary external users; inbound invocation automatically supplies outbound resource permissions. Cloud Run Invoker permits an inbound call to the service. It is separate from the identity's permissions to reach Cloud Storage, BigQuery or other services.

D:

Change the service URL; the hostname determines which Google Cloud API IAM role the container uses. A URL change alters endpoint routing but does not change the effective IAM roles of the container's service identity.

Question 463

A Cloud Run job runs for several minutes and is mistakenly deployed as a normal service requiring an HTTP response. Which resource better fits the workload?

  1. Inspect per-task statuses, retry limits and aggregate job completion criteria rather than relying on a single container log line.
  2. Switch the service to public unauthenticated ingress as a workaround for the stated requirement.
  3. Move the container image to another registry while leaving the failing trigger and permissions untouched.
  4. Create a Cloud Run job for finite background processing with appropriate task timeout and retries.

Explanation

Correct Answer

D:

Cloud Run jobs are designed for run-to-completion tasks; a web service's request/response contract is not the same as a batch task.

Incorrect Answers

A:

Retries repeat operations; they do not correct missing permissions or invalid configuration. The specific requirement concerns the Cloud Run service setting.

B:

The change does not configure the Cloud Run runtime or traffic behavior at issue. The necessary distinction is the Cloud Run service setting. The appropriate action here is: Create a Cloud Run job for finite background processing with appropriate task timeout and retries.

C:

The change does not configure the Cloud Run runtime or traffic behavior at issue. The case instead depends on the Cloud Run service setting. The appropriate action here is: Create a Cloud Run job for finite background processing with appropriate task timeout and retries.

Question 464

An event-driven Cloud Run handler is invoked twice for a single Cloud Storage object finalize event and writes duplicate invoice records. What safeguard should be added?

  1. Create a Cloud Run job for finite background processing with appropriate task timeout and retries.
  2. Delete the working revision before confirming that the replacement can serve requests.
  3. Use event identifiers or object generation as an idempotency key and make the database write conditional on prior processing.
  4. Switch the service to public unauthenticated ingress as a workaround for the stated requirement.

Explanation

Correct Answer

C:

Event delivery can be at least once; processing logic must tolerate retried or duplicate events.

Incorrect Answers

A:

Timeouts control waiting time, not the missing platform feature or access right. The necessary distinction is the required Cloud Storage behavior.

B:

The change does not configure the Cloud Run runtime or traffic behavior at issue. The case instead depends on the required Cloud Storage behavior.

D:

The change does not configure the Cloud Run runtime or traffic behavior at issue. It leaves the required Cloud Storage behavior unaddressed.

Question 465

A Cloud Run service reads an environment variable for production credentials that was mistakenly embedded directly in source code. How should the secret be delivered?

  1. Use approved Secret Manager integration with least-privilege runtime identity and rotate the exposed secret.
  2. Inspect the deployed Cloud Run revision's runtime service account and grant that principal the required least-privilege target-resource permission.
  3. Delete the working revision before confirming that the replacement can serve requests.
  4. Increase Cloud Run memory alone while leaving the failing routing, identity or event setting unchanged.

Explanation

Correct Answer

A:

A string in source control is not a governed secret; Cloud Run can consume secrets without hardcoding credentials in the image.

Incorrect Answers

B:

The change does not configure the Cloud Run runtime or traffic behavior at issue. The case instead depends on the Cloud Run service setting. The appropriate action here is: Use approved Secret Manager integration with least-privilege runtime identity and rotate the exposed secret.

C:

The change does not configure the Cloud Run runtime or traffic behavior at issue. It leaves the Cloud Run service setting unaddressed. The appropriate action here is: Use approved Secret Manager integration with least-privilege runtime identity and rotate the exposed secret.

D:

Memory sizing may change capacity but cannot replace the specified platform feature. The specific requirement concerns the Cloud Run service setting.

Question 466

A public webhook endpoint has no authentication although its payload controls expensive compute actions. What protection should be designed?

  1. Update the centrally governed OS Login and organization access settings, validating the supported certificate and IAM flow for users.
  2. Restart the instance repeatedly while leaving the underlying error or missing dependency in place.
  3. Give the attached VM service account project Owner instead of fixing resource configuration.
  4. Require a supported signed request or authenticated invoker contract with replay protection and least-privilege downstream authorization.

Explanation

Correct Answer

D:

A public route need not be an unauthenticated trust boundary; validating caller identity reduces abuse of event-triggered actions.

Incorrect Answers

A:

The proposed setting does not correct the stated machine, disk or scheduling requirement. It leaves the actual compute scheduling or resource condition unaddressed. The appropriate action here is: Require a supported signed request or authenticated invoker contract with replay protection and least-privilege downstream authorization.

B:

The proposed setting does not correct the stated machine, disk or scheduling requirement. The specific requirement concerns the actual compute scheduling or resource condition. The appropriate action here is: Require a supported signed request or authenticated invoker contract with replay protection and least-privilege downstream authorization.

C:

Project Owner broadens authorization and is not an appropriate substitute for the named control. The necessary distinction is the actual compute scheduling or resource condition. The appropriate action here is: Require a supported signed request or authenticated invoker contract with replay protection and least-privilege downstream authorization.

Question 467

A private Cloud Run service rejects Pub/Sub push deliveries with HTTP 401. The Cloud Run runtime service account already reads its own database successfully. Which separate caller authorization is required?

  1. Grant the Cloud Run runtime service account the Storage Admin role; the service identity and push caller are interchangeable.
  2. Disable Pub/Sub push authentication; a private Cloud Run service automatically trusts any request with a Pub/Sub User-Agent.
  3. Grant Pub/Sub Subscriber to every project user; pull permissions automatically provide Cloud Run request authorization for push.
  4. Configure the push subscription's OIDC identity/audience and grant its authenticated service account permission to invoke this Cloud Run service.

Explanation

Correct Answer

D:

Configure the push subscription's OIDC identity/audience and grant its authenticated service account permission to invoke this Cloud Run service. Pub/Sub authenticated push sends an identity token for the configured caller. That identity needs Cloud Run Invoker permission and a valid audience for the target service.

Incorrect Answers

A:

Grant the Cloud Run runtime service account the Storage Admin role; the service identity and push caller are interchangeable. The runtime identity authorizes outgoing calls made by Cloud Run. It is not automatically the authenticated principal that Pub/Sub presents on inbound requests.

B:

Disable Pub/Sub push authentication; a private Cloud Run service automatically trusts any request with a Pub/Sub User-Agent. Removing authentication defeats the private ingress requirement and does not create a valid caller identity for Cloud Run IAM.

C:

Grant Pub/Sub Subscriber to every project user; pull permissions automatically provide Cloud Run request authorization for push. Pub/Sub subscriber permissions govern subscription operations and are not equivalent to permission to invoke a private Cloud Run service.

Question 468

A deployment uses a Cloud Run custom domain and users still receive a certificate warning because DNS points to the old endpoint. What should be checked?

  1. Verify readiness and explicitly update the revision's approved traffic percentage through the service traffic configuration.
  2. Correct domain mapping DNS records and ensure the supported certificate validation process completes for the intended service.
  3. Switch the service to public unauthenticated ingress as a workaround for the stated requirement.
  4. Change only the Cloud Run maximum instance count and assume all other service configuration follows.

Explanation

Correct Answer

B:

A mapped hostname must resolve to the proper service target before managed TLS validation and traffic can function correctly.

Incorrect Answers

A:

The change does not configure the Cloud Run runtime or traffic behavior at issue. The necessary distinction is the Cloud Run service setting. The appropriate action here is: Correct domain mapping DNS records and ensure the supported certificate validation process completes for the intended service.

C:

The change does not configure the Cloud Run runtime or traffic behavior at issue. The case instead depends on the Cloud Run service setting. The appropriate action here is: Correct domain mapping DNS records and ensure the supported certificate validation process completes for the intended service.

D:

The change does not configure the Cloud Run runtime or traffic behavior at issue. It leaves the Cloud Run service setting unaddressed. The appropriate action here is: Correct domain mapping DNS records and ensure the supported certificate validation process completes for the intended service.

Question 469

A service handles confidential requests but is configured to log raw authorization headers on every invocation. What is the necessary operational change?

  1. Keep synchronous calls within supported request limits and move prolonged report work to a job or asynchronous workflow.
  2. Change the instance display name as a replacement for modifying the actual machine or disk.
  3. Create a snapshot only and assume it immediately changes the live VM capacity.
  4. Redact sensitive request headers and set least-privilege log access and retention before enabling production request logging.

Explanation

Correct Answer

D:

Cloud Run request logs and application logs can expose secrets independently of transport encryption.

Incorrect Answers

A:

The proposed setting does not correct the stated machine, disk or scheduling requirement. The case instead depends on retention or recoverability controls.

B:

Display names and labels identify resources; they do not enforce their runtime behavior. It leaves retention or recoverability controls unaddressed.

C:

Snapshots are recovery artifacts and do not directly reconfigure a running resource. The specific requirement concerns retention or recoverability controls.

Question 470

A team deploys a new container and then loses the prior image tag because it reused a mutable latest tag, undermining rollback. What should it retain?

  1. Produce and validate a governed custom image or image family from the approved golden source with version control.
  2. Deploy using immutable image digests or versioned tags and keep previous proven images available for rollback.
  3. Increase the VM vCPU quota without changing the failed configuration or resource setting.
  4. Change the instance display name as a replacement for modifying the actual machine or disk.

Explanation

Correct Answer

B:

Container image references must be reproducible; mutable tags can point to different bytes across releases.

Incorrect Answers

A:

The proposed setting does not correct the stated machine, disk or scheduling requirement. It leaves the actual compute scheduling or resource condition unaddressed. The appropriate action here is: Deploy using immutable image digests or versioned tags and keep previous proven images available for rollback.

C:

More CPU quota affects capacity, not the API or policy decision described. The specific requirement concerns the actual compute scheduling or resource condition. The appropriate action here is: Deploy using immutable image digests or versioned tags and keep previous proven images available for rollback.

D:

Display names and labels identify resources; they do not enforce their runtime behavior. The necessary distinction is the actual compute scheduling or resource condition. The appropriate action here is: Deploy using immutable image digests or versioned tags and keep previous proven images available for rollback.

Associate Cloud Engineer Practice Tests