A database engineer is deploying a Cloud Spanner instance named `prod-spanner-db` to support a high-throughput transactional service. The workload requires sub-node scaling, specifically 300 processing units of compute capacity, hosted in the `us-east1` region. Which `gcloud` command correctly provisions this Cloud Spanner instance according to Google Cloud best practices?
- gcloud spanner instances create prod-spanner-db --config=regional-us-east1 --description="Production DB" --processing-units=300Answer
- Bgcloud spanner instances create prod-spanner-db --config=regional-us-east1 --description="Production DB" --nodes=0.3
- Cgcloud spanner instances create prod-spanner-db --config=regional-us-east1 --description="Production DB" --nodes=300
- Dgcloud sql instances create prod-spanner-db --tier=db-custom-2-3750 --region=us-east1 --database-version=SPANNER
Answer
The command `gcloud spanner instances create prod-spanner-db --config=regional-us-east1 --description="Production DB" --processing-units=300` correctly provisions the instance.
The correct option executes `gcloud spanner instances create` specifying `--processing-units=300`. In Google Cloud Spanner, compute capacity below 1 full node (1,000 processing units) is configured using the `--processing-units` flag in increments of 100.
Step-by-Step Solution
Key Concept
Cloud Spanner Instance Provisioning and Processing Unit Scaling via gcloud CLI
Estimated Time:2m 0s