Google
PROFESSIONAL-CLOUD-ARCHITECT · Question #268
Your company and one of its partners each have a Google Cloud project in separate organizations. Your company's project (prj-a) runs in Virtual Private Cloud (vpc-a). The partner's project (prj-b) run
The correct answer is A. Set up a network peering between vpc-a and vpc-b. https://cloud.google.com/vpc/docs/vpc-peering Google Cloud VPC Network Peering allows internal IP address connectivity across two Virtual Private Cloud (VPC) networks regardless of whether they belong to the same project or the same
Submitted by amina.ke· Mar 30, 2026Designing and planning a cloud solution architecture
Question
Your company and one of its partners each have a Google Cloud project in separate organizations. Your company's project (prj-a) runs in Virtual Private Cloud (vpc-a). The partner's project (prj-b) runs in vpc-b. There are two instances running on vpc-a and one instance running on vpc-b. Subnets defined in both VPCs are not overlapping. You need to ensure that all instances communicate with each other via internal IPs, minimizing latency and maximizing throughput. What should you do?
Options
- ASet up a network peering between vpc-a and vpc-b
- BSet up a VPN between vpc-a and vpc-b using Cloud VPN
- CConfigure IAP TCP forwarding on the instance in vpc-b, and then launch the following gcloud
- D
- Create an additional instance in vpc-a.
How the community answered
(16 responses)- A81% (13)
- B6% (1)
- D13% (2)
Explanation
https://cloud.google.com/vpc/docs/vpc-peering Google Cloud VPC Network Peering allows internal IP address connectivity across two Virtual Private Cloud (VPC) networks regardless of whether they belong to the same project or the same
Topics
#VPC peering#cross-organization networking#internal IPs#network latency
Community Discussion
No community discussion yet for this question.