A DevOps engineer is deploying a specialized compute workload on Google Cloud attached to GPU hardware accelerators. Compute Engine GPU instances do not support live migration. The application configuration requires that if host maintenance occurs, the instance must terminate instead of migrating, and it should not restart automatically if the host experiences an unexpected outage. Which flags must be passed to the `gcloud compute instances create` command to configure this availability behavior correctly?
- --on-host-maintenance=TERMINATE --no-automatic-restartCevap
- B--maintenance-policy=TERMINATE --restart-on-failure=false
- C--provisioning-model=SPOT --on-host-maintenance=MIGRATE
- D--on-host-maintenance=MIGRATE --automatic-restart
Cevap
The correct option sets `--on-host-maintenance=TERMINATE` and `--no-automatic-restart`.
Compute Engine instances attached to GPU accelerators cannot undergo live migration. Consequently, their host maintenance policy must be set to `TERMINATE` via `--on-host-maintenance=TERMINATE`. To ensure the VM does not automatically reboot following a host disruption, `--no-automatic-restart` must be specified.
Adım Adım Çözüm
Anahtar Kavram
Compute Engine Availability Policies and GPU Instance Maintenance Configuration