Two cloud IOS XE routers peer with iBGP. Return traffic should prefer the router closer to the users. The preference has to be shared between those routers. Which attribute does that?
Select an answer to reveal the explanation.
Short Explanation
You need both cloud routers to agree on the closer door, so the note has to travel with iBGP. You set local preference. Weight stays on the router where you typed it, and the other cloud router never sees it.
Full Explanation
Local preference is sent to iBGP peers. Set a higher local preference for the closer exit and both cloud routers can select it. A higher value is preferred. Weight is local to the router it is configured on and is not advertised, so the second cloud router would not share the decision. The IKE lifetime is not copied into iBGP. The OSPF dead timer does not select an iBGP exit. Exam caveat: local preference does not cross eBGP to the campus. It only steers the choice between these two iBGP routers. Operational check: show ip bgp on both cloud routers should show the higher local preference on the closer exit, and return traffic should arrive on that router. A preference set on only one router still has to be the value iBGP actually advertises to the other.