Question 360
At fictional Maple Housing, a network engineer supporting property locations is reviewing IGMP and PIM multicast distribution during a supervised route change (HCIP-H12-821-MULTICAST-090). The observed network issue is: A multicast core drops packets after a path failover because the unicast RPF route has not converged to the new incoming link. Which ongoing preventive or detective control would best reduce recurrence?
Explanation
Correct Answer
The preventive or detective safeguard is: Test source-route failure recovery for multicast services. This directly addresses the recurring fault: A multicast core drops packets after a path failover because the unicast RPF route has not converged to the new incoming link. The corrective action would be: Repair or accelerate intended unicast convergence and validate multicast state reevaluation. Success is demonstrated when: Multicast packets resume on the revised valid RPF interface after failover.
Incorrect Answers
“Validate snooping memberships after each VLAN access change” addresses recurrence of another problem: A receiver sends IGMP membership reports but the local VLAN switch floods the multicast group to every port. That problem depends on: The preventive or detective safeguard is: Validate snooping memberships after each VLAN access change. The recurring risk here is: A multicast core drops packets after a path failover because the unicast RPF route has not converged to the new incoming link. The more targeted safeguard is “Test source-route failure recovery for multicast services” because the preventive or detective safeguard is: Test source-route failure recovery for multicast services.
“Record IGMP version compatibility for source-filtered applications” addresses recurrence of another problem: A network expects IGMPv3 source-specific filtering but uses routers configured only for IGMPv2. That problem depends on: The preventive or detective safeguard is: Record IGMP version compatibility for source-filtered applications. The recurring risk here is: A multicast core drops packets after a path failover because the unicast RPF route has not converged to the new incoming link. The more targeted safeguard is “Test source-route failure recovery for multicast services” because the preventive or detective safeguard is: Test source-route failure recovery for multicast services.
“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 multicast core drops packets after a path failover because the unicast RPF route has not converged to the new incoming link. The more targeted safeguard is “Test source-route failure recovery for multicast services” because the preventive or detective safeguard is: Test source-route failure recovery for multicast services.