Google Professional Cloud Network Engineer Question 262
Select 2Google Cloud PlatformYou are managing two VPC networks, VPC-A and VPC-B, that are connected via VPC Network Peering. VPC-A has several custom static routes configured for routing traffic to on-premises resources through a Cloud VPN tunnel. These routes need to be shared with VPC-B to ensure that traffic from VPC-B to the on-premises resources is routed correctly. How can you achieve this while maintaining minimal changes to the existing configuration?
- A
Enable custom route import on VPC-A's peering connection.
- B
Enable custom route export on VPC-A's peering connection.
- C
Enable custom route import on VPC-B's peering connection.
- D
Enable custom route export on VPC-B's peering connection.
- E
Update the static routes in VPC-A to include VPC-B as a next hop.
Show answer and explanation
Correct answers: B, C
Explanation
To share static routes from one VPC to another over VPC Network Peering, custom route export must be enabled on the source VPC (VPC-A in this case) and custom route import must be enabled on the destination VPC (VPC-B). This allows the custom static routes from VPC-A to propagate to VPC-B via the peering connection. No changes to the existing static routes or next hops are required.
- A. Incorrect.
Incorrect. Enabling custom route import on VPC-A’s peering connection will not allow VPC-A’s custom routes to be shared with VPC-B. Route import only allows a VPC to receive routes from its peered network.
- B. Correct.
Correct. Enabling custom route export on VPC-A’s peering connection ensures that VPC-A’s custom static routes are shared with VPC-B.
- C. Correct.
Correct. Enabling custom route import on VPC-B’s peering connection allows VPC-B to receive the custom static routes exported by VPC-A.
- D. Incorrect.
Incorrect. Enabling custom route export on VPC-B’s peering connection is unnecessary because VPC-B does not need to export routes in this scenario.
- E. Incorrect.
Incorrect. Updating the static routes in VPC-A to include VPC-B as a next hop is not valid or supported. Routes in a VPC cannot specify another VPC as a next hop.