An associate cloud engineer needs to deploy a Cloud SQL PostgreSQL instance configured exclusively with a Private IP address in a custom Virtual Private Cloud (VPC) network. Place the necessary configuration steps in the correct chronological order from first to last.
- 1Allocate an IP address range in the VPC network reserved for private service access.
- 2Create a private connection to the Service Networking API using the allocated IP range.
- 3Provision the Cloud SQL instance with the --network flag set and the --no-assign-ip flag enabled.
- 4Create the database users and configure database schemas on the instance.
Answer
The correct deployment sequence is: 1) Allocate an IP address range in the VPC network, 2) Create a private connection to the Service Networking API, 3) Provision the Cloud SQL instance with the private network flags, and 4) Create database users and schemas.
Deploying a Cloud SQL instance with Private IP connectivity requires setting up Private Services Access first. You must first reserve an IP address block in your VPC, then establish a private service connection (VPC peering) to the Service Networking API. After peering is established, you create the Cloud SQL instance attached to that network without a public IP assigned. Finally, once the instance is running, you configure database users and application schemas.
Step-by-Step Solution
Key Concept
Provisioning Cloud SQL with Private IP using Private Services Access
Estimated Time:1m 0s