Google Associate Cloud Engineer Practice Test 50
Question 490
A team stores its only uncommitted source changes on an ephemeral workstation disk before resetting the environment. What should they do?
- Grant the minimum workstation-use permission and reserve configuration administration to an authorized platform team.
- Give the attached VM service account project Owner instead of fixing resource configuration.
- Create a snapshot only and assume it immediately changes the live VM capacity.
- Commit or back up approved work to governed persistent source storage before lifecycle recreation.
Explanation
Correct Answer
D:Developer workspace lifecycle actions can discard local changes if durable source artifacts were not preserved.
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: Commit or back up approved work to governed persistent source storage before lifecycle recreation.
B: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: Commit or back up approved work to governed persistent source storage before lifecycle recreation.
C:Snapshots are recovery artifacts and do not directly reconfigure a running resource. The necessary distinction is the actual compute scheduling or resource condition. The appropriate action here is: Commit or back up approved work to governed persistent source storage before lifecycle recreation.
Question 491
A workstation's container image includes an old vulnerable CLI version even though the underlying service is current. What should be updated?
- Roll out or recreate affected workstation instances under the reviewed updated configuration after preserving necessary user data.
- Move the VM to a different billing account and assume its scheduling and storage behavior changes.
- Change the instance display name as a replacement for modifying the actual machine or disk.
- Build and publish a patched workstation image and redeploy the approved configuration under normal review.
Explanation
Correct Answer
D:The management service's patch level does not ensure custom containerized development tools are up to date.
Incorrect Answers
A: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: Build and publish a patched workstation image and redeploy the approved configuration under normal review.
B:Billing changes payment responsibility, not the technical behavior of this workload. The necessary distinction is the actual compute scheduling or resource condition. The appropriate action here is: Build and publish a patched workstation image and redeploy the approved configuration under normal review.
C:Display names and labels identify resources; they do not enforce their runtime behavior. The case instead depends on the actual compute scheduling or resource condition. The appropriate action here is: Build and publish a patched workstation image and redeploy the approved configuration under normal review.
Question 492
A company wants to stop developers from opening workstations outside approved hours, but only sets a VM startup schedule in an unrelated project. What scope should be controlled?
- Use supported workstation idle timeout and startup/shutdown policies reflecting real work patterns.
- Change the instance display name as a replacement for modifying the actual machine or disk.
- Apply the supported workstation access and lifecycle policies to the actual Cloud Workstations resources and principal identities.
- Create a snapshot only and assume it immediately changes the live VM capacity.
Explanation
Correct Answer
C:Control over a separate VM fleet does not govern managed workstation access and activity.
Incorrect Answers
A:Timeouts control waiting time, not the missing platform feature or access right. The necessary distinction is the actual compute scheduling or resource condition.
B:Display names and labels identify resources; they do not enforce their runtime behavior. The case instead depends on the actual compute scheduling or resource condition. The appropriate action here is: Apply the supported workstation access and lifecycle policies to the actual Cloud Workstations resources and principal identities.
D:Snapshots are recovery artifacts and do not directly reconfigure a running resource. It leaves the actual compute scheduling or resource condition unaddressed. The appropriate action here is: Apply the supported workstation access and lifecycle policies to the actual Cloud Workstations resources and principal identities.
Question 493
A Cloud Scheduler HTTP job calls a Cloud Run service that requires authentication. After the scheduler job's caller service account was replaced, every invocation returns 401. What should be updated?
- Configure the Scheduler HTTP target to send a valid OIDC token for the approved caller, check its audience, and grant that caller Cloud Run Invoker.
- Grant the Cloud Run runtime service account extra database read permissions; incoming request identity is always identical to runtime identity.
- Change the Cloud Scheduler job's timezone; timezone controls whether Cloud Run accepts OIDC-signed identities.
- Switch from HTTPS to unauthenticated HTTP so the private Cloud Run policy can no longer reject the request.
Explanation
Correct Answer
A:Configure the Scheduler HTTP target to send a valid OIDC token for the approved caller, check its audience, and grant that caller Cloud Run Invoker. Scheduler can send OIDC identity tokens to authenticated targets. The selected principal and token audience must match Cloud Run's invocation checks.
Incorrect Answers
B:Grant the Cloud Run runtime service account extra database read permissions; incoming request identity is always identical to runtime identity. The service's runtime identity makes outgoing API calls; it does not establish the Scheduler job's permission to invoke the private endpoint.
C:Change the Cloud Scheduler job's timezone; timezone controls whether Cloud Run accepts OIDC-signed identities. Scheduling timezone affects when a job runs, not whether its OIDC token is accepted by Cloud Run.
D:Switch from HTTPS to unauthenticated HTTP so the private Cloud Run policy can no longer reject the request. Removing transport or invocation authentication violates the intended private service requirements and cannot fix the authorized identity binding.
Question 494
A monthly Cloud Scheduler report job fires in UTC rather than the local reporting timezone and misses the agreed cut-off. Which configuration should change?
- Set the supported scheduler timezone and cron schedule and test daylight-saving behavior where relevant.
- Use an approved instance schedule or centrally managed Scheduler-driven automation with least-privilege identity and monitoring.
- Create a snapshot only and assume it immediately changes the live VM capacity.
- Restart the instance repeatedly while leaving the underlying error or missing dependency in place.
Explanation
Correct Answer
A:Cron times are interpreted according to the scheduled timezone, not necessarily the operator's current local time.
Incorrect Answers
B:Monitoring reports symptoms; it does not enact the missing resource configuration. It leaves the actual compute scheduling or resource condition unaddressed.
C:Snapshots are recovery artifacts and do not directly reconfigure a running resource. The specific requirement concerns the actual compute scheduling or resource condition. The appropriate action here is: Set the supported scheduler timezone and cron schedule and test daylight-saving behavior where relevant.
D:The proposed setting does not correct the stated machine, disk or scheduling requirement. The necessary distinction is the actual compute scheduling or resource condition. The appropriate action here is: Set the supported scheduler timezone and cron schedule and test daylight-saving behavior where relevant.
Question 495
A queue worker deployed from Cloud Tasks receives bursts of retries after returning 500 because it commits data before sending the response. What handling should be corrected?
- Set queue rate and maximum concurrent dispatch limits to the partner's documented API capacity.
- Make task processing idempotent and acknowledge successful completed work with a suitable 2xx response.
- Change the instance display name as a replacement for modifying the actual machine or disk.
- Give the attached VM service account project Owner instead of fixing resource configuration.
Explanation
Correct Answer
B:Cloud Tasks retries failed dispatches; side effects that occur before a failed HTTP response may be repeated.
Incorrect Answers
A: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: Make task processing idempotent and acknowledge successful completed work with a suitable 2xx response.
C: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: Make task processing idempotent and acknowledge successful completed work with a suitable 2xx response.
D:Project Owner broadens authorization and is not an appropriate substitute for the named control. The case instead depends on the actual compute scheduling or resource condition. The appropriate action here is: Make task processing idempotent and acknowledge successful completed work with a suitable 2xx response.
Question 496
An operations script is intended to run every day but occasionally skips when the only developer laptop is offline. Which service better hosts the scheduled invocation?
- Configure the Scheduler HTTP target to send a valid OIDC token for the approved caller, check its audience, and grant that caller Cloud Run Invoker.
- Deploy a new revision to all traffic without checking the intended rollout behavior.
- Use Cloud Scheduler triggering a governed Cloud Run job or authenticated service with monitored retries.
- Move the container image to another registry while leaving the failing trigger and permissions untouched.
Explanation
Correct Answer
C:Central managed scheduling is independent of a particular engineer's workstation and provides traceable execution.
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: Use Cloud Scheduler triggering a governed Cloud Run job or authenticated service with monitored retries.
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 Cloud Scheduler triggering a governed Cloud Run job or authenticated service with monitored retries.
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: Use Cloud Scheduler triggering a governed Cloud Run job or authenticated service with monitored retries.
Question 497
A Cloud Tasks queue has an unlimited dispatch rate and exhausts a partner API's quota in seconds. What should be configured?
- Make task processing idempotent and acknowledge successful completed work with a suitable 2xx response.
- Create a snapshot only and assume it immediately changes the live VM capacity.
- Restart the instance repeatedly while leaving the underlying error or missing dependency in place.
- Set queue rate and maximum concurrent dispatch limits to the partner's documented API capacity.
Explanation
Correct Answer
D:Queue dispatch pacing can protect downstream rate limits independently of worker autoscaling policies.
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: Set queue rate and maximum concurrent dispatch limits to the partner's documented API capacity.
B:Snapshots are recovery artifacts and do not directly reconfigure a running resource. It leaves the actual compute scheduling or resource condition unaddressed. The appropriate action here is: Set queue rate and maximum concurrent dispatch limits to the partner's documented API capacity.
C: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: Set queue rate and maximum concurrent dispatch limits to the partner's documented API capacity.
Question 498
A Pub/Sub subscription backlog rises because the pull worker is offline, but the team considers dropping messages immediately. What should be checked first?
- Set queue rate and maximum concurrent dispatch limits to the partner's documented API capacity.
- Give the attached VM service account project Owner instead of fixing resource configuration.
- Inspect subscription retention, oldest unacknowledged age and worker health, then restore consumers within the configured retention window.
- Increase the VM vCPU quota without changing the failed configuration or resource setting.
Explanation
Correct Answer
C:Pub/Sub can retain unacknowledged messages according to configured policy; backlog should be managed without unnecessary data loss.
Incorrect Answers
A:The proposed setting does not correct the stated machine, disk or scheduling requirement. It leaves retention or recoverability controls unaddressed.
B:Project Owner broadens authorization and is not an appropriate substitute for the named control. The specific requirement concerns retention or recoverability controls.
D:More CPU quota affects capacity, not the API or policy decision described. The necessary distinction is retention or recoverability controls.
Question 499
A Cloud Scheduler job sometimes invokes the same HTTP handler twice after network timeouts, and the handler sends duplicate notifications. What safeguard is necessary?
- Keep synchronous calls within supported request limits and move prolonged report work to a job or asynchronous workflow.
- Change the instance display name as a replacement for modifying the actual machine or disk.
- Create a snapshot only and assume it immediately changes the live VM capacity.
- Use a request-level idempotency key or stored execution marker and ensure duplicate invocations are safe.
Explanation
Correct Answer
D:Scheduler at-least-once delivery patterns require job handlers to tolerate retries and duplicate attempts.
Incorrect Answers
A: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: Use a request-level idempotency key or stored execution marker and ensure duplicate invocations are safe.
B: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: Use a request-level idempotency key or stored execution marker and ensure duplicate invocations are safe.
C:Snapshots are recovery artifacts and do not directly reconfigure a running resource. The case instead depends on the actual compute scheduling or resource condition. The appropriate action here is: Use a request-level idempotency key or stored execution marker and ensure duplicate invocations are safe.
Question 500
A Cloud Run job handles a weekly data export but reports success even though one parallel task failed. What should be evaluated?
- Create a Cloud Run job for finite background processing with appropriate task timeout and retries.
- Delete the working revision before confirming that the replacement can serve requests.
- Change only the Cloud Run maximum instance count and assume all other service configuration follows.
- Inspect per-task statuses, retry limits and aggregate job completion criteria rather than relying on a single container log line.
Explanation
Correct Answer
D:Cloud Run jobs can run multiple tasks; operational success requires every required task to satisfy the job's completion policy.
Incorrect Answers
A:Timeouts control waiting time, not the missing platform feature or access right. The necessary distinction is the Cloud Run service setting.
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: Inspect per-task statuses, retry limits and aggregate job completion criteria rather than relying on a single container log line.
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: Inspect per-task statuses, retry limits and aggregate job completion criteria rather than relying on a single container log line.