Q: 14
Refer to the exhibit, which shows an enterprise network connected to an internet service provider.
An administrator must configure a loopback as a BGP source to connect to the ISP.
Which two commands are required to establish the connection? (Choose two.)
An administrator must configure a loopback as a BGP source to connect to the ISP.
Which two commands are required to establish the connection? (Choose two.)Options
Discussion
A and B here. eBGP with loopback needs ebgp-enforce-multihop to let the connection work, and update-source points BGP to use the loopback IP. D is for next hop recursion which isn’t required in this ask. Pretty sure about this combo but correct me if you’ve done it differently in practice.
Its A and B. Both needed when you set up BGP neighbors via loopback so the session can come up.
A and B tbh. Loopback peering with eBGP needs update-source to pick the loopback IP, and ebgp-enforce-multihop so TTL lets the session form. D looks relevant but isn't for this use case. Anyone disagree?
Feels like A and B. Using loopback for eBGP peering always needs you to set update-source and allow multihop, or it won't bring up the session. D looks tempting but that's not needed here. Let me know if anyone's seen a case where this didn't work.
A is wrong, B and A. Both are needed for BGP peering via loopback, pretty sure that's in the official admin guide and shows up in practice labs too.
I don’t think it’s C/D. BGP with loopback as the source needs A (ebgp-enforce-multihop) and B (update-source), otherwise the session won’t form. D is a trap, for recursive next hop only. Pretty sure but open if I missed something.
A/B makes sense. Whenever BGP uses loopback as source, you need update-source to specify it, and ebgp-enforce-multihop since eBGP expects directly connected peers otherwise. That’s what I saw in the admin guide and labs too, but could be missing something minor.
C/D? I always get tripped up when it's loopback as BGP source, thought recursive-next-hop might be needed.
A/B imo. You need ebgp-enforce-multihop and update-source for this setup with a loopback, that's from official guide and some similar lab tasks I saw. If you want a reference, practice labs or the config examples in the admin guide cover this.
I think it should be A and B, since for eBGP with a loopback you need to allow multihop and set update-source. Not 100% but I don't see C or D fitting here, since they're for iBGP or recursive next hop situations. Agree?
Be respectful. No spam.
