A Cloud Operations engineer needs to provision a Compute Engine virtual machine instance named `data-processor-vm` in zone `us-central1-a`. The virtual machine requires an automated initial startup script stored in a Cloud Storage bucket at `gs://company-bootstrap-scripts/init-processor.sh` to execute upon system boot. Which `gcloud compute` command correctly configures the instance to use this remote script?
- gcloud compute instances create data-processor-vm --zone=us-central1-a --metadata=startup-script-url=gs://company-bootstrap-scripts/init-processor.shCevap
- Bgcloud compute instances create data-processor-vm --zone=us-central1-a --startup-script-url=gs://company-bootstrap-scripts/init-processor.sh
- Cgcloud compute instances create data-processor-vm --zone=us-central1-a --metadata-from-file=startup-script-url=gs://company-bootstrap-scripts/init-processor.sh
- Dgcloud compute instances create data-processor-vm --zone=us-central1-a --scopes=startup-script-url=gs://company-bootstrap-scripts/init-processor.sh
Cevap
The command using `--metadata=startup-script-url=gs://company-bootstrap-scripts/init-processor.sh` is the correct approach.
The correct command uses `--metadata=startup-script-url=gs://company-bootstrap-scripts/init-processor.sh`. Compute Engine retrieves and runs startup scripts hosted in Cloud Storage when the `startup-script-url` key is passed within the standard `--metadata` flag.
Adım Adım Çözüm
Anahtar Kavram
Configuring Compute Engine Startup Scripts via Cloud Storage Metadata