A mill's MPLS carrier already hands the private WAN off to Google Cloud Partner Interconnect. Someone suggests the mill order Dedicated Interconnect on its own. The carrier path is the one they must use. Which path is that?
Select an answer to reveal the explanation.
Short Explanation
The carrier is already standing at the cloud door with your private WAN. You use that MPLS handoff into Partner Interconnect. Dedicated Interconnect would be a circuit you order yourself, which is a different model from the one you were told to use.
Full Explanation
An MPLS provider handoff into Partner Interconnect keeps the mill on the private WAN, and the carrier, not the mill, provides the connection into Google Cloud. That is the private provider model they must use. Dedicated Interconnect is a port the customer orders and connects themselves. It can be private and it is not this carrier handoff. Cloud VPN over the internet is native IPsec. Partner Interconnect is not a public VPN. A colocation cross-connect needs a cage the mill does not occupy. Exam caveat: confirm the carrier's attachment is actually associated with the VPC. A handoff that lands in the wrong project never shows the prefixes. Operational check: the VPC routes should arrive through the carrier, and the mill should not have a Dedicated Interconnect port in its own name for this path.