To support a microservices backend, a devops team is deploying a new Cloud SQL for PostgreSQL database instance. Company governance rules require that the database use Private IP connectivity over an established Private Services Access connection within the VPC, while also maintaining high availability with regional redundancy. Which TWO options correctly specify the required `gcloud sql instances create` flags to meet these requirements?
- Specify `--network=VPC_NAME` together with `--no-assign-ip` to enforce Private IP connectivity without exposing a public IP address.Cevap
- Specify `--availability-type=REGIONAL` to configure primary and standby instances in different zones within the selected region.Cevap
- CSpecify `--authorized-networks=0.0.0.0/0` alongside `--network=VPC_NAME` to allow internal subnet traffic through the public gateway.
- DSpecify `--tier=db-f1-micro` when configuring regional high availability to optimize cost for production database workloads.
Cevap
The correct requirements are to specify `--network=VPC_NAME` with `--no-assign-ip` for private connectivity and `--availability-type=REGIONAL` for high availability.
Provisioning a secure, highly available Cloud SQL instance requires disabling public IP assignment (`--no-assign-ip`) while attaching to a VPC network (`--network`), and setting regional availability (`--availability-type=REGIONAL`) to maintain synchronous replication across zones.
Adım Adım Çözüm
Anahtar Kavram
Provisioning Cloud SQL instances with Private IP connectivity and High Availability using the gcloud CLI