nerdexam
Google

ASSOCIATE-CLOUD-ENGINEER · Question #327

You have two Google Cloud projects: project-a with VPC vpc-a (10.0.0.0/16) and project-b with VPC vpc-b (10.8.0.0/16). Your frontend application resides in vpc-a and the backend API services are deplo

The correct answer is B. Create VPC Network Peering between vpc-a and vpc-b.. VPC Network Peering: This allows private and secure communication between VPCs in different Google Cloud projects without using public IP addresses or VPN connections. It is cost-effective because it only incurs network egress charges within the same region and provides high- ban

Submitted by tom_us· Mar 30, 2026Planning and configuring a cloud solution

Question

You have two Google Cloud projects: project-a with VPC vpc-a (10.0.0.0/16) and project-b with VPC vpc-b (10.8.0.0/16). Your frontend application resides in vpc-a and the backend API services are deployed in vpc-b. You need to efficiently and cost-effectively enable communication between these Google Cloud projects. You also want to follow Google-recommended practices. What should you do?

Options

  • ACreate an OpenVPN connection between vpc-a and vpc-b.
  • BCreate VPC Network Peering between vpc-a and vpc-b.
  • CConfigure a Cloud Router in vpc-a and another Cloud Router in vpc-b.
  • DConfigure a Cloud Interconnect connection between vpc-a and vpc-b.

How the community answered

(36 responses)
  • A
    3% (1)
  • B
    89% (32)
  • C
    6% (2)
  • D
    3% (1)

Explanation

VPC Network Peering: This allows private and secure communication between VPCs in different Google Cloud projects without using public IP addresses or VPN connections. It is cost-effective because it only incurs network egress charges within the same region and provides high- bandwidth, low-latency connectivity.

Topics

#VPC peering#cross-project networking#cost-effective connectivity#VPC

Community Discussion

No community discussion yet for this question.

Full ASSOCIATE-CLOUD-ENGINEER Practice