Google Associate Cloud EngineerDeploying and implementing a cloud solutionMedium
A company is designing a new microservices architecture on Google Cloud. They need to ensure that application components within different VPCs can communicate securely using internal IP addresses without traversing the public internet. The components are managed by different teams in separate Google Cloud projects. Which networking feature should be used?
- ACloud VPN
- BVPC Network Peering
- CShared VPC
- DCloud Interconnect (Dedicated)
Show answer & explanationAnswer & explanation
Correct answer: B. VPC Network Peering
VPC Network Peering allows two VPC networks to connect, enabling resources in each network to communicate using internal IP addresses as if they were in the same network. This is ideal for connecting microservices across different projects securely without using the public internet.
Why the other options are wrong
- A. Cloud VPN connects VPCs over the public internet, not using internal IP addresses directly.
- C. Shared VPC allows multiple service projects to use a single host project's VPC, but the question implies distinct VPCs requiring inter-VPC communication.
- D. Cloud Interconnect connects on-premises networks to Google Cloud, not two VPCs within Google Cloud.
VPC Network Peering
A networking feature that allows you to connect two Virtual Private Cloud (VPC) networks so that resources in each network can communicate using internal IP addresses.
- Enables private communication between VPCs, even across different projects and organizations.
- Traffic stays within Google's network, not traversing the public internet.
- No single point of failure and no bandwidth bottlenecks.
- Routes are automatically exchanged between peered networks.
Memory trick: Peering is like holding hands between two VPCs, making them feel like one big network.