A museum has a cage in one building. The cloud on-ramp is in another building on the same provider campus. The museum does not have an SDCI fabric port. How should the museum reach the on-ramp?
Select an answer to reveal the explanation.
Short Explanation
Two buildings on the campus do not invent a fabric port you do not have. You order the physical cross-connect from your own cage to the on-ramp. That is still colocation, and a virtual circuit is not waiting on a port you never bought.
Full Explanation
Colocation is the customer's cage and a physical cross-connect the customer orders to the cloud on-ramp. The on-ramp being in another building on the same campus changes the cable path. It does not change who orders the cross-connect, and it does not create an SDCI port. SDCI would be a virtual circuit on a fabric port the museum does not have. An internet VPN can leave the building and it abandons the private cross-connect. An MPLS handoff would be the carrier extending the WAN. The museum's own cage is not that product. Exam caveat: the provider has to offer the extended cross-connect between those buildings. If they do not, the museum needs a different model. It still does not become SDCI without a fabric port. Operational check: the cross-connect order should name the museum cage and the on-ramp panel, and the cage router should see the cloud prefixes on that link.