Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise runs a suite of business-critical production workloads on Compute Engine virtual machines. The operations team needs to establish a post-deployment maintenance strategy that satisfies the following requirements:
Which configuration should you implement on the Compute Engine instances?
Setting onHostMaintenance to TERMINATE and automaticRestart to false configures Compute Engine instances to shut down permanently whenever host maintenance occurs and to stay offline after any unexpected hardware failure.
onHostMaintenance is set to TERMINATE, Google Cloud shuts down the virtual machine instance rather than performing a live migration during routine infrastructure maintenance.automaticRestart set to false, the instance remains stopped indefinitely after a host failure or maintenance shutdown until an administrator manually issues a start command.TERMINATED state.This configuration would be suitable for batch processing jobs, preemptible workloads, or stateless worker pools where jobs can easily be rescheduled elsewhere and licensing or GPU constraints prevent live migration.
Instances configured with certain hardware attachments (such as specific specialized accelerators) do not support live migration and must use TERMINATE, but general production enterprise workloads should avoid this setting.
In Google Cloud Compute Engine, the instance availability policy determines how virtual machine (VM) instances behave during host events such as planned infrastructure maintenance or unplanned hardware failures. Setting onHostMaintenance to MIGRATE and automaticRestart to true establishes automated resilience and high availability for deployed compute workloads.
onHostMaintenance property to MIGRATE enables Live Migration. When Google performs planned maintenance on physical host hardware, the hypervisor moves running VM instances to an alternative host in the same zone without stopping the guest operating system or dropping network connections.automaticRestart to true ensures that if a physical host experiences an unexpected crash, kernel panic, or hardware failure, Google Cloud automatically restarts the virtual machine on a healthy host without requiring manual operator intervention.
This configuration directly fulfills all operational requirements by leveraging native platform resilience mechanisms. It avoids workload disruption during planned maintenance while ensuring rapid automated recovery after unexpected infrastructure incidents.
This option involves tearing down existing VM instances and deploying new software packages from Cloud Marketplace whenever platform maintenance is scheduled.
The objective was to apply major vendor security patches to a third-party Marketplace appliance that does not support in-place package updates.
Cloud Marketplace updates software package base images over time, but deployed instances do not receive these image updates automatically. However, this is independent of Compute Engine host-level maintenance.
This option enables live migration for planned Google Cloud host maintenance events but disables the automatic restart capability when unexpected crashes or unrecoverable host errors occur.
onHostMaintenance to MIGRATE handles planned host updates smoothly, setting automaticRestart to false leaves the instance offline if the physical host crashes unexpectedly.The organization specifically required manual verification of database integrity or external disk states before allowing any crashed system to restart.
Disabling automaticRestart is rarely recommended for production enterprise applications because automated platform restarts are essential for maintaining uptime SLAs.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated