A cloud engineer is provisioning a production Cloud SQL for PostgreSQL instance named `analytics-db` in the `us-central1` region. The database must be reachable exclusively via Private IP within an existing Virtual Private Cloud network named `corp-vpc`, completely disabling any public IP address exposure. Additionally, the instance must be configured for High Availability (HA) across multiple zones and allow disk storage to automatically scale as data grows. Which `gcloud` command correctly deploys the instance according to these requirements?
- gcloud sql instances create analytics-db --database-version=POSTGRES_15 --tier=db-custom-4-15360 --region=us-central1 --network=corp-vpc --no-assign-ip --availability-type=REGIONAL --storage-auto-increaseCevap
- Bgcloud sql instances create analytics-db --database-version=POSTGRES_15 --tier=db-custom-4-15360 --region=us-central1 --network=corp-vpc --availability-type=REGIONAL --storage-auto-increase
- Cgcloud sql instances create analytics-db --database-version=POSTGRES_15 --tier=db-custom-4-15360 --region=us-central1 --network=corp-vpc --no-assign-ip --availability-type=ZONAL --storage-auto-increase
- Dgcloud sql instances create analytics-db --database-version=POSTGRES_15 --tier=db-custom-4-15360 --region=us-central1 --authorized-networks=0.0.0.0/0 --availability-type=REGIONAL --storage-auto-increase
Cevap
The command including `--network=corp-vpc`, `--no-assign-ip`, `--availability-type=REGIONAL`, and `--storage-auto-increase` is correct.
The correct command combines `--network=corp-vpc` and `--no-assign-ip` to enforce private IP access only while disabling public IP assignment. It also sets `--availability-type=REGIONAL` to enable cross-zone failover (HA) and includes `--storage-auto-increase` to enable dynamic storage capacity expansion.
Adım Adım Çözüm
Anahtar Kavram
Cloud SQL Private IP and HA Deployment via gcloud CLI