Google Associate Cloud Engineer Practice Test 46
Question 450
A GKE cluster's control plane is reachable publicly despite a requirement that administrator access use authorized network boundaries. What should be configured?
- Validate controller compatibility against the supported Kubernetes release channel and pin a supported controller version before changes.
- Disable the cluster health checks and treat missing readiness as a successful deployment.
- Grant the GKE node service account project Owner to bypass the workload-specific issue.
- Set an approved control-plane authorized-network or private endpoint access path under the supported GKE networking mode.
Explanation
Correct Answer
D:Kubernetes API access needs its own network and IAM protection; private workload subnets alone do not secure the control-plane endpoint.
Incorrect Answers
A:This changes a neighboring Kubernetes feature, not the stated control. It leaves the Kubernetes workload or scheduling control unaddressed.
B:Deploying a separate workload does not automatically configure the existing feature. The specific requirement concerns the Kubernetes workload or scheduling control. The appropriate action here is: Set an approved control-plane authorized-network or private endpoint access path under the supported GKE networking mode.
C:Project Owner broadens authorization and is not an appropriate substitute for the named control. The necessary distinction is the Kubernetes workload or scheduling control.
Question 451
A team wants to deploy a GKE workload but its artifact was published to a different registry project that allows only its original build service account. How should pull access be granted?
- Grant read access to the appropriate GKE image-pull identity at the target Artifact Registry repository and validate repository path.
- Inspect previous container logs, termination reason, startup command and readiness/liveness probe configurations.
- Grant the GKE node service account project Owner to bypass the workload-specific issue.
- Move all Pods to the default namespace and assume this repairs scheduling and authorization.
Explanation
Correct Answer
A:Artifact Registry IAM applies to repository consumers; a successful CI push in one project does not authorize cluster pulls in another.
Incorrect Answers
B:This changes a neighboring Kubernetes feature, not the stated control. The specific requirement concerns the correct runtime principal and its bindings.
C:Project Owner broadens authorization and is not an appropriate substitute for the named control. The necessary distinction is the correct runtime principal and its bindings.
D:Changing an unrelated Pod setting leaves the stated cloud feature unresolved. The case instead depends on the correct runtime principal and its bindings.
Question 452
A Kubernetes CronJob repeatedly starts overlapping expensive report jobs because one run often takes longer than the interval. What should be set?
- Use Kubernetes Job TTL-after-finished or a governed cleanup policy for completed work and associated Pods.
- Use a public LoadBalancer Service for an internal-only issue instead of fixing its actual boundary.
- Change only the container image tag and assume a networking or policy failure is repaired.
- Choose an appropriate CronJob concurrencyPolicy and starting deadline behavior for the workload's expected duration.
Explanation
Correct Answer
D:CronJob schedule intervals do not serialize active jobs unless concurrency policy and missed-run handling are configured.
Incorrect Answers
A:Changing an unrelated Pod setting leaves the stated cloud feature unresolved. The necessary distinction is the Kubernetes workload or scheduling control. The appropriate action here is: Choose an appropriate CronJob concurrencyPolicy and starting deadline behavior for the workload's expected duration.
B:This changes a neighboring Kubernetes feature, not the stated control. The case instead depends on the Kubernetes workload or scheduling control. The appropriate action here is: Choose an appropriate CronJob concurrencyPolicy and starting deadline behavior for the workload's expected duration.
C:Network settings and service or application controls must be distinguished. It leaves the Kubernetes workload or scheduling control unaddressed. The appropriate action here is: Choose an appropriate CronJob concurrencyPolicy and starting deadline behavior for the workload's expected duration.
Question 453
An Autopilot workload requests hostPath access to arbitrary system directories and gets denied by admission. What architectural decision is appropriate?
- Align the workload's node affinity or selector with actual supported node labels and eligible capacity.
- Remove privileged host filesystem dependencies or use a supported Standard cluster design when such host access is essential and approved.
- Move the VM to a different billing account and assume its scheduling and storage behavior changes.
- Give the attached VM service account project Owner instead of fixing resource configuration.
Explanation
Correct Answer
B:Autopilot enforces managed workload restrictions; arbitrary node-level host access is not a portable workload assumption.
Incorrect Answers
A:The proposed setting does not correct the stated machine, disk or scheduling requirement. The case instead depends on the actual compute scheduling or resource condition. The appropriate action here is: Remove privileged host filesystem dependencies or use a supported Standard cluster design when such host access is essential and approved.
C:Billing changes payment responsibility, not the technical behavior of this workload. It leaves the actual compute scheduling or resource condition unaddressed. The appropriate action here is: Remove privileged host filesystem dependencies or use a supported Standard cluster design when such host access is essential and approved.
D:Project Owner broadens authorization and is not an appropriate substitute for the named control. The specific requirement concerns the actual compute scheduling or resource condition. The appropriate action here is: Remove privileged host filesystem dependencies or use a supported Standard cluster design when such host access is essential and approved.
Question 454
A Kubernetes Pod has adequate resources but remains Pending because all eligible nodes are in an unrelated topology zone constrained by required pod anti-affinity. What can be adjusted?
- Remove overbroad tolerations and apply the intended taint, namespace and workload scheduling policy separation.
- Grant the GKE node service account project Owner to bypass the workload-specific issue.
- Revise hard anti-affinity or provide eligible zonal capacity while retaining genuine availability separation goals.
- Increase the Kubernetes Service port without changing the failing Pod or cluster configuration.
Explanation
Correct Answer
C:Required pod affinity/anti-affinity rules can block scheduling when their topology domain conditions cannot be satisfied.
Incorrect Answers
A:This changes a neighboring Kubernetes feature, not the stated control. It leaves the Kubernetes workload or scheduling control unaddressed. The appropriate action here is: Revise hard anti-affinity or provide eligible zonal capacity while retaining genuine availability separation goals.
B:Project Owner broadens authorization and is not an appropriate substitute for the named control. The specific requirement concerns the Kubernetes workload or scheduling control. The appropriate action here is: Revise hard anti-affinity or provide eligible zonal capacity while retaining genuine availability separation goals.
D:A Kubernetes Service port does not change a Pod’s scheduling, image or identity. The necessary distinction is the Kubernetes workload or scheduling control. The appropriate action here is: Revise hard anti-affinity or provide eligible zonal capacity while retaining genuine availability separation goals.
Question 455
A Cloud Run service's new revision fails to receive traffic after deployment because the engineer set no-traffic and forgot the later promotion. How should it be promoted?
- Evaluate service-level versus revision-level minimum instance settings and apply a supported warm-capacity policy to active serving revisions.
- Verify readiness and explicitly update the revision's approved traffic percentage through the service traffic configuration.
- Increase Cloud Run memory alone while leaving the failing routing, identity or event setting unchanged.
- Move the container image to another registry while leaving the failing trigger and permissions untouched.
Explanation
Correct Answer
B:Cloud Run revisions can be deployed without traffic; a healthy new revision is not automatically the active serving destination.
Incorrect Answers
A: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: Verify readiness and explicitly update the revision's approved traffic percentage through the service traffic configuration.
C:Memory sizing may change capacity but cannot replace the specified platform feature. The necessary distinction is the Cloud Run service setting. The appropriate action here is: Verify readiness and explicitly update the revision's approved traffic percentage through the service traffic configuration.
D:The change does not configure the Cloud Run runtime or traffic behavior at issue. The case instead depends on the Cloud Run service setting.
Question 456
Cloud Run revision B is receiving 100% of customer requests and generating new 5xx responses. Revision A is a previously tested healthy version and can still serve traffic. Which immediate recovery action fits?
- Delete the entire Cloud Run service and recreate it from the first container image, losing the existing release history.
- Increase the revision B request timeout only; timeouts automatically correct every application exception and 5xx response.
- Shift production traffic to the verified healthy revision A using Cloud Run traffic controls, while recording incident evidence.
- Grant allUsers project Owner to make revision B requests bypass application errors.
Explanation
Correct Answer
C:Shift production traffic to the verified healthy revision A using Cloud Run traffic controls, while recording incident evidence. Cloud Run supports routing traffic between immutable revisions and rollback to a healthy revision. Its current health and dependencies should be checked.
Incorrect Answers
A:Delete the entire Cloud Run service and recreate it from the first container image, losing the existing release history. Deleting the service discards a useful rollback target and adds avoidable deployment risk to an incident that can be mitigated through traffic routing.
B:Increase the revision B request timeout only; timeouts automatically correct every application exception and 5xx response. A request timeout is only relevant to timeout-related failures. It cannot guarantee recovery from a defective revision's code or dependencies.
D:Grant allUsers project Owner to make revision B requests bypass application errors. IAM escalation does not repair application exceptions; broad public ownership would create a serious security exposure.
Question 457
A team sets a Cloud Run concurrency limit of one for an I/O-bound service and observes costly unnecessary instance scale-out. What should it test?
- Set an appropriate Cloud Run maximum instance limit, at or below the database connection budget divided by the worst-case connections per instance.
- Load-test a suitable higher concurrency setting against latency, memory and CPU limits before controlled rollout.
- Switch the service to public unauthenticated ingress as a workaround for the stated requirement.
- Change only the Cloud Run maximum instance count and assume all other service configuration follows.
Explanation
Correct Answer
B:Cloud Run concurrency affects request density per instance and must be tuned for the application's actual work characteristics.
Incorrect Answers
A:The change does not configure the Cloud Run runtime or traffic behavior at issue. The case instead depends on the requested latency measurement.
C:The change does not configure the Cloud Run runtime or traffic behavior at issue. It leaves the requested latency measurement unaddressed.
D:The change does not configure the Cloud Run runtime or traffic behavior at issue. The specific requirement concerns the requested latency measurement.
Question 458
A Cloud Run service sets minimum instances on revision A, but an upgrade routes all traffic to revision B and unexpectedly loses warm capacity. What scope must operators review?
- Verify readiness and explicitly update the revision's approved traffic percentage through the service traffic configuration.
- Move the container image to another registry while leaving the failing trigger and permissions untouched.
- Switch the service to public unauthenticated ingress as a workaround for the stated requirement.
- Evaluate service-level versus revision-level minimum instance settings and apply a supported warm-capacity policy to active serving revisions.
Explanation
Correct Answer
D:Revision-scoped minimum instances do not automatically transfer to newly promoted revisions; service traffic changes can alter warm capacity.
Incorrect Answers
A: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: Evaluate service-level versus revision-level minimum instance settings and apply a supported warm-capacity policy to active serving revisions.
B: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: Evaluate service-level versus revision-level minimum instance settings and apply a supported warm-capacity policy to active serving revisions.
C: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: Evaluate service-level versus revision-level minimum instance settings and apply a supported warm-capacity policy to active serving revisions.
Question 459
During a large request burst, Cloud Run scales from 3 to 80 instances. Each instance opens at most five Cloud SQL connections, but the database supports only 200 concurrent connections for this service. Which Cloud Run capacity setting protects that limit?
- Increase the service maximum instance count above 80 to distribute traffic across more connections.
- Raise the number of database connections per instance above five without changing the instance ceiling.
- Set an appropriate Cloud Run maximum instance limit, at or below the database connection budget divided by the worst-case connections per instance.
- Increase the minimum instance count to 80 so instances stay warm even when traffic disappears.
Explanation
Correct Answer
C:Set an appropriate Cloud Run maximum instance limit, at or below the database connection budget divided by the worst-case connections per instance. The stated worst case is five connections for each running instance. A cap of 40 instances or fewer keeps the modeled pool total at 200 or below, subject to reserving capacity for other database consumers.
Incorrect Answers
A:Increase the service maximum instance count above 80 to distribute traffic across more connections. More instances at the same per-instance connection cap can raise the aggregate number of open database sessions, aggravating the constraint.
B:Raise the number of database connections per instance above five without changing the instance ceiling. Increasing per-instance connections reduces the number of instances the database can safely serve, so the existing burst could exhaust connections sooner.
D:Increase the minimum instance count to 80 so instances stay warm even when traffic disappears. A high minimum holds additional instances open even off peak; it does not cap maximum scale or preserve the database connection budget.
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?
- Shift production traffic to the verified healthy revision A using Cloud Run traffic controls, while recording incident evidence.
- Change only the Cloud Run maximum instance count and assume all other service configuration follows.
- Increase Cloud Run memory alone while leaving the failing routing, identity or event setting unchanged.
- 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.