Name four features a peer group can have

• A. Update-source, next-hop-self, ebgp-multihop and authentication of the bgp sessions
• B. Weight, local preference, MED and AS_PATH prepending
• C. Route filtering, redirection, logging, and timers
• D. Update-source, route reflectors, hold time, and keepalive

Answer: (A)

Peer groups let you apply the same BGP session settings to multiple neighbors. Four features you can configure for a peer group are update-source, next-hop-self, eBGP multihop, and authentication of the BGP sessions.

update-source chooses which IP address the BGP TCP session uses, which is important when neighbors reach you via loopback interfaces or you want a consistent source across many sessions. next-hop-self changes the next-hop seen by iBGP peers to your own address, helping ensure the advertised routes have a reachable next-hop within the group. eBGP multihop allows establishing eBGP sessions with neighbors that aren’t directly connected by increasing the TCP packet TTL. authentication adds a shared password (MD5) to secure the BGP session, a common requirement across multiple peers in the same group.

The other options mix in route attributes or unrelated features that aren’t configured as peer-group session settings in the same way, so they don’t represent the typical set of peer-group features.