A European store's BFD to an AWS cloud gateway is up, and the gateway was built in a distant region. Application delay to the VPC is far higher than the store's internet delay to a European AWS region. What should move?
Select an answer to reveal the explanation.
Short Explanation
The tunnel is healthy and it lands on another continent. You move the cloud gateway into the European region where the VPC actually sits. Swapping the SIG provider does not move an IaaS gateway, and VPN 512 is not a shortcut across regions.
Full Explanation
BFD up means the overlay to the cloud gateway works. The delay is high because that gateway, and the VPC behind it, were built in a distant region while the store is in Europe and a European region is the one they use. Move the gateway to that region. A SIG provider inspects internet-bound traffic. Changing it does not relocate an IaaS cloud gateway. VPN 512 is management and does not shorten the data path to AWS. The OSPF cost on the store LAN does not select an AWS region. Exam caveat: moving the gateway means a new attachment in the right region and a routing change. Leaving the old gateway up can keep some flows on the long path. Operational check: the store's path to the VPC should show the European cloud gateway, and the delay should drop to what that region supports.