Soru

Zorluk: KolayDeploying and Configuring Managed Database Instances

A Cloud Engineer needs to deploy a Cloud SQL for PostgreSQL instance with Private IP connectivity in an existing Virtual Private Cloud (VPC) network. Place the required steps in the correct chronological order from first to last.

  1. 1Allocate an IP address range in the VPC network for private services access.
  2. 2Establish a private connection between the VPC network and Google Service Networking.
  3. 3Create the Cloud SQL instance specifying the VPC network and disabling public IP.

Cevap

The correct order of deployment steps is: 1) Allocate an IP address range in the VPC network for private services access, 2) Establish a private connection between the VPC network and Google Service Networking, 3) Create the Cloud SQL instance specifying the VPC network and disabling public IP.
Configuring Cloud SQL for private access requires preparing network infrastructure prior to instance creation. First, an IP allocation is reserved for Google services. Next, a private service connection (VPC Peering) is created between the user VPC and Google Service Networking. Finally, the Cloud SQL instance is provisioned specifying the target VPC network.

Adım Adım Çözüm

1
Allocate IP address range
A named IP range is reserved within the target VPC network.
Google Cloud SQL Private IP requires a allocated IP CIDR block dedicated to Service Networking.
2
Create Private Connection (VPC Peering)
The VPC network is peered with Google Service Networking.
Cloud SQL instances run in a tenant VPC managed by Google, which must be connected to the user VPC via Private Services Access.
3
Provision Cloud SQL instance
Cloud SQL instance is deployed with a private IP address.
With the private connection configured, the database instance can be launched using the gcloud sql instances create command with the --network flag.

Anahtar Kavram

Deploying Cloud SQL with Private IP using Private Services Access and VPC Peering
Bu soruyu puanla