A lab already has an SDCI port in the right metro, with a virtual circuit into one AWS region. A second AWS region must be added on that same private fabric. What should they order?
Select an answer to reveal the explanation.
Short Explanation
The port you already pay for can grow another private path. You order another virtual circuit on that SDCI port toward the second region. A new physical port is the wait this model avoids, and an internet VPN leaves the private fabric.
Full Explanation
SDCI gives you a fabric port and then virtual circuits into cloud on-ramps, including another region, without a new physical port for each one. The lab already has the port and one circuit. The second region is another virtual circuit on that port. A new physical port in an unused metro, with a cage cross-connect, is a different and slower build. An internet VPN can reach the second region and it is no longer the private fabric they asked to stay on. A Catalyst SD-WAN controller does not convert an SDCI port into an OMP session. The handoff is still the virtual circuit. Exam caveat: the virtual circuit has to land on the interconnect location that can reach the second region. A circuit aimed at the first region does not become multi-region by itself. Operational check: the fabric portal should show two virtual circuits on the same port, and the new one should carry the second region's prefixes.