Google Professional Cloud Network Engineer Question 87
Single answerGoogle Cloud PlatformYour company is deploying a managed service in Google Cloud that requires connectivity to on-premises resources. The on-premises network uses the 10.0.0.0/8 IP address range. During the deployment, you notice that the managed service is using IP addresses from the 10.0.0.0/8 range, which causes conflicts. How can you resolve the IP overlap issue while ensuring the managed service can still communicate with the on-premises network?
- A
Configure Private Service Connect to assign a custom IP address range for the managed service.
- B
Use a different managed service that does not require IP addresses in the 10.0.0.0/8 range.
- C
Set up VPC peering and use route priority to avoid IP conflicts.
- D
Use a different subnet in the same VPC for the managed service to isolate it from conflicting IP ranges.
Show answer and explanation
Correct answer: A
Explanation
When using managed services in Google Cloud, IP address conflicts with on-premises networks can occur if overlapping IP ranges are used. Private Service Connect allows you to define a custom IP address range for the managed service, avoiding conflicts and maintaining seamless connectivity between the on-premises network and the managed service.
- A. Correct.
This is the correct solution. Private Service Connect allows you to assign a custom IP address range for managed services, resolving the IP conflict while maintaining connectivity.
- B. Incorrect.
This is incorrect because switching to a different managed service may not address the fundamental issue of IP overlap, and it may not be feasible depending on the use case.
- C. Incorrect.
This is incorrect because VPC peering does not resolve IP address conflicts. It requires non-overlapping IP ranges to function.
- D. Incorrect.
This is incorrect because using a different subnet in the same VPC does not resolve conflicts with the 10.0.0.0/8 range used by the on-premises network.