Google Professional Cloud Network Engineer Question 260
Select 3Google Cloud PlatformYour organization has two VPC networks, VPC-A and VPC-B, connected using VPC Network Peering. You need to configure custom route import/export to allow subnets from VPC-B to access a private service in VPC-A through a specific custom static route. What steps must you perform to ensure the custom route is shared between the VPCs?
- A
Enable custom route export on VPC-A's peering connection.
- B
Enable custom route import on VPC-B's peering connection.
- C
Add the custom static route to VPC-A.
- D
Set the next hop of the custom static route to 'default internet gateway' in VPC-A.
- E
Enable Google Cloud's internal DNS resolution between the two VPCs.
Show answer and explanation
Correct answers: A, B, C
Explanation
To share custom static routes between VPCs using VPC Network Peering, you must enable custom route export on the source VPC's peering connection and custom route import on the receiving VPC's peering connection. Additionally, you need to create the custom static route in the source VPC to define the desired routing behavior. These steps ensure that the custom routes are exchanged and functional between the VPCs.
- A. Correct.
This is correct. Custom route export must be enabled on the source VPC (VPC-A) to share custom static routes with the peer VPC.
- B. Correct.
This is correct. Custom route import must be enabled on the receiving VPC (VPC-B) to allow it to accept custom routes from VPC-A.
- C. Correct.
This is correct. A custom static route must be created in VPC-A to define the specific routing behavior required for the private service.
- D. Incorrect.
This is incorrect. The next hop for the custom static route should be defined according to the private service's network configuration, not the default internet gateway.
- E. Incorrect.
This is incorrect. While internal DNS can help resolve internal services, it is not required for configuring custom route import/export over VPC Network Peering.