Google Professional Cloud Network Engineer Question 261
Select 2Google Cloud PlatformYour company has two VPC networks, 'VPC-A' and 'VPC-B', connected via VPC Network Peering. VPC-A contains custom routes to an on-premises environment via a VPN tunnel. You need to allow VPC-B to access the on-premises environment through these custom routes. How should you configure the VPC Network Peering settings to meet the requirement?
- A
Enable 'Export custom routes' on VPC-A's peering connection.
- B
Enable 'Import custom routes' on VPC-B's peering connection.
- C
Enable 'Export subnet routes with public IP' on VPC-A's peering connection.
- D
Enable 'Import subnet routes with public IP' on VPC-B's peering connection.
- E
Add a route in VPC-B pointing to the on-premises environment using VPC-A's gateway as the next hop.
Show answer and explanation
Correct answers: A, B
Explanation
VPC Network Peering supports the sharing of custom routes between peered VPC networks. To allow VPC-B to access the on-premises environment through the routes in VPC-A, you must enable 'Export custom routes' on VPC-A to share its custom routes and 'Import custom routes' on VPC-B to receive and use those routes. Without these settings, VPC-B will not know about the custom routes to the on-premises environment.
- A. Correct.
Correct. Enabling 'Export custom routes' on VPC-A allows VPC-A to share its custom routes (in this case, the routes to the on-premises environment) with VPC-B through the peering connection.
- B. Correct.
Correct. Enabling 'Import custom routes' on VPC-B allows VPC-B to receive and utilize the custom routes exported by VPC-A.
- C. Incorrect.
Incorrect. 'Export subnet routes with public IP' is not relevant to this scenario as it pertains to subnet routes with public IP addresses, not custom routes.
- D. Incorrect.
Incorrect. 'Import subnet routes with public IP' is not relevant to this scenario as it pertains to subnet routes with public IP addresses, not custom routes.
- E. Incorrect.
Incorrect. Adding a route in VPC-B pointing to the on-premises environment is not possible because VPC-B cannot directly reference VPC-A's gateway. The correct approach is to use route import/export via peering.