350-401 · Question #386
What are two methods of ensuring that the multicast RPF check passes without changing the unicast routing table? (Choose two.)
The correct answer is A. implementing static mroutes C. implementing MBGP. To allow multicast RPF checks to pass without altering the unicast routing table, engineers can implement static mroutes or use MBGP to carry multicast-specific routing information.
Question
Options
- Aimplementing static mroutes
- Bdisabling BGP routing protocol
- Cimplementing MBGP
- Ddisabling the interface of the router back to the multicast source
- Eimplementing OSPF routing protocol
How the community answered
(39 responses)- A62% (24)
- B5% (2)
- D23% (9)
- E10% (4)
Why each option
To allow multicast RPF checks to pass without altering the unicast routing table, engineers can implement static mroutes or use MBGP to carry multicast-specific routing information.
Static mroutes (multicast routes) explicitly define the RPF interface and next hop for multicast sources, allowing the RPF check to pass independently of the unicast routing table by providing a direct lookup for multicast source reachability.
Disabling BGP would disrupt unicast routing and does not provide an alternative mechanism for the multicast RPF check.
MBGP (Multiprotocol BGP) allows BGP to exchange multicast-specific Network Layer Reachability Information (NLRI), enabling the PIM RPF check to use this distinct multicast routing information instead of relying solely on the unicast routing table.
Disabling an interface to the multicast source would prevent multicast traffic from entering the network entirely, not facilitate the RPF check.
Implementing OSPF would involve changing the unicast routing table, which the question explicitly states should be avoided.
Concept tested: Multicast RPF check bypass
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipmulti_pim/configuration/xe-16/imc-pim-xe-16-book/imc-pim-cfg.html
Topics
Community Discussion
No community discussion yet for this question.