A manufacturer's MPLS provider will extend the private WAN into Google Cloud. The manufacturer will not order its own interconnect port and will not use the public internet. Which model is this?
Select an answer to reveal the explanation.
Short Explanation
The carrier already has the private road, and they are the ones turning into Google. You stay on the MPLS handoff and you do not order your own interconnect. An internet VPN to HA VPN would leave the private WAN you just said you would keep.
Full Explanation
An MPLS provider handoff into Google Cloud keeps the manufacturer's traffic on the private WAN and off the public internet. The manufacturer is not ordering the port. The carrier is extending the WAN. That is the provider private-connectivity model. A dedicated Cloud Interconnect the manufacturer orders and cross-connects is the customer's own physical port, which they said they will not order. Native IPsec to an HA VPN gateway uses the public internet, which this design excludes. An SDCI virtual circuit requires the customer's fabric port. They do not have one, and they are not ordering the circuit. The carrier is the actor. Exam caveat: the carrier attachment still has to land on a Google VLAN attachment and a Cloud Router. A private WAN that stops at the carrier's edge does not enter the VPC. Operational check: the manufacturer should learn the VPC prefixes from the MPLS cloud handoff, and there should be no HA VPN tunnel counters for this plant.