Which of the following is a feature of a BGP peer group?

• A. Hold time and keepalive intervals
• B. Update-source, next-hop-self, and route reflectors
• C. Update-source, next-hop-self, ebgp-multihop and authentication of the bgp sessions
• D. Maximum-prefix, route dampening and TTL security

Answer: (C)

Peer groups are for applying common session settings to multiple BGP neighbors, so you configure parameters once and have them apply to all members. The options listed here are precisely the session-related controls you’d want shared across a group.

Update-source ensures the BGP session is established from a consistent local address (often a loopback), which is essential in scalable topologies where many peers use the same addressing approach. Next-hop-self is used so that when routes are advertised to the group’s iBGP peers, the next-hop attribute is the local router, keeping internal paths reachable for all peers in the group. EBGP-multihop is necessary when EBGP peers aren’t directly connected; configuring it on the group lets all such sessions form correctly without separate per-neighbor settings. Authentication of the BGP sessions provides a single shared MD5 password for all sessions in the group, strengthening security across the whole set.

Other options mix timer settings, route reflector behavior, or per-peer features that aren’t as cleanly represented as a single group-wide configuration, so they’re not the best match for the concept being tested.