Google Associate Cloud Engineer Practice Test 41

Question 400

An application must consume a password without placing it directly in a Deployment manifest. Which configuration best meets the requirement?

  1. Select an appropriate Kubernetes StorageClass in its claim
  2. Mount the ConfigMap or expose its values through the Pod spec
  3. Use a Kubernetes Secret or approved external secret integration
  4. Create a PersistentVolumeClaim using a supported StorageClass
  5. Run kubectl rollout undo on the Deployment

Explanation

Correct Answer

C:

Secrets provide a Kubernetes interface for sensitive values with access-control requirements. They still need encryption and RBAC practices appropriate to risk.

Incorrect Answers

A:

Select this when the goal is to choose a Kubernetes persistent storage class. Here the decisive requirement is to avoid hardcoded manifest passwords, and that outcome is not achieved by this action.

B:

This mechanism is intended to inject non-secret Kubernetes configuration. It does not implement the required action to avoid hardcoded manifest passwords, even though both are relevant to the same general service.

D:

Administrators use it to request persistent Kubernetes storage, rather than to avoid hardcoded manifest passwords. Applying it would change the wrong component of this deployment.

E:

This proposal can roll back a Kubernetes Deployment, but the failure or goal described here calls for a way to avoid hardcoded manifest passwords; It changes the wrong control or scope for the requested outcome.

Question 401

A production Cloud Run service requires a new container image while retaining the ability to route back to an old release. Which choice provides the required behavior?

  1. Shift Cloud Run traffic allocation back to the healthy prior revision
  2. Inspect the service's revisions and traffic configuration
  3. Deploy a new Cloud Run revision
  4. Configure the service traffic split with the candidate revision receiving 5%

Explanation

Correct Answer

C:

Cloud Run revisions are immutable deployment snapshots. Previous revisions can remain available for configured traffic routing when retained.

Incorrect Answers

A:

This choice is useful to roll back active Cloud Run request routing. The stated task is to release an updated container safely, which requires a different mechanism or permission scope.

B:

This setting would list Cloud Run revisions and traffic percentages. That behavior does not establish the requested ability to release an updated container safely; it addresses an adjacent concern instead.

D:

Using this action would canary a Cloud Run revision by percentage, not release an updated container safely. Its function is different from the specific change described in the scenario.

Question 402

A service owner wants 5% of new traffic sent to a candidate Cloud Run revision. Which approach should be selected?

  1. Shift Cloud Run traffic allocation back to the healthy prior revision
  2. Deploy a new Cloud Run revision
  3. Inspect the service's revisions and traffic configuration
  4. Configure the service traffic split with the candidate revision receiving 5%
  5. Use gcloud compute ssh over a direct reachable address with appropriate access

Explanation

Correct Answer

D:

Cloud Run traffic allocations can distribute requests across eligible revisions. A new revision does not require immediate 100% traffic routing.

Incorrect Answers

A:

The result of this choice would be to roll back active Cloud Run request routing. The requested outcome, to test a new version with limited requests, is handled at a different layer or through another operation.

B:

Administrators use it to create a new immutable serverless revision, rather than to test a new version with limited requests. Applying it would change the wrong component of this deployment.

C:

While this can list Cloud Run revisions and traffic percentages, the present task requires an action to test a new version with limited requests. This operation does not supply the behavior described in the requirements.

E:

Its purpose is to start a direct CLI SSH session to a VM. That distinction matters: the scenario calls for an action to test a new version with limited requests, not this separate configuration task.

Question 403

A newly deployed revision is failing and traffic should return to the last known good one. Which method addresses the task?

  1. Shift Cloud Run traffic allocation back to the healthy prior revision
  2. Configure the service traffic split with the candidate revision receiving 5%
  3. Inspect the service's revisions and traffic configuration
  4. Use an appropriate Cloud Run minimum instances setting of zero
  5. Deploy a new Cloud Run revision

Explanation

Correct Answer

A:

Traffic splitting changes which revision serves requests without rebuilding containers. It is a direct rollback route when the earlier revision remains available.

Incorrect Answers

B:

The tool can canary a Cloud Run revision by percentage, but it cannot be substituted for the capability needed to recover from a bad serverless release. Its operational effect is not equivalent.

C:

This choice is useful to list Cloud Run revisions and traffic percentages. The stated task is to recover from a bad serverless release, which requires a different mechanism or permission scope.

D:

This proposal can allow serverless scale-to-zero, but the failure or goal described here calls for a way to recover from a bad serverless release; It changes the wrong control or scope for the requested outcome.

E:

It can create a new immutable serverless revision; however, it does not provide the specific operation to recover from a bad serverless release. The two controls serve different purposes.

Question 404

An operator must identify which Cloud Run revisions exist and how traffic is allocated. What is the best next step?

  1. Shift Cloud Run traffic allocation back to the healthy prior revision
  2. Configure the service traffic split with the candidate revision receiving 5%
  3. Inspect the service's revisions and traffic configuration
  4. Deploy a new Cloud Run revision
  5. Configure Cloud Run minimum instances with appropriate cost awareness

Explanation

Correct Answer

C:

Cloud Run maintains revision metadata and traffic targets. Reviewing both establishes which build receives live requests.

Incorrect Answers

A:

While this can roll back active Cloud Run request routing, the present task requires an action to audit active serverless versions. This operation does not supply the behavior described in the requirements.

B:

Its purpose is to canary a Cloud Run revision by percentage. That distinction matters: the scenario calls for an action to audit active serverless versions, not this separate configuration task.

D:

This approach can create a new immutable serverless revision. The requirement is to audit active serverless versions, so it controls a different part of the workflow and leaves that result unaddressed.

E:

An operator would use this action to keep warm Cloud Run instances, chiefly when trying to reduce latency from instance startup; The current requirement is to audit active serverless versions, which remains unresolved by that operation.

Question 405

An application has unpredictable traffic but must avoid sustained charges for preallocated idle instances. What should the administrator do?

  1. Configure Cloud Run minimum instances with appropriate cost awareness
  2. Use an appropriate Cloud Run minimum instances setting of zero
  3. Reduce Cloud Run concurrency appropriately
  4. Configure a maximum instance cap suited to backend capacity

Explanation

Correct Answer

B:

Scaling to zero can avoid idle instance reservations when supported, with cold-start trade-offs. It does not make active request processing free.

Incorrect Answers

A:

Select this when the goal is to keep warm Cloud Run instances. Here the decisive requirement is to minimize idle container capacity, and that outcome is not achieved by this action.

C:

The result of this choice would be to tune concurrent requests per Cloud Run instance. The requested outcome, to minimize idle container capacity, is handled at a different layer or through another operation.

D:

This mechanism is intended to limit total Cloud Run instances. It does not implement the required action to minimize idle container capacity, even though both are relevant to the same general service.

Question 406

A service must protect a legacy database from a large number of concurrent serverless instances. Which choice provides the required behavior?

  1. Use an appropriate Cloud Run minimum instances setting of zero
  2. Reduce Cloud Run concurrency appropriately
  3. Configure Cloud Run minimum instances with appropriate cost awareness
  4. Require Cloud Run authentication and grant the invoker permission to the intended principal
  5. Configure a maximum instance cap suited to backend capacity

Explanation

Correct Answer

E:

The cap limits service scale-out and may increase latency or error rates under heavy demand. A concurrency setting affects per-instance load instead.

Incorrect Answers

A:

Using this action would allow serverless scale-to-zero, not bound database connection pressure. Its function is different from the specific change described in the scenario.

B:

This approach can tune concurrent requests per Cloud Run instance. The requirement is to bound database connection pressure, so it controls a different part of the workflow and leaves that result unaddressed.

C:

This setting would keep warm Cloud Run instances. That behavior does not establish the requested ability to bound database connection pressure; it addresses an adjacent concern instead.

D:

This proposal can authorize a service-to-service Cloud Run caller, but the failure or goal described here calls for a way to bound database connection pressure; It changes the wrong control or scope for the requested outcome.

Question 407

A CPU-bound container handles poorly when many requests execute simultaneously on one instance. Which approach should be selected?

  1. Configure a maximum instance cap suited to backend capacity
  2. Set supported Cloud Run ingress restrictions in addition to IAM authentication
  3. Reduce Cloud Run concurrency appropriately
  4. Configure Cloud Run minimum instances with appropriate cost awareness
  5. Use an appropriate Cloud Run minimum instances setting of zero

Explanation

Correct Answer

C:

Request concurrency determines simultaneous request handling per instance. Lower concurrency can scale more instances and reduce per-instance contention at a cost.

Incorrect Answers

A:

While this can limit total Cloud Run instances, the present task requires an action to reduce container-level contention. This operation does not supply the behavior described in the requirements.

B:

An operator would use this action to restrict network ingress to a serverless service, chiefly when trying to keep Cloud Run internal to approved sources; The current requirement is to reduce container-level contention, which remains unresolved by that operation.

D:

This mechanism is intended to keep warm Cloud Run instances. It does not implement the required action to reduce container-level contention, even though both are relevant to the same general service.

E:

The result of this choice would be to allow serverless scale-to-zero. The requested outcome, to reduce container-level contention, is handled at a different layer or through another operation.

Question 408

A Cloud Run service has a generous configured maximum instance cap, yet scaling plateaus during a regional load test; metrics show that the project's regional CPU allocation is exhausted. Which investigation or change is most relevant?

  1. Check regional Cloud Run CPU quota consumption and request an eligible quota increase or reduce per-instance CPU demand
  2. Set minimum instances to the configured maximum and ignore regional capacity limits
  3. Enable Public Access Prevention on the serving project's Cloud Storage buckets
  4. Increase the Cloud Run request timeout and assume the regional CPU quota automatically increases

Explanation

Correct Answer

A:

Effective Cloud Run scale is constrained by regional CPU and memory quotas as well as service-level instance limits. Raising an instance cap alone cannot override exhausted regional capacity.

Incorrect Answers

B:

Minimum instances can reserve warm capacity but do not bypass regional resource quotas. They may worsen allocation pressure rather than resolve it.

C:

Cloud Storage public access prevention is a storage authorization control. It cannot add regional compute CPU capacity to Cloud Run or bypass instance scaling quotas during the load test.

D:

Request timeout controls how long a request may execute, not the project's available regional CPU. The capacity ceiling remains.

Question 409

A backend service must be callable only by an authenticated internal workload. Which implementation matches this requirement?

  1. Update the service configuration to create a new revision
  2. Require Cloud Run authentication and grant the invoker permission to the intended principal
  3. Integrate Secret Manager with supported Cloud Run secret references and IAM
  4. Set supported Cloud Run ingress restrictions in addition to IAM authentication

Explanation

Correct Answer

B:

IAM invocation protects the service from unauthenticated access. Network ingress settings are an additional consideration for internal-only exposure.

Incorrect Answers

A:

While this can update Cloud Run runtime configuration, the present task requires an action to restrict serverless invocation by identity. This operation does not supply the behavior described in the requirements.

C:

Its purpose is to supply managed secrets to Cloud Run. That distinction matters: the scenario calls for an action to restrict serverless invocation by identity, not this separate configuration task.

D:

Administrators use it to restrict network ingress to a serverless service, rather than to restrict serverless invocation by identity. Applying it would change the wrong component of this deployment.

Question 410

A Cloud Run revision needs a database password sourced from a managed secret. What should the administrator do?

  1. Update the service configuration to create a new revision
  2. Require Cloud Run authentication and grant the invoker permission to the intended principal
  3. Set supported Cloud Run ingress restrictions in addition to IAM authentication
  4. Shift Cloud Run traffic allocation back to the healthy prior revision
  5. Integrate Secret Manager with supported Cloud Run secret references and IAM

Explanation

Correct Answer

E:

Secret Manager holds credential versions; Cloud Run can expose authorized secrets as supported environment or volume data. The runtime service identity needs permission to access the secret.

Incorrect Answers

A:

The tool can update Cloud Run runtime configuration, but it cannot be substituted for the capability needed to avoid plaintext serverless credentials. Its operational effect is not equivalent.

B:

It can authorize a service-to-service Cloud Run caller; however, it does not provide the specific operation to avoid plaintext serverless credentials. The two controls serve different purposes.

C:

This mechanism is intended to restrict network ingress to a serverless service. It does not implement the required action to avoid plaintext serverless credentials, even though both are relevant to the same general service.

D:

An operator would use this action to roll back active Cloud Run request routing, chiefly when trying to recover from a bad serverless release; The current requirement is to avoid plaintext serverless credentials, which remains unresolved by that operation.

Associate Cloud Engineer Practice Tests