4A0-102 · Question #117
Which of the following is a correct BGP configuration for IPv6 eBGP?
The correct answer is C. group "IPv6_eBGP" family ipv6 peer-as 65550 neighbor 2001:DB8:13::31 exit. Option C is correct because it includes the essential family ipv6 statement - which activates the IPv6 address family for the BGP group - and uses the topologically correct neighbor address 2001:DB8:13::31; in this platform's syntax, eBGP is implicitly determined by specifying…
Question
Options
- Agroup "IPv6_eBGP" family ipv6 type external peer-as 65550 neighbor 2001:DB8:3::3 exit
- Bgroup "IPv6_eBGP" type external peer-as 65550 neighbor 2001:DB8:3::3 exit
- Cgroup "IPv6_eBGP" family ipv6 peer-as 65550 neighbor 2001:DB8:13::31 exit
- Dgroup "IPv6_eBGP" type external peer-as 65550 neighbor 2001:DB8:13::31 exit
How the community answered
(55 responses)- A2% (1)
- B2% (1)
- C91% (50)
- D5% (3)
Explanation
Option C is correct because it includes the essential family ipv6 statement - which activates the IPv6 address family for the BGP group - and uses the topologically correct neighbor address 2001:DB8:13::31; in this platform's syntax, eBGP is implicitly determined by specifying a peer-as that differs from the local AS, making type external redundant. A includes both family ipv6 and type external but specifies the wrong neighbor address (2001:DB8:3::3), making it invalid for the given topology. B omits family ipv6 entirely and also uses the wrong neighbor address, failing on two counts. D uses the correct neighbor address but is missing family ipv6, meaning the group would not carry IPv6 prefixes - it's an eBGP session that simply doesn't speak IPv6.
Memory tip: Think "Family is mandatory, type is optional" - for IPv6 BGP, the family ipv6 statement is non-negotiable (no family = no IPv6 routes), while the session type can often be inferred from whether the peer-as is external; always verify the neighbor IP matches the actual interface/topology.
Topics
Community Discussion
No community discussion yet for this question.