Exam Professional Cloud Network Engineer topic 1 question 56 discussion

The answer is D. https://cloud.google.com/network-connectivity/docs/interconnect/concepts/partner-overview For Layer 3 connections, your service provider establishes a BGP session between your Cloud Routers and their edge routers for each VLAN attachment. You don't need to configure BGP on your on-premises router. Google and your service provider automatically set the correct configurations.

The answer is D: Partner interconnect is of two types layer 2 and layer 3 With Layer 2 Interconnect you MUST configure BGP on your on-prem router With Layer 3: router configuration and peers are fully automated. Hence the question "Your on-prem router cannot run a BGP protocol configuration"

Layer 3 Partner Interconnect allows you to connect your on-premises network to Google Cloud without needing to configure BGP on your on-premises router, as the service provider will handle the BGP session between the Cloud Router and their edge routers. This matches your scenario where you cannot configure BGP on your own on-premises router.

Layer 3 Partner Interconnect allows you to connect your on-premises network to Google Cloud without needing to configure BGP on your on-premises router, as the service provider will handle the BGP session between the Cloud Router and their edge routers. This matches your scenario where you cannot configure BGP on your own on-premises router.

https://cloud.google.com/network-connectivity/docs/interconnect/concepts/partner-overview

As on-prem router doesnt support bgp therefore we need to get the partner interconnect with layer 3 capability.

L3 does not need bgp on prem router

answer is D

Guys , most of em are giving right documents but wrong answers, the answer is C, refer the below link , https://cloud.google.com/network-connectivity/docs/interconnect/concepts/partner-overview#connectivity-type It says layer 2 doesn't need BGP configurations, where else layer3 requires BGP configuration

For Layer 3 connections, your service provider establishes a BGP session between your Cloud Routers and their on-premises routers for each VLAN attachment. You don't need to configure BGP on your local router. Google and your service provider automatically set the correct BGP configurations

Partner Interconnect with a layer 2 partner allows you to connect to GCP through a partner's connection to Google's network. This model doesn't require BGP configuration on your on-premises router, and the partner handles the BGP peering. Since you can't meet Google at one of its POP locations, Direct Peering and Dedicated Interconnect are not viable options. Partner Interconnect with a layer 3 partner would require BGP configuration on your on-premises router, so it's not the best choice in this scenario.

Given these specifications, the best option for connecting your on-premises network to a GCP VPC is D. Partner Interconnect with a layer 3 partner. This way, you can leverage your service provider’s existing physical connection to Google’s network without meeting Google at one of its POP locations, and avoid running a BGP configuration on your on-premises router.

as per explained on the docs, the layer 3 connectivity doesn't need BGP config on your local router. https://cloud.google.com/network-connectivity/docs/interconnect/concepts/partner-overview#connectivity-type

I go with C

Answer is : D

D is the answer - For layer 2 connections, you must configure and establish a BGP session between your Cloud Routers and on-premises routers for each VLAN attachment that you create. The BGP configuration information is provided by the VLAN attachment after your service provider has configured it. For a Layer 3 connection BGP is configured from your partner to the Cloud Router in GCP, no need for BGP on-premise.

I'll go with C, BGP is layer 4 but in this case it use Layer 3 Essentially, the carrier provides a Layer 3 Partner Interconnect service to you, and then "binds" your VLAN attachment with the correct MPLS VPN on the carrier's edge device. Because this is a Layer 3 service model, the BGP session is established between your Cloud Router and your VRF inside the carrier edge device.