Google Professional Cloud Network Engineer Question 199
Single answerGoogle Cloud PlatformYour company is designing a hybrid cloud network to connect its on-premises data center to Google Cloud. The on-premises network uses RFC 1918 private IP ranges, and you want to ensure there are no IP conflicts between the on-premises network and the Google Cloud VPC. Additionally, some of your workloads in the cloud require access to the public internet. Which type of IP address configuration is the most appropriate for the Google Cloud VPC subnets to fulfill these requirements?
- A
Use RFC 1918 private IP ranges for Google Cloud VPC subnets that do not overlap with the on-premises network.
- B
Use non-RFC 1918 private IP ranges for Google Cloud VPC subnets.
- C
Use publicly routable IP addresses for all Google Cloud VPC subnets.
- D
Use privately used public IP (PUPI) addresses for Google Cloud VPC subnets.
Show answer and explanation
Correct answer: A
Explanation
When designing a hybrid cloud network, avoiding IP conflicts between the on-premises network and the Google Cloud VPC is critical. Using RFC 1918 ranges for the VPC subnets is the best practice, as these private IP ranges are reserved for internal use and align well with hybrid networking scenarios. Ensuring the ranges do not overlap with the on-premises network avoids conflicts and ensures seamless communication. Non-RFC 1918 ranges, public IPs, or PUPI should only be used in very specific scenarios, with careful consideration of their implications.
- A. Correct.
This is the correct approach. By using RFC 1918 private IP ranges that do not overlap with the on-premises network, you avoid IP conflicts while maintaining a private addressing scheme appropriate for internal communication.
- B. Incorrect.
Non-RFC 1918 private IP ranges are not officially reserved for private use and may conflict with public IP addresses, which could lead to routing issues or unexpected behavior.
- C. Incorrect.
Using publicly routable IP addresses for all subnets is not recommended for security and cost efficiency. Public IPs should only be used for specific workloads that require direct internet access.
- D. Incorrect.
Privately used public IP (PUPI) addresses can create challenges with routing and are generally not recommended unless there is a specific use case that requires them.