Google Professional Cloud Network Engineer Question 71
Single answerGoogle Cloud PlatformYour company has two VPC networks in Google Cloud, 'VPC-A' and 'VPC-B', located in the same region. The networks need to communicate with each other to share an internal database service hosted in 'VPC-B'. You want to minimize latency, avoid depending on an external IP address, and ensure that the connection is private. In the future, you may need to extend the architecture to support connections from on-premises workloads. Which solution should you choose?
- A
VPC Network Peering between VPC-A and VPC-B
- B
Private Service Connect between VPC-A and VPC-B
- C
Cloud VPN between VPC-A and VPC-B
- D
VPC Network Peering with Network Connectivity Center
Show answer and explanation
Correct answer: A
Explanation
In this scenario, VPC Network Peering is the correct solution because it provides a direct, private, and low-latency connection between two VPC networks in the same region. It avoids the need for external IPs and meets the requirement for private communication. While other options like Private Service Connect and Network Connectivity Center might be applicable in different use cases, they are not optimal for the direct VPC-to-VPC communication described in this scenario.
- A. Correct.
VPC Network Peering allows private, low-latency, and high-bandwidth communication directly between two VPC networks. It is the ideal solution for the scenario described, where the networks are in the same region and need to communicate privately, without external IPs.
- B. Incorrect.
Private Service Connect is used to connect to managed Google services or to expose services privately within a VPC. It is not applicable when you need direct VPC-to-VPC connectivity.
- C. Incorrect.
Cloud VPN is used for securely connecting on-premises networks to Google Cloud or for hybrid solutions. It is not the best choice for connecting two VPC networks within Google Cloud, especially when low latency is required.
- D. Incorrect.
VPC Network Peering with Network Connectivity Center is suited for complex, hybrid, or large-scale multi-VPC architectures. However, it introduces additional overhead and complexity that is unnecessary for simple VPC-to-VPC communication within the same region.