A cloud systems engineer is deploying a non-fault-tolerant telemetry processing application onto a Google Compute Engine VM named `telemetry-node-01` in the `europe-west3-a` zone. The VM requires a dedicated user-managed service account `[email protected]` for identity authorization, must attach an existing persistent disk named `log-archive-disk` in read-only mode to prevent data corruption, and must not be assigned a public external IP address. Which `gcloud` command correctly provisions this Compute Engine virtual machine instance according to these requirements?
- gcloud compute instances create telemetry-node-01 --zone=europe-west3-a [email protected] --no-address --disk=name=log-archive-disk,mode=roAnswer
- Bgcloud compute instances create telemetry-node-01 --zone=europe-west3-a [email protected] --no-address --disk=name=log-archive-disk,mode=ro
- Cgcloud compute instances create telemetry-node-01 --zone=europe-west3-a [email protected] --no-external-ip --provisioning-model=SPOT --disk=name=log-archive-disk,mode=ro
- Dgcloud compute instances create telemetry-node-01 --zone=europe-west3-a --scopes=cloud-platform --no-address --disk=name=log-archive-disk,mode=ro
Answer
The correct command is `gcloud compute instances create telemetry-node-01 --zone=europe-west3-a [email protected] --no-address --disk=name=log-archive-disk,mode=ro`.
The command correctly uses `--service-account` to assign the user-managed service account identity, `--no-address` to omit an external IP address, and `--disk=name=log-archive-disk,mode=ro` to attach the existing persistent disk in read-only mode while maintaining standard provisioning for a non-fault-tolerant process.
Step-by-Step Solution
Key Concept
Provisioning Compute Engine instances using gcloud CLI with custom service accounts, private networking, and attached persistent disks