Google Professional Cloud Network Engineer Question 88
Single answerGoogle Cloud PlatformYour organization is using a private IP range (10.0.0.0/16) in its on-premises network and has migrated several applications to Google Cloud. One of the applications uses Cloud SQL, a managed database service. You notice that there are connectivity issues between the on-premises network and Cloud SQL. What is the most likely reason for this issue, and how can you resolve it?
- A
The private IP range 10.0.0.0/16 conflicts with Google Cloud's default VPC address range. Configure a custom VPC with non-overlapping IP ranges.
- B
Cloud SQL does not support private IPs for connectivity. Use a public IP to connect to Cloud SQL.
- C
The private IP range 10.0.0.0/16 is overlapping with the IP range used by the Cloud SQL private IP. Use a different non-overlapping range for the on-premises network.
- D
Cloud SQL requires a VPN or Interconnect to communicate with on-premises networks. Set up a VPN or Interconnect between your on-premises network and Google Cloud.
Show answer and explanation
Correct answer: C
Explanation
Cloud SQL allows private IP connectivity, but it uses a specific CIDR range for its private IP addresses. If this range overlaps with the on-premises network range (in this case, 10.0.0.0/16), it can cause routing and connectivity issues. To resolve this, you need to ensure that the IP ranges do not overlap by either modifying the on-premises range or choosing a different range for Cloud SQL's private IP.
- A. Incorrect.
This is incorrect. While overlapping IP ranges can cause issues, the conflict is not with the default VPC range but rather with Cloud SQL's private IP range.
- B. Incorrect.
This is incorrect. Cloud SQL does support private IPs for connectivity, and using a public IP is not recommended for secure, private communication.
- C. Correct.
This is correct. Cloud SQL private IPs are assigned from a specific IP range that may conflict with the on-premises network range if they overlap. Modifying the on-premises network range or using a different IP range for Cloud SQL resolves the issue.
- D. Incorrect.
This is incorrect. A VPN or Interconnect is required for private connectivity between on-premises and Google Cloud, but the issue in this scenario is overlapping IP ranges, not the lack of a VPN or Interconnect.