Google Professional Cloud Network Engineer Question 198
Single answerGoogle Cloud PlatformYour company is designing a hybrid cloud architecture to connect its on-premises data center with Google Cloud. The on-premises network uses RFC 1918 IP addresses in the 192.168.0.0/16 range. The architecture requires connectivity to a Google Cloud VPC without IP address conflicts. Which approach should you take when configuring the IP address ranges for the Google Cloud VPC?
- A
Use a different RFC 1918 range, such as 10.0.0.0/8, for the Google Cloud VPC.
- B
Configure the Google Cloud VPC to use the same 192.168.0.0/16 range as the on-premises network and enable overlapping IP address handling.
- C
Use a publicly routable IP range instead of RFC 1918 addresses for the Google Cloud VPC.
- D
Use privately used public IP (PUPI) addresses for the Google Cloud VPC to avoid conflicts.
Show answer and explanation
Correct answer: A
Explanation
In hybrid cloud architectures, it is critical to avoid IP address conflicts between the on-premises network and the Google Cloud VPC. The best practice is to use a different, non-overlapping RFC 1918 range for the Google Cloud VPC. This ensures smooth connectivity and avoids the complexity of handling overlapping IPs or the risks associated with using publicly routable IPs in private networks.
- A. Correct.
This is the correct option. Using a different RFC 1918 range, such as 10.0.0.0/8, avoids IP address conflicts while adhering to best practices for private addressing.
- B. Incorrect.
This is incorrect. Using the same 192.168.0.0/16 range will result in IP conflicts and is not a recommended practice unless advanced solutions like NAT or overlapping IP handling are implemented, which add complexity.
- C. Incorrect.
This is incorrect. Using publicly routable IP ranges in a private network is not recommended as it can lead to routing issues and potential conflicts with public IPs.
- D. Incorrect.
This is incorrect. While privately used public IP (PUPI) addresses can avoid conflicts, they are not a standard or widely supported approach in hybrid cloud setups compared to using non-overlapping RFC 1918 ranges.