Google Professional Cloud Network Engineer Question 160
Single answerGoogle Cloud PlatformYou are tasked with designing the IP address space for a hybrid cloud network connecting two on-premises data centers and a Google Cloud environment. The on-premises data centers use the IP ranges 10.0.0.0/16 and 192.168.1.0/24, respectively. You also need to design a range for a private Google Cloud VPC that avoids conflicts or overlaps with the on-premises networks. Which IP range should you choose for the Google Cloud VPC?
- A
10.0.1.0/24
- B
192.168.2.0/24
- C
172.16.0.0/16
- D
192.168.1.0/25
Show answer and explanation
Correct answer: C
Explanation
When designing IP ranges for hybrid networks, it is crucial to avoid overlapping IP ranges between on-premises and cloud environments. The 172.16.0.0/16 range is part of the private IP space and does not overlap with the on-premises networks (10.0.0.0/16 and 192.168.1.0/24). It is the most suitable choice for the Google Cloud VPC in this scenario. Ensuring no overlap prevents routing issues and maintains a consistent hybrid network setup.
- A. Incorrect.
This range (10.0.1.0/24) overlaps with the existing on-premises 10.0.0.0/16 range, so it is not suitable for the Google Cloud VPC.
- B. Incorrect.
This range (192.168.2.0/24) does not overlap with the current on-premises ranges, but it's part of the private IP range typically used in on-premises networks. While technically valid, it's not ideal for avoiding future conflicts as it could overlap with other on-premises networks in the future.
- C. Correct.
The 172.16.0.0/16 range is part of the private IP address space and does not overlap with either of the on-premises ranges. It is the best choice for the Google Cloud VPC in this scenario.
- D. Incorrect.
This range (192.168.1.0/25) overlaps with the on-premises 192.168.1.0/24 range, so it cannot be used for the Google Cloud VPC.