PROFESSIONAL-CLOUD-DATABASE-ENGINEER · Question #194
You are creating new Cloud SQL for PostgreSQL instances in us-east1 and us-east4. You are assigning private IP addresses to the Cloud SQL instances starting with us-east1 so you can reach the…
The correct answer is C. Configure Private Services Access prior to assigning a private IP to Cloud SQL. To use private IP addresses with Cloud SQL, you must first configure Private Services Access between your VPC network and Google-managed services. This step creates the necessary allocated IP range for Google services and establishes the required peering connection. Without it…
Question
You are creating new Cloud SQL for PostgreSQL instances in us-east1 and us-east4. You are assigning private IP addresses to the Cloud SQL instances starting with us-east1 so you can reach the instance without going through the internet or using external IP addresses. However, you keep getting a “Network association failed” error message. You are using a shared VPC network. What should you do to resolve the issue-
Options
- AUse the Google Cloud console to assign private IP.
- BEnable the for the host and service projects.
- CConfigure Private Services Access prior to assigning a private IP to Cloud SQL.
- DAssign the private IP by using the command.
How the community answered
(45 responses)- A4% (2)
- B16% (7)
- C73% (33)
- D7% (3)
Explanation
To use private IP addresses with Cloud SQL, you must first configure Private Services Access between your VPC network and Google-managed services. This step creates the necessary allocated IP range for Google services and establishes the required peering connection. Without it, assigning a private IP will fail with a "Network association failed" error.
Topics
Community Discussion
No community discussion yet for this question.