You want to use Cloud Interconnect to connect your on-premises network to a GCP VPC.
You cannot meet Google at one of its point-of-presence (POP) locations, and your on-premises router cannot run a Border Gateway Protocol (BGP) configuration.
Which connectivity model should you use?
Click on the arrows to vote for the correct answer
A. B. C. D.B.
https://cloud.google.com/interconnect/docs/support/faqIf you cannot meet Google at one of its point-of-presence (POP) locations and your on-premises router cannot run a Border Gateway Protocol (BGP) configuration, you have two options for using Cloud Interconnect to connect your on-premises network to a GCP VPC: Dedicated Interconnect or Partner Interconnect with a layer 2 partner.
Direct Peering is not an appropriate option because it requires you to have a BGP-enabled router and meet Google at a POP location.
Dedicated Interconnect provides a direct physical connection between your on-premises network and Google's network. This connection is established through a third-party colocation provider, who provides the physical cross-connect between your on-premises router and Google's router. Dedicated Interconnect does not require BGP, but it is recommended. You can also use static routing instead of BGP.
Partner Interconnect with a layer 2 partner provides a layer 2 connection between your on-premises network and Google's network. This connection is established through a service provider who acts as a layer 2 intermediary between your on-premises router and Google's router. Partner Interconnect with a layer 2 partner does not require BGP, and you can use static routing instead.
Partner Interconnect with a layer 3 partner is not an appropriate option because it requires you to have a BGP-enabled router.
Therefore, in this case, the recommended connectivity model is either Dedicated Interconnect or Partner Interconnect with a layer 2 partner, depending on your specific requirements and constraints.