A systems administrator needs to deploy a high-availability Cloud SQL for MySQL database instance that is accessible exclusively using Private IP from an existing Virtual Private Cloud (VPC) network named `internal-vpc`. Which two configurations or procedures must be executed to satisfy these requirements? (Select TWO answers.)
- Create a private services access connection by allocating an IP address range and establishing VPC network peering with Google services inside `internal-vpc`.Cevap
- Provision the Cloud SQL instance using `gcloud sql instances create` with the `--availability-type=REGIONAL`, `--network=internal-vpc`, and `--no-assign-ip` flags.Cevap
- CProvision the Cloud SQL instance using `gcloud sql instances create` with `--availability-type=ZONAL` and specify `--authorized-networks=0.0.0.0/0` to enable internal subnet routing.
- DAssign primitive `roles/owner` permissions to the Cloud SQL default service account and deploy the instance with a public IP address for internal VPC routing.
Cevap
To deploy a high-availability Cloud SQL instance accessible only via Private IP, you must establish a private services access connection (VPC network peering) in `internal-vpc` and create the Cloud SQL instance using the `--availability-type=REGIONAL`, `--network=internal-vpc`, and `--no-assign-ip` flags.
Deploying a high-availability Cloud SQL instance on Private IP requires two key steps: first, establishing a private services access connection (allocating an IP block and peering the VPC), and second, provisioning the database instance with regional availability (`--availability-type=REGIONAL`) linked to the VPC network (`--network`) without a public IP (`--no-assign-ip`).
Adım Adım Çözüm
Anahtar Kavram
Cloud SQL High Availability and Private IP Provisioning