Question 570
Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A multicast service sends duplicate stream copies into access rings after a failover because forwarding boundaries are not recalculated. Which observable result most directly verifies that this network issue was resolved?
Explanation
Correct Answer
For this scenario, the observed situation is: A multicast service sends duplicate stream copies into access rings after a failover because forwarding boundaries are not recalculated. The most directly supported response is: Inspect PIM interfaces, RPF state, and access multicast snooping/membership tables. Technical basis: Multicast replication follows distribution trees and requires consistent RPF and listener state. Evidence of success: The downstream branch receives one intended stream copy after convergence without loops. Ongoing protection: Exercise link failover with multicast counters and packet duplication checks.
Incorrect Answers
That observation tests a different mechanism: E-Access is intended for wholesale Ethernet access arrangements involving operator connectivity. It cannot establish this case, whose mechanism is: Multicast replication follows distribution trees and requires consistent RPF and listener state. The needed verification is: The downstream branch receives one intended stream copy after convergence without loops.
That observation tests a different mechanism: VPN route distinguishers make otherwise identical prefixes distinct while route targets control membership. It cannot establish this case, whose mechanism is: Multicast replication follows distribution trees and requires consistent RPF and listener state. The needed verification is: The downstream branch receives one intended stream copy after convergence without loops.
That observation tests a different mechanism: Hierarchical QoS can combine aggregate shaping with per-class scheduling for shared access links. It cannot establish this case, whose mechanism is: Multicast replication follows distribution trees and requires consistent RPF and listener state. The needed verification is: The downstream branch receives one intended stream copy after convergence without loops.