350-401 · Question #245
What are two reasons to define static peers in EIGRP? (Choose two.)
The correct answer is A. Security requirements do not allow dynamic learning of neighbors. D. The link between peers requires unicast packets.. Static EIGRP peer definitions are used to enforce security policies by preventing dynamic neighbor discovery and to enable EIGRP peering over link types that do not support multicast.
Question
Options
- ASecurity requirements do not allow dynamic learning of neighbors.
- BThe link between peers requires multicast packets.
- CBack-level peers require static definition for successful connection.
- DThe link between peers requires unicast packets.
How the community answered
(45 responses)- A91% (41)
- B2% (1)
- C7% (3)
Why each option
Static EIGRP peer definitions are used to enforce security policies by preventing dynamic neighbor discovery and to enable EIGRP peering over link types that do not support multicast.
Defining static EIGRP neighbors is a security measure that prevents unauthorized routers from forming dynamic adjacencies and exchanging routing information within the EIGRP domain.
If a link requires multicast packets, dynamic EIGRP neighbor discovery (which relies on multicast Hellos) would function correctly without the need for static definitions.
The concept of 'back-level peers' is not a standard technical reason requiring static EIGRP peering, as EIGRP versions are generally backward compatible for basic neighbor formation.
Static EIGRP neighbors are required on network segments where multicast is not supported or disabled, forcing EIGRP to send unicast Hello packets and updates to specific peers to establish and maintain adjacencies.
Concept tested: EIGRP Static Neighbors use cases
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_eigrp/configuration/15-mt/ire-15-mt-book/ire-static-neighbors.html
Topics
Community Discussion
No community discussion yet for this question.