Question 540
At fictional Pinewell Electronics, a network engineer supporting engineering labs is reviewing IGMP and PIM multicast distribution during a lab-to-production acceptance (HCIP-H12-821-MULTICAST-135). The observed network issue is: A PIM-SM router cannot switch efficiently to a shortest-path tree because its source route points through another neighbor. Which ongoing preventive or detective control would best reduce recurrence?
Explanation
Correct Answer
The preventive or detective safeguard is: Measure source-tree RPF selection after unicast topology changes. This directly addresses the recurring fault: A PIM-SM router cannot switch efficiently to a shortest-path tree because its source route points through another neighbor. The corrective action would be: Check reverse path to the source and verify supported SPT switching behavior. Success is demonstrated when: Traffic moves to the expected shortest-path branch without invalid RPF drops.
Incorrect Answers
“Compare dense and sparse behavior before expanding multicast across WAN sites” addresses recurrence of another problem: A PIM dense-mode network floods large multicast volumes to branches with no interested receivers. That problem depends on: The preventive or detective safeguard is: Compare dense and sparse behavior before expanding multicast across WAN sites. The recurring risk here is: A PIM-SM router cannot switch efficiently to a shortest-path tree because its source route points through another neighbor. The more targeted safeguard is “Measure source-tree RPF selection after unicast topology changes” because the preventive or detective safeguard is: Measure source-tree RPF selection after unicast topology changes.
“Check the querier role and aging timers during multicast incidents” addresses recurrence of another problem: A multicast router sees no group receivers because IGMP query messages are absent from a VLAN. That problem depends on: The preventive or detective safeguard is: Check the querier role and aging timers during multicast incidents. The recurring risk here is: A PIM-SM router cannot switch efficiently to a shortest-path tree because its source route points through another neighbor. The more targeted safeguard is “Measure source-tree RPF selection after unicast topology changes” because the preventive or detective safeguard is: Measure source-tree RPF selection after unicast topology changes.
“Include explicit (source, group) joins in SSM acceptance tests” addresses recurrence of another problem: A source-specific multicast receiver attempts to use an any-source RP tree even though the deployment expects a specified source. That problem depends on: The preventive or detective safeguard is: Include explicit (source, group) joins in SSM acceptance tests. The recurring risk here is: A PIM-SM router cannot switch efficiently to a shortest-path tree because its source route points through another neighbor. The more targeted safeguard is “Measure source-tree RPF selection after unicast topology changes” because the preventive or detective safeguard is: Measure source-tree RPF selection after unicast topology changes.