Question 560
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: A NOC sees rising interface-level drops but cannot determine whether loss occurs in the assured-forwarding queue or at an ingress policer. Which operational control would best prevent a recurrence of this exact failure mode?
- Track sustained and burst traffic separately when changing service policers.
- Trace classification and scheduling at every congested hop during service acceptance.
- Review drop curves with a known traffic mix, including high and low loss-priority flows.
- Preserve labeled counter baselines during incident and post-change reviews.
Explanation
Correct Answer
D:Preserve labeled counter baselines during incident and post-change reviews. The control limits repetition of the described root condition: Interface total drops conflate multiple mechanisms, while queue and policer counters identify different stages of treatment. During audits, confirm: The relevant drop counter increments only for the mechanism causing the observed service problem.
Incorrect Answers
A:Track sustained and burst traffic separately when changing service policers. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Policer threshold drop. A policer meters a flow and may discard or reclassify out-of-profile traffic; it is not a capacity reservation. In this scenario, however, the distinguishing issue is Queue telemetry misleading totals and the confirming observation is: The relevant drop counter increments only for the mechanism causing the observed service problem.
B:Trace classification and scheduling at every congested hop during service acceptance. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Traffic priority at egress bottleneck. CoS decisions that influence transmission occur at the real bottleneck; accurate classification upstream cannot reserve service at a differently configured output. In this scenario, however, the distinguishing issue is Queue telemetry misleading totals and the confirming observation is: The relevant drop counter increments only for the mechanism causing the observed service problem.
C:Review drop curves with a known traffic mix, including high and low loss-priority flows. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically RED drop profile. Random early detection uses occupancy thresholds and packet loss priority to begin selective dropping before full buffer exhaustion. In this scenario, however, the distinguishing issue is Queue telemetry misleading totals and the confirming observation is: The relevant drop counter increments only for the mechanism causing the observed service problem.
Question 561
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: A multicast router receives packets from the source on an interface different from its unicast route back toward that source, and drops packets instead of forwarding them. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare source RPF route and actual incoming multicast interface using group and source forwarding state.
- Inspect PIM Hello counters and interface filtering for the directly connected transit.
- Inspect the unicast best route toward each source and the multicast packet ingress interface after the metric change.
- Inspect PIM dense-mode prune and periodic reflood behavior on the branch.
Explanation
Correct Answer
A:Compare source RPF route and actual incoming multicast interface using group and source forwarding state. This check examines the decisive condition for PIM RPF interface mismatch before any unrelated changes are made. The underlying mechanism is: Reverse-path forwarding rejects traffic received away from the interface selected as the path toward the multicast source. The confirming observation is: RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list.
Incorrect Answers
B:Inspect PIM Hello counters and interface filtering for the directly connected transit. This is a plausible diagnostic check for a different IP Multicast condition, specifically PIM hello neighbor dead. PIM neighbor discovery requires compatible Hello exchange on every required multicast-routing link. In this scenario, however, the distinguishing issue is PIM RPF interface mismatch and the confirming observation is: RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list.
C:Inspect the unicast best route toward each source and the multicast packet ingress interface after the metric change. This is a plausible diagnostic check for a different IP Multicast condition, specifically RPF asymmetry after IGP cost change. An IGP change can alter RPF selection, invalidating multicast arriving on an old interface even when unicast service succeeds. In this scenario, however, the distinguishing issue is PIM RPF interface mismatch and the confirming observation is: RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list.
D:Inspect PIM dense-mode prune and periodic reflood behavior on the branch. This is a plausible diagnostic check for a different IP Multicast condition, specifically PIM dense-mode prune expiry. Dense mode may periodically refresh distribution and prune state, so temporary unwanted traffic can occur before pruning. In this scenario, however, the distinguishing issue is PIM RPF interface mismatch and the confirming observation is: RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list.
Question 562
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: A multicast router receives packets from the source on an interface different from its unicast route back toward that source, and drops packets instead of forwarding them. Which routing or service mechanism best explains the reported behavior?
- PIM neighbor discovery requires compatible Hello exchange on every required multicast-routing link.
- Reverse-path forwarding rejects traffic received away from the interface selected as the path toward the multicast source.
- An IGP change can alter RPF selection, invalidating multicast arriving on an old interface even when unicast service succeeds.
- Dense mode may periodically refresh distribution and prune state, so temporary unwanted traffic can occur before pruning.
Explanation
Correct Answer
B:Reverse-path forwarding rejects traffic received away from the interface selected as the path toward the multicast source. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list. The targeted correction is: Correct source reachability, RPF policy or topology so valid multicast traffic arrives on the selected RPF interface.
Incorrect Answers
A:PIM neighbor discovery requires compatible Hello exchange on every required multicast-routing link. This is a plausible protocol explanation for a different IP Multicast condition, specifically PIM hello neighbor dead. PIM neighbor discovery requires compatible Hello exchange on every required multicast-routing link. In this scenario, however, the distinguishing issue is PIM RPF interface mismatch and the confirming observation is: RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list.
C:An IGP change can alter RPF selection, invalidating multicast arriving on an old interface even when unicast service succeeds. This is a plausible protocol explanation for a different IP Multicast condition, specifically RPF asymmetry after IGP cost change. An IGP change can alter RPF selection, invalidating multicast arriving on an old interface even when unicast service succeeds. In this scenario, however, the distinguishing issue is PIM RPF interface mismatch and the confirming observation is: RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list.
D:Dense mode may periodically refresh distribution and prune state, so temporary unwanted traffic can occur before pruning. This is a plausible protocol explanation for a different IP Multicast condition, specifically PIM dense-mode prune expiry. Dense mode may periodically refresh distribution and prune state, so temporary unwanted traffic can occur before pruning. In this scenario, however, the distinguishing issue is PIM RPF interface mismatch and the confirming observation is: RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list.
Question 563
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A multicast router receives packets from the source on an interface different from its unicast route back toward that source, and drops packets instead of forwarding them. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- A PIM neighbor forms and downstream join state propagates after the control traffic is allowed.
- The multicast source ingress matches current RPF route selection and forwarding resumes.
- RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list.
- The RP learns the moved source and traffic begins flowing down the established receiver tree.
Explanation
Correct Answer
C:RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Reverse-path forwarding rejects traffic received away from the interface selected as the path toward the multicast source.
Incorrect Answers
A:A PIM neighbor forms and downstream join state propagates after the control traffic is allowed. This is a plausible observed evidence for a different IP Multicast condition, specifically PIM hello neighbor dead. PIM neighbor discovery requires compatible Hello exchange on every required multicast-routing link. In this scenario, however, the distinguishing issue is PIM RPF interface mismatch and the confirming observation is: RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list.
B:The multicast source ingress matches current RPF route selection and forwarding resumes. This is a plausible observed evidence for a different IP Multicast condition, specifically RPF asymmetry after IGP cost change. An IGP change can alter RPF selection, invalidating multicast arriving on an old interface even when unicast service succeeds. In this scenario, however, the distinguishing issue is PIM RPF interface mismatch and the confirming observation is: RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list.
D:The RP learns the moved source and traffic begins flowing down the established receiver tree. This is a plausible observed evidence for a different IP Multicast condition, specifically ASM shared-tree source loss. A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source. In this scenario, however, the distinguishing issue is PIM RPF interface mismatch and the confirming observation is: RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list.
Question 564
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A multicast router receives packets from the source on an interface different from its unicast route back toward that source, and drops packets instead of forwarding them. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Restore the minimum authorized PIM control traffic on the affected link.
- Correct multicast path placement or source RPF design to agree with the intended unicast topology.
- Correct the source DR and RP discovery path without rebuilding healthy downstream joins.
- Correct source reachability, RPF policy or topology so valid multicast traffic arrives on the selected RPF interface.
Explanation
Correct Answer
D:Correct source reachability, RPF policy or topology so valid multicast traffic arrives on the selected RPF interface. The change addresses the root behavior described here: Reverse-path forwarding rejects traffic received away from the interface selected as the path toward the multicast source. Verify success with: RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list.
Incorrect Answers
A:Restore the minimum authorized PIM control traffic on the affected link. This is a plausible configuration or operational fix for a different IP Multicast condition, specifically PIM hello neighbor dead. PIM neighbor discovery requires compatible Hello exchange on every required multicast-routing link. In this scenario, however, the distinguishing issue is PIM RPF interface mismatch and the confirming observation is: RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list.
B:Correct multicast path placement or source RPF design to agree with the intended unicast topology. This is a plausible configuration or operational fix for a different IP Multicast condition, specifically RPF asymmetry after IGP cost change. An IGP change can alter RPF selection, invalidating multicast arriving on an old interface even when unicast service succeeds. In this scenario, however, the distinguishing issue is PIM RPF interface mismatch and the confirming observation is: RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list.
C:Correct the source DR and RP discovery path without rebuilding healthy downstream joins. This is a plausible configuration or operational fix for a different IP Multicast condition, specifically ASM shared-tree source loss. A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source. In this scenario, however, the distinguishing issue is PIM RPF interface mismatch and the confirming observation is: RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list.
Question 565
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A multicast router receives packets from the source on an interface different from its unicast route back toward that source, and drops packets instead of forwarding them. Which operational control would best prevent a recurrence of this exact failure mode?
- Audit RPF path changes whenever unicast routing policy changes.
- Include protocol control-plane permit tests in multicast transit security reviews.
- Include multicast RPF tests in every core metric migration.
- Test source failover and relocation independently of receiver join success.
Explanation
Correct Answer
A:Audit RPF path changes whenever unicast routing policy changes. The control limits repetition of the described root condition: Reverse-path forwarding rejects traffic received away from the interface selected as the path toward the multicast source. During audits, confirm: RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list.
Incorrect Answers
B:Include protocol control-plane permit tests in multicast transit security reviews. This is a plausible preventive practice for a different IP Multicast condition, specifically PIM hello neighbor dead. PIM neighbor discovery requires compatible Hello exchange on every required multicast-routing link. In this scenario, however, the distinguishing issue is PIM RPF interface mismatch and the confirming observation is: RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list.
C:Include multicast RPF tests in every core metric migration. This is a plausible preventive practice for a different IP Multicast condition, specifically RPF asymmetry after IGP cost change. An IGP change can alter RPF selection, invalidating multicast arriving on an old interface even when unicast service succeeds. In this scenario, however, the distinguishing issue is PIM RPF interface mismatch and the confirming observation is: RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list.
D:Test source failover and relocation independently of receiver join success. This is a plausible preventive practice for a different IP Multicast condition, specifically ASM shared-tree source loss. A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source. In this scenario, however, the distinguishing issue is PIM RPF interface mismatch and the confirming observation is: RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list.
Question 566
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: Receivers join an ASM multicast group but no shared tree develops because the last-hop router cannot determine an RP for that group. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Check RP address resolution and RPF route on every affected last-hop router.
- Inspect group-to-RP mapping and the PIM join state on receiver-facing and upstream routers.
- Inspect source DR registration and RP source-state updates separately from receiver joins.
- Inspect PIM neighbor and join state at each transit interface along the RPF path.
Explanation
Correct Answer
B:Inspect group-to-RP mapping and the PIM join state on receiver-facing and upstream routers. This check examines the decisive condition for PIM sparse RP mapping absent before any unrelated changes are made. The underlying mechanism is: PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over. The confirming observation is: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
Incorrect Answers
A:Check RP address resolution and RPF route on every affected last-hop router. This is a plausible diagnostic check for a different IP Multicast condition, specifically RP unreachable by unicast. PIM joins are sent toward the RP using unicast-derived RPF paths; a configured RP with no route is not usable. In this scenario, however, the distinguishing issue is PIM sparse RP mapping absent and the confirming observation is: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
C:Inspect source DR registration and RP source-state updates separately from receiver joins. This is a plausible diagnostic check for a different IP Multicast condition, specifically ASM shared-tree source loss. A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source. In this scenario, however, the distinguishing issue is PIM sparse RP mapping absent and the confirming observation is: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
D:Inspect PIM neighbor and join state at each transit interface along the RPF path. This is a plausible diagnostic check for a different IP Multicast condition, specifically Missing PIM on transit. Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path. In this scenario, however, the distinguishing issue is PIM sparse RP mapping absent and the confirming observation is: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
Question 567
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: Receivers join an ASM multicast group but no shared tree develops because the last-hop router cannot determine an RP for that group. Which routing or service mechanism best explains the reported behavior?
- PIM joins are sent toward the RP using unicast-derived RPF paths; a configured RP with no route is not usable.
- A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source.
- PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over.
- Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path.
Explanation
Correct Answer
C:PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP. The targeted correction is: Configure an appropriate reachable RP mapping for the group range.
Incorrect Answers
A:PIM joins are sent toward the RP using unicast-derived RPF paths; a configured RP with no route is not usable. This is a plausible protocol explanation for a different IP Multicast condition, specifically RP unreachable by unicast. PIM joins are sent toward the RP using unicast-derived RPF paths; a configured RP with no route is not usable. In this scenario, however, the distinguishing issue is PIM sparse RP mapping absent and the confirming observation is: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
B:A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source. This is a plausible protocol explanation for a different IP Multicast condition, specifically ASM shared-tree source loss. A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source. In this scenario, however, the distinguishing issue is PIM sparse RP mapping absent and the confirming observation is: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
D:Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path. This is a plausible protocol explanation for a different IP Multicast condition, specifically Missing PIM on transit. Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path. In this scenario, however, the distinguishing issue is PIM sparse RP mapping absent and the confirming observation is: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
Question 568
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: Receivers join an ASM multicast group but no shared tree develops because the last-hop router cannot determine an RP for that group. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- A reachable RP loopback results in downstream (*,G) join state and delivered multicast traffic.
- The RP learns the moved source and traffic begins flowing down the established receiver tree.
- PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP.
- A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
Explanation
Correct Answer
D:A group-specific RP mapping exists and the (*,G) join reaches the mapped RP. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over.
Incorrect Answers
A:A reachable RP loopback results in downstream (*,G) join state and delivered multicast traffic. This is a plausible observed evidence for a different IP Multicast condition, specifically RP unreachable by unicast. PIM joins are sent toward the RP using unicast-derived RPF paths; a configured RP with no route is not usable. In this scenario, however, the distinguishing issue is PIM sparse RP mapping absent and the confirming observation is: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
B:The RP learns the moved source and traffic begins flowing down the established receiver tree. This is a plausible observed evidence for a different IP Multicast condition, specifically ASM shared-tree source loss. A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source. In this scenario, however, the distinguishing issue is PIM sparse RP mapping absent and the confirming observation is: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
C:PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP. This is a plausible observed evidence for a different IP Multicast condition, specifically Missing PIM on transit. Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path. In this scenario, however, the distinguishing issue is PIM sparse RP mapping absent and the confirming observation is: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
Question 569
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: Receivers join an ASM multicast group but no shared tree develops because the last-hop router cannot determine an RP for that group. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Configure an appropriate reachable RP mapping for the group range.
- Restore the IGP or static route to the RP address instead of changing receiver group membership.
- Correct the source DR and RP discovery path without rebuilding healthy downstream joins.
- Enable the intended multicast routing protocol on all required transit interfaces.
Explanation
Correct Answer
A:Configure an appropriate reachable RP mapping for the group range. The change addresses the root behavior described here: PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over. Verify success with: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
Incorrect Answers
B:Restore the IGP or static route to the RP address instead of changing receiver group membership. This is a plausible configuration or operational fix for a different IP Multicast condition, specifically RP unreachable by unicast. PIM joins are sent toward the RP using unicast-derived RPF paths; a configured RP with no route is not usable. In this scenario, however, the distinguishing issue is PIM sparse RP mapping absent and the confirming observation is: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
C:Correct the source DR and RP discovery path without rebuilding healthy downstream joins. This is a plausible configuration or operational fix for a different IP Multicast condition, specifically ASM shared-tree source loss. A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source. In this scenario, however, the distinguishing issue is PIM sparse RP mapping absent and the confirming observation is: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
D:Enable the intended multicast routing protocol on all required transit interfaces. This is a plausible configuration or operational fix for a different IP Multicast condition, specifically Missing PIM on transit. Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path. In this scenario, however, the distinguishing issue is PIM sparse RP mapping absent and the confirming observation is: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
Question 570
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: Receivers join an ASM multicast group but no shared tree develops because the last-hop router cannot determine an RP for that group. Which operational control would best prevent a recurrence of this exact failure mode?
- Track RP loopback availability from each multicast island.
- Verify RP discovery and mapping on each receiver POP after configuration changes.
- Test source failover and relocation independently of receiver join success.
- Trace every hop's group state before modifying endpoint subscriptions.
Explanation
Correct Answer
B:Verify RP discovery and mapping on each receiver POP after configuration changes. The control limits repetition of the described root condition: PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over. During audits, confirm: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
Incorrect Answers
A:Track RP loopback availability from each multicast island. This is a plausible preventive practice for a different IP Multicast condition, specifically RP unreachable by unicast. PIM joins are sent toward the RP using unicast-derived RPF paths; a configured RP with no route is not usable. In this scenario, however, the distinguishing issue is PIM sparse RP mapping absent and the confirming observation is: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
C:Test source failover and relocation independently of receiver join success. This is a plausible preventive practice for a different IP Multicast condition, specifically ASM shared-tree source loss. A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source. In this scenario, however, the distinguishing issue is PIM sparse RP mapping absent and the confirming observation is: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
D:Trace every hop's group state before modifying endpoint subscriptions. This is a plausible preventive practice for a different IP Multicast condition, specifically Missing PIM on transit. Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path. In this scenario, however, the distinguishing issue is PIM sparse RP mapping absent and the confirming observation is: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests