A lab company already has an SDCI port in one metro and wants a private virtual circuit from that port into Google Cloud. They do not want a new physical interconnect they would order themselves. Which model is this?
Select an answer to reveal the explanation.
Short Explanation
You already have the programmable port, so you order a virtual circuit from it into Google Cloud instead of pulling a new physical interconnect yourself. That is the SDCI model. HA VPN over the internet leaves the private fabric you are trying to use.
Full Explanation
An SDCI regional cross-connect is a virtual circuit from a fabric port the customer already has into the cloud on-ramp in that metro. The lab company wants exactly that into Google Cloud, and they refused a new physical port of their own. A dedicated Cloud Interconnect is the physical port they said they do not want to order. Native IPsec to an HA VPN gateway uses the public internet. It does not use the SDCI port. A colocation cross-connect requires their cage in the meet-me room. They do not occupy that cage. The attachment they want rides the fabric port they already pay for. Exam caveat: the virtual circuit still becomes a Google Cloud attachment, often a partner interconnect VLAN. SDCI is how it is ordered. The VLAN still has to be accepted on a Cloud Router. Operational check: the fabric portal should show the virtual circuit live to Google in this metro, and Google should show the attachment up on the Cloud Router the lab company named.