Google PCA Practice Question: Managing Implementation and Ensuring Solution and Operations Reliability
Your team runs a stateful analytics workload on a Managed Instance Group (MIG) of Compute Engine VMs. The VMs write intermediate results to local SSD scratch disks. During a recent incident, an autoscaling event terminated VMs and the intermediate data was lost, causing hours of recomputation. You need to change the deployment so that when a VM is terminated by the autoscaler, a shutdown script has enough time to flush the intermediate results to a Cloud Storage bucket before the VM is deleted. What should you do?
⚠ Common exam trap
The trap here is assuming that autoscaler cool-down or scheduling controls how long a terminating VM stays alive, when only the shutdown duration setting actually extends that window.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure the instance template with a shutdown script and set the instance's shutdown duration metadata key to a value that gives the script enough time to flush data.
The shutdown duration metadata key is the supported mechanism to extend the STOPPING state so a shutdown script can finish. Because the MIG creates instances from the instance template, placing the key in the template guarantees that autoscaler-created VMs inherit the behavior. Autoscaler tuning and disk-type changes do not bound the time between the shutdown signal and instance deletion.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Replace the local SSD scratch disks with Persistent Disk volumes and rely on the autoscaler to detach them before deleting the VM.
Why it's wrong here
Persistent Disk volumes can be detached and reattached, but the autoscaler does not automatically detach them during scale-in, nor does it flush application data. Switching disk types changes the storage durability model but does not solve the requirement to give a shutdown script time to persist in-flight results.
- ✗
Enable live migration on the MIG and set the autoscaler to scale in only during off-peak hours.
Why it's wrong here
Live migration applies to maintenance events on sole-tenant or standard instances and does not prevent termination during scale-in. Scheduling scale-in for off-peak hours delays but does not eliminate the data loss, and the shutdown script still would not be guaranteed time to complete before the VM is deleted.
- ✗
Set the MIG autoscaler's scale-in control to a longer cool-down period, and increase the instance template's minimum CPU utilization target.
Why it's wrong here
The autoscaler cool-down period only controls how long the autoscaler waits before making another scaling decision; it does not extend the lifetime of a VM that is already being removed. Increasing the CPU target merely changes when scaling triggers, and neither setting guarantees the shutdown script finishes before the instance is deleted.
- ✓
Configure the instance template with a shutdown script and set the instance's shutdown duration metadata key to a value that gives the script enough time to flush data.
Why this is correct
Compute Engine supports a per-instance shutdown duration, specified through the shutdown-duration metadata key, which extends the time the instance stays in the STOPPING state so a shutdown script can complete. Setting this on the instance template ensures every VM created by the MIG, including autoscaler-created ones, has enough time to flush intermediate results to Cloud Storage.
Go deeper
Related to this question
Learn chapter
Deployment Manager and Infrastructure as Code
Key term
Instance group
An instance group is a collection of virtual machine instances that are managed as a single unit for scaling, load balancing, and lifecycle management in cloud computing.
Key term
Compute Engine
Compute Engine is Google Cloud's Infrastructure-as-a-Service (IaaS) offering that lets you create and run virtual machines on Google's infrastructure.
About these practice questions
Courseiva writes every PCA question from scratch — 807 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Google Cloud exam blueprint
This PCA practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PCA exam.