CLOUD-NETWORK practice question 27 of 30

Your company has separate Virtual Private Cloud (VPC) networks in a single region for two departments: Sales and Finance. The Sales department's VPC…

Full set: 233 questions
Your company has separate Virtual Private Cloud (VPC) networks in a single region for two departments: Sales and Finance. The Sales department's VPC network already has connectivity to on- premises locations using HA VPN, and you have confirmed that the subnet ranges do not overlap. You plan to peer both VPC networks to use the same HA tunnels for on-premises connectivity, while providing internet connectivity for the Google Cloud workloads through Cloud NAT. Internet access from the on-premises locations should not flow through Google Cloud. You need to propagate all routes between the Finance department and on-premises locations. What should you do?
Answer options
A: Peer the two VPCs, and use the default configuration for the Cloud Routers.
B: Peer the two VPCs, and use Cloud Router’s custom route advertisements to announce the peered VPC network ranges to the on-premises locations.
C: Peer the two VPCs. Configure VPC Network Peering to export custom routes from Sales and import custom routes on Finance's VPC network. Use Cloud Router’s custom route advertisements to announce a default route to the on-premises locations.
D: Peer the two VPCs. Configure VPC Network Peering to export custom routes from Sales and import custom routes on Finance's VPC network. Use Cloud Router’s custom route advertisements to announce the peered VPC network ranges to the on-premises locations. Correct answer
Correct Answer:
D. Peer the two VPCs. Configure VPC Network Peering to export custom routes from Sales and import custom routes on Finance's VPC network. Use Cloud Router’s custom route advertisements to announce the peered VPC network ranges to the on-premises locations.
Explanation

To allow the Finance VPC to use the Sales VPC's HA VPN for on-premises connectivity, you must first establish VPC Network Peering. For routes to be exchanged, the peering connection must be configured to export routes from the Finance VPC and import them into the Sales VPC (and vice-versa). By default, a Cloud Router does not advertise subnet routes from peered networks. Therefore, you must create a custom route advertisement on the Cloud Router in the Sales VPC to explicitly announce the Finance VPC's subnet ranges to the on-premises network.

Why Incorrect

A. The default Cloud Router configuration only advertises subnets from its local VPC, not from peered VPCs. This would leave the Finance VPC unreachable from on-premises.
B. This option omits the critical step of configuring the VPC Network Peering connection to exchange custom routes, without which the Sales VPC would not learn the Finance routes to advertise.
C. Advertising a default route to on-premises is incorrect. It would route all internet-bound traffic from Google Cloud to on-premises, conflicting with the Cloud NAT requirement for direct internet egress.

References

1. Google Cloud Documentation

"VPC Network Peering use cases"

Section: "Sharing an on-premises connection with a peer VPC network". It states: "To provide connectivity from on-premises to subnets in peer networks

you must create custom route advertisements on your Cloud Routers... In addition

you must configure the peering connections to export custom routes."

2. Google Cloud Documentation

"VPC Network Peering"

Section: "Exchanging custom routes". It details the necessity of configuring both peering connections to import and export custom routes for full connectivity.

Scroll to Top