Question 660
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: A provider uses one unicast best-path policy for customer traffic but needs multicast source RPF lookups to follow a controlled alternative path. Which operational control would best prevent a recurrence of this exact failure mode?
- Include multicast RPF tests in every core metric migration.
- Validate path change effects on packet loss and multicast jitter.
- Include protocol control-plane permit tests in multicast transit security reviews.
- Audit multicast and unicast route tables independently during asymmetric routing changes.
Explanation
Correct Answer
D:Audit multicast and unicast route tables independently during asymmetric routing changes. The control limits repetition of the described root condition: Multicast RPF may use explicitly controlled multicast routing information where Junos supports separate RPF lookup. During audits, confirm: The configured RPF selection points to the intended valid upstream interface without disturbing ordinary unicast forwarding.
Incorrect Answers
A: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 Multicast RPF policy separation and the confirming observation is: The configured RPF selection points to the intended valid upstream interface without disturbing ordinary unicast forwarding.
B:Validate path change effects on packet loss and multicast jitter. This is a plausible preventive practice for a different IP Multicast condition, specifically PIM shortest-path switch. PIM sparse mode can transition from shared RP tree to an efficient source-specific tree as receivers learn the source. In this scenario, however, the distinguishing issue is Multicast RPF policy separation and the confirming observation is: The configured RPF selection points to the intended valid upstream interface without disturbing ordinary unicast forwarding.
C: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 Multicast RPF policy separation and the confirming observation is: The configured RPF selection points to the intended valid upstream interface without disturbing ordinary unicast forwarding.
Question 661
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: A multicast transit interface passes unicast pings but PIM neighbors remain absent after an ACL blocks protocol control messages. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect PIM Hello counters and interface filtering for the directly connected transit.
- Inspect last-hop membership state and the multicast OIL for the destination group.
- Compare source RPF route and actual incoming multicast interface using group and source forwarding state.
- Inspect group-to-RP mapping and the PIM join state on receiver-facing and upstream routers.
Explanation
Correct Answer
A:Inspect PIM Hello counters and interface filtering for the directly connected transit. This check examines the decisive condition for PIM hello neighbor dead before any unrelated changes are made. The underlying mechanism is: PIM neighbor discovery requires compatible Hello exchange on every required multicast-routing link. The confirming observation is: A PIM neighbor forms and downstream join state propagates after the control traffic is allowed.
Incorrect Answers
B:Inspect last-hop membership state and the multicast OIL for the destination group. This is a plausible diagnostic check for a different IP Multicast condition, specifically Multicast output interface list empty. A passing RPF check does not create downstream delivery without an interested outgoing interface. In this scenario, however, the distinguishing issue is PIM hello neighbor dead and the confirming observation is: A PIM neighbor forms and downstream join state propagates after the control traffic is allowed.
C:Compare source RPF route and actual incoming multicast interface using group and source forwarding state. This is a plausible diagnostic check for a different IP Multicast condition, specifically PIM RPF interface mismatch. Reverse-path forwarding rejects traffic received away from the interface selected as the path toward the multicast source. In this scenario, however, the distinguishing issue is PIM hello neighbor dead and the confirming observation is: A PIM neighbor forms and downstream join state propagates after the control traffic is allowed.
D:Inspect group-to-RP mapping and the PIM join state on receiver-facing and upstream routers. This is a plausible diagnostic check for a different IP Multicast condition, specifically PIM sparse RP mapping absent. PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over. In this scenario, however, the distinguishing issue is PIM hello neighbor dead and the confirming observation is: A PIM neighbor forms and downstream join state propagates after the control traffic is allowed.
Question 662
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: A multicast transit interface passes unicast pings but PIM neighbors remain absent after an ACL blocks protocol control messages. Which routing or service mechanism best explains the reported behavior?
- A passing RPF check does not create downstream delivery without an interested outgoing interface.
- 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.
- PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over.
Explanation
Correct Answer
B:PIM neighbor discovery requires compatible Hello exchange on every required multicast-routing link. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: A PIM neighbor forms and downstream join state propagates after the control traffic is allowed. The targeted correction is: Restore the minimum authorized PIM control traffic on the affected link.
Incorrect Answers
A:A passing RPF check does not create downstream delivery without an interested outgoing interface. This is a plausible protocol explanation for a different IP Multicast condition, specifically Multicast output interface list empty. A passing RPF check does not create downstream delivery without an interested outgoing interface. In this scenario, however, the distinguishing issue is PIM hello neighbor dead and the confirming observation is: A PIM neighbor forms and downstream join state propagates after the control traffic is allowed.
C:Reverse-path forwarding rejects traffic received away from the interface selected as the path toward the multicast source. This is a plausible protocol explanation for a different IP Multicast condition, specifically PIM RPF interface mismatch. Reverse-path forwarding rejects traffic received away from the interface selected as the path toward the multicast source. In this scenario, however, the distinguishing issue is PIM hello neighbor dead and the confirming observation is: A PIM neighbor forms and downstream join state propagates after the control traffic is allowed.
D:PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over. This is a plausible protocol explanation for a different IP Multicast condition, specifically PIM sparse RP mapping absent. PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over. In this scenario, however, the distinguishing issue is PIM hello neighbor dead and the confirming observation is: A PIM neighbor forms and downstream join state propagates after the control traffic is allowed.
Question 663
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: A multicast transit interface passes unicast pings but PIM neighbors remain absent after an ACL blocks protocol control messages. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The group forwarding entry contains the intended access-facing interface after receiver membership is restored.
- RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list.
- A PIM neighbor forms and downstream join state propagates after the control traffic is allowed.
- A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
Explanation
Correct Answer
C:A PIM neighbor forms and downstream join state propagates after the control traffic is allowed. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: PIM neighbor discovery requires compatible Hello exchange on every required multicast-routing link.
Incorrect Answers
A:The group forwarding entry contains the intended access-facing interface after receiver membership is restored. This is a plausible observed evidence for a different IP Multicast condition, specifically Multicast output interface list empty. A passing RPF check does not create downstream delivery without an interested outgoing interface. In this scenario, however, the distinguishing issue is PIM hello neighbor dead and the confirming observation is: A PIM neighbor forms and downstream join state propagates after the control traffic is allowed.
B:RPF counters clear and incoming traffic on the RPF interface is forwarded to the intended receiver list. This is a plausible observed evidence for a different IP Multicast condition, specifically PIM RPF interface mismatch. Reverse-path forwarding rejects traffic received away from the interface selected as the path toward the multicast source. In this scenario, however, the distinguishing issue is PIM hello neighbor dead and the confirming observation is: A PIM neighbor forms and downstream join state propagates after the control traffic is allowed.
D:A group-specific RP mapping exists and the (*,G) join reaches the mapped RP. This is a plausible observed evidence for a different IP Multicast condition, specifically PIM sparse RP mapping absent. PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over. In this scenario, however, the distinguishing issue is PIM hello neighbor dead and the confirming observation is: A PIM neighbor forms and downstream join state propagates after the control traffic is allowed.
Question 664
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: A multicast transit interface passes unicast pings but PIM neighbors remain absent after an ACL blocks protocol control messages. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Repair IGMP last-hop membership or PIM downstream join signaling.
- Correct source reachability, RPF policy or topology so valid multicast traffic arrives on the selected RPF interface.
- Configure an appropriate reachable RP mapping for the group range.
- Restore the minimum authorized PIM control traffic on the affected link.
Explanation
Correct Answer
D:Restore the minimum authorized PIM control traffic on the affected link. The change addresses the root behavior described here: PIM neighbor discovery requires compatible Hello exchange on every required multicast-routing link. Verify success with: A PIM neighbor forms and downstream join state propagates after the control traffic is allowed.
Incorrect Answers
A:Repair IGMP last-hop membership or PIM downstream join signaling. This is a plausible configuration or operational fix for a different IP Multicast condition, specifically Multicast output interface list empty. A passing RPF check does not create downstream delivery without an interested outgoing interface. In this scenario, however, the distinguishing issue is PIM hello neighbor dead and the confirming observation is: A PIM neighbor forms and downstream join state propagates after the control traffic is allowed.
B:Correct source reachability, RPF policy or topology so valid multicast traffic arrives on the selected RPF interface. This is a plausible configuration or operational fix for a different IP Multicast condition, specifically PIM RPF interface mismatch. Reverse-path forwarding rejects traffic received away from the interface selected as the path toward the multicast source. In this scenario, however, the distinguishing issue is PIM hello neighbor dead and the confirming observation is: A PIM neighbor forms and downstream join state propagates after the control traffic is allowed.
C:Configure an appropriate reachable RP mapping for the group range. This is a plausible configuration or operational fix for a different IP Multicast condition, specifically PIM sparse RP mapping absent. PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over. In this scenario, however, the distinguishing issue is PIM hello neighbor dead and the confirming observation is: A PIM neighbor forms and downstream join state propagates after the control traffic is allowed.
Question 665
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: A multicast transit interface passes unicast pings but PIM neighbors remain absent after an ACL blocks protocol control messages. Which operational control would best prevent a recurrence of this exact failure mode?
- Include protocol control-plane permit tests in multicast transit security reviews.
- Monitor outgoing-interface lists alongside source packet counters.
- Audit RPF path changes whenever unicast routing policy changes.
- Verify RP discovery and mapping on each receiver POP after configuration changes.
Explanation
Correct Answer
A:Include protocol control-plane permit tests in multicast transit security reviews. The control limits repetition of the described root condition: PIM neighbor discovery requires compatible Hello exchange on every required multicast-routing link. During audits, confirm: A PIM neighbor forms and downstream join state propagates after the control traffic is allowed.
Incorrect Answers
B:Monitor outgoing-interface lists alongside source packet counters. This is a plausible preventive practice for a different IP Multicast condition, specifically Multicast output interface list empty. A passing RPF check does not create downstream delivery without an interested outgoing interface. In this scenario, however, the distinguishing issue is PIM hello neighbor dead and the confirming observation is: A PIM neighbor forms and downstream join state propagates after the control traffic is allowed.
C:Audit RPF path changes whenever unicast routing policy changes. This is a plausible preventive practice for a different IP Multicast condition, specifically PIM RPF interface mismatch. Reverse-path forwarding rejects traffic received away from the interface selected as the path toward the multicast source. In this scenario, however, the distinguishing issue is PIM hello neighbor dead and the confirming observation is: A PIM neighbor forms and downstream join state propagates after the control traffic is allowed.
D:Verify RP discovery and mapping on each receiver POP after configuration changes. This is a plausible preventive practice for a different IP Multicast condition, specifically PIM sparse RP mapping absent. PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over. In this scenario, however, the distinguishing issue is PIM hello neighbor dead and the confirming observation is: A PIM neighbor forms and downstream join state propagates after the control traffic is allowed.
Question 666
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A multicast group continues to show (*,G) state but no source traffic arrives after a source moves behind a different first-hop router. Which targeted check most directly distinguishes the likely cause before a configuration change?
- 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 source/group register filters and the offending DR's PIM register counters.
- Compare intended SSM group-range policy against actual application destinations.
Explanation
Correct Answer
B:Inspect source DR registration and RP source-state updates separately from receiver joins. This check examines the decisive condition for ASM shared-tree source loss before any unrelated changes are made. The underlying mechanism is: A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source. The confirming observation is: The RP learns the moved source and traffic begins flowing down the established receiver tree.
Incorrect Answers
A:Inspect group-to-RP mapping and the PIM join state on receiver-facing and upstream routers. This is a plausible diagnostic check for a different IP Multicast condition, specifically PIM sparse RP mapping absent. PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over. In this scenario, however, the distinguishing issue is ASM shared-tree source loss and the confirming observation is: The RP learns the moved source and traffic begins flowing down the established receiver tree.
C:Inspect source/group register filters and the offending DR's PIM register counters. This is a plausible diagnostic check for a different IP Multicast condition, specifically ASM RP register suppression. RP register acceptance is a control-plane admission point separate from generic unicast route filtering. In this scenario, however, the distinguishing issue is ASM shared-tree source loss and the confirming observation is: The RP learns the moved source and traffic begins flowing down the established receiver tree.
D:Compare intended SSM group-range policy against actual application destinations. This is a plausible diagnostic check for a different IP Multicast condition, specifically Multicast group range mismatch. Multicast source-specific versus any-source behavior is selected by group range and configuration policy. In this scenario, however, the distinguishing issue is ASM shared-tree source loss and the confirming observation is: The RP learns the moved source and traffic begins flowing down the established receiver tree.
Question 667
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A multicast group continues to show (*,G) state but no source traffic arrives after a source moves behind a different first-hop router. Which routing or service mechanism best explains the reported behavior?
- PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over.
- RP register acceptance is a control-plane admission point separate from generic unicast route filtering.
- A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source.
- Multicast source-specific versus any-source behavior is selected by group range and configuration policy.
Explanation
Correct Answer
C:A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The RP learns the moved source and traffic begins flowing down the established receiver tree. The targeted correction is: Correct the source DR and RP discovery path without rebuilding healthy downstream joins.
Incorrect Answers
A:PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over. This is a plausible protocol explanation for a different IP Multicast condition, specifically PIM sparse RP mapping absent. PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over. In this scenario, however, the distinguishing issue is ASM shared-tree source loss and the confirming observation is: The RP learns the moved source and traffic begins flowing down the established receiver tree.
B:RP register acceptance is a control-plane admission point separate from generic unicast route filtering. This is a plausible protocol explanation for a different IP Multicast condition, specifically ASM RP register suppression. RP register acceptance is a control-plane admission point separate from generic unicast route filtering. In this scenario, however, the distinguishing issue is ASM shared-tree source loss and the confirming observation is: The RP learns the moved source and traffic begins flowing down the established receiver tree.
D:Multicast source-specific versus any-source behavior is selected by group range and configuration policy. This is a plausible protocol explanation for a different IP Multicast condition, specifically Multicast group range mismatch. Multicast source-specific versus any-source behavior is selected by group range and configuration policy. In this scenario, however, the distinguishing issue is ASM shared-tree source loss and the confirming observation is: The RP learns the moved source and traffic begins flowing down the established receiver tree.
Question 668
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A multicast group continues to show (*,G) state but no source traffic arrives after a source moves behind a different first-hop router. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
- The RP rejects unauthorized register sources while approved sources still establish traffic.
- The application uses a supported SSM group and receivers issue source-aware joins as designed.
- The RP learns the moved source and traffic begins flowing down the established receiver tree.
Explanation
Correct Answer
D:The RP learns the moved source and traffic begins flowing down the established receiver tree. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source.
Incorrect Answers
A:A group-specific RP mapping exists and the (*,G) join reaches the mapped RP. This is a plausible observed evidence for a different IP Multicast condition, specifically PIM sparse RP mapping absent. PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over. In this scenario, however, the distinguishing issue is ASM shared-tree source loss and the confirming observation is: The RP learns the moved source and traffic begins flowing down the established receiver tree.
B:The RP rejects unauthorized register sources while approved sources still establish traffic. This is a plausible observed evidence for a different IP Multicast condition, specifically ASM RP register suppression. RP register acceptance is a control-plane admission point separate from generic unicast route filtering. In this scenario, however, the distinguishing issue is ASM shared-tree source loss and the confirming observation is: The RP learns the moved source and traffic begins flowing down the established receiver tree.
C:The application uses a supported SSM group and receivers issue source-aware joins as designed. This is a plausible observed evidence for a different IP Multicast condition, specifically Multicast group range mismatch. Multicast source-specific versus any-source behavior is selected by group range and configuration policy. In this scenario, however, the distinguishing issue is ASM shared-tree source loss and the confirming observation is: The RP learns the moved source and traffic begins flowing down the established receiver tree.
Question 669
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: A multicast group continues to show (*,G) state but no source traffic arrives after a source moves behind a different first-hop router. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Correct the source DR and RP discovery path without rebuilding healthy downstream joins.
- Configure an appropriate reachable RP mapping for the group range.
- Apply a targeted register policy for the permitted source and group scope.
- Align application group addresses and network SSM range mapping.
Explanation
Correct Answer
A:Correct the source DR and RP discovery path without rebuilding healthy downstream joins. The change addresses the root behavior described here: A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source. Verify success with: The RP learns the moved source and traffic begins flowing down the established receiver tree.
Incorrect Answers
B:Configure an appropriate reachable RP mapping for the group range. This is a plausible configuration or operational fix for a different IP Multicast condition, specifically PIM sparse RP mapping absent. PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over. In this scenario, however, the distinguishing issue is ASM shared-tree source loss and the confirming observation is: The RP learns the moved source and traffic begins flowing down the established receiver tree.
C:Apply a targeted register policy for the permitted source and group scope. This is a plausible configuration or operational fix for a different IP Multicast condition, specifically ASM RP register suppression. RP register acceptance is a control-plane admission point separate from generic unicast route filtering. In this scenario, however, the distinguishing issue is ASM shared-tree source loss and the confirming observation is: The RP learns the moved source and traffic begins flowing down the established receiver tree.
D:Align application group addresses and network SSM range mapping. This is a plausible configuration or operational fix for a different IP Multicast condition, specifically Multicast group range mismatch. Multicast source-specific versus any-source behavior is selected by group range and configuration policy. In this scenario, however, the distinguishing issue is ASM shared-tree source loss and the confirming observation is: The RP learns the moved source and traffic begins flowing down the established receiver tree.
Question 670
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: A multicast group continues to show (*,G) state but no source traffic arrives after a source moves behind a different first-hop router. Which operational control would best prevent a recurrence of this exact failure mode?
- Verify RP discovery and mapping on each receiver POP after configuration changes.
- Test source failover and relocation independently of receiver join success.
- Test registered-source admission after group-range policy updates.
- Maintain a documented multicast addressing and receiver protocol matrix.
Explanation
Correct Answer
B:Test source failover and relocation independently of receiver join success. The control limits repetition of the described root condition: A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source. During audits, confirm: The RP learns the moved source and traffic begins flowing down the established receiver tree.
Incorrect Answers
A:Verify RP discovery and mapping on each receiver POP after configuration changes. This is a plausible preventive practice for a different IP Multicast condition, specifically PIM sparse RP mapping absent. PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over. In this scenario, however, the distinguishing issue is ASM shared-tree source loss and the confirming observation is: The RP learns the moved source and traffic begins flowing down the established receiver tree.
C:Test registered-source admission after group-range policy updates. This is a plausible preventive practice for a different IP Multicast condition, specifically ASM RP register suppression. RP register acceptance is a control-plane admission point separate from generic unicast route filtering. In this scenario, however, the distinguishing issue is ASM shared-tree source loss and the confirming observation is: The RP learns the moved source and traffic begins flowing down the established receiver tree.
D:Maintain a documented multicast addressing and receiver protocol matrix. This is a plausible preventive practice for a different IP Multicast condition, specifically Multicast group range mismatch. Multicast source-specific versus any-source behavior is selected by group range and configuration policy. In this scenario, however, the distinguishing issue is ASM shared-tree source loss and the confirming observation is: The RP learns the moved source and traffic begins flowing down the established receiver tree.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests