A shipper has one SDCI port in a single metro into AWS and wants the private path to survive that metro failing. They can buy a second SDCI port in another metro. What routing should use both?
Select an answer to reveal the explanation.
Short Explanation
A second city only helps if you actually send and receive routes there. You run BGP on a virtual circuit from each metro so a metro failure withdraws one path and leaves the other. A static route to the first city ignores the port you just bought.
Full Explanation
Multi-homing a private SDCI design means each metro has a virtual circuit into AWS and BGP advertises the prefixes over both. When one metro fails, that session drops and the other metro still carries the traffic. A static route only to the first metro never uses the second port, so the new metro does not provide the survival they asked for. OSPF is not the routing protocol an AWS virtual private gateway uses on a private attachment or a VPN. Two static defaults toward an internet VPN abandon the private path entirely. That may be a backup design, and it is not using both SDCI ports. Exam caveat: both virtual circuits need to land on gateways that can actually fail over, such as a transit gateway with both attachments. A second circuit into an unused account does not rescue production. Operational check: shut the first metro's circuit and confirm the AWS prefix remains reachable through the second metro's BGP session.