Question 640
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: A team deploys SSM for one multicast range but applications use a different ASM group range, causing source-specific joins to be treated inconsistently. Which operational control would best prevent a recurrence of this exact failure mode?
- Test source failover and relocation independently of receiver join success.
- Test registered-source admission after group-range policy updates.
- Check IGMP source-filter capability before migrating a group range to SSM.
- Maintain a documented multicast addressing and receiver protocol matrix.
Explanation
Correct Answer
D:Maintain a documented multicast addressing and receiver protocol matrix. The control limits repetition of the described root condition: Multicast source-specific versus any-source behavior is selected by group range and configuration policy. During audits, confirm: The application uses a supported SSM group and receivers issue source-aware joins as designed.
Incorrect Answers
A: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 Multicast group range mismatch and the confirming observation is: The application uses a supported SSM group and receivers issue source-aware joins as designed.
B: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 Multicast group range mismatch and the confirming observation is: The application uses a supported SSM group and receivers issue source-aware joins as designed.
C:Check IGMP source-filter capability before migrating a group range to SSM. This is a plausible preventive practice for a different IP Multicast condition, specifically IGMPv2 limitations for SSM. Native IGMPv3 carries source-specific membership information required for straightforward IPv4 SSM subscriptions. In this scenario, however, the distinguishing issue is Multicast group range mismatch and the confirming observation is: The application uses a supported SSM group and receivers issue source-aware joins as designed.
Question 641
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: Multicast streams stopped after an IGP cost adjustment even though unicast traffic still reaches the server through a different path. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect the unicast best route toward each source and the multicast packet ingress interface after the metric change.
- Inspect source/group register filters and the offending DR's PIM register counters.
- Inspect multicast RPF table selection and the approved source routing policy.
- Compare source RPF route and actual incoming multicast interface using group and source forwarding state.
Explanation
Correct Answer
A:Inspect the unicast best route toward each source and the multicast packet ingress interface after the metric change. This check examines the decisive condition for RPF asymmetry after IGP cost change before any unrelated changes are made. The underlying mechanism is: An IGP change can alter RPF selection, invalidating multicast arriving on an old interface even when unicast service succeeds. The confirming observation is: The multicast source ingress matches current RPF route selection and forwarding resumes.
Incorrect Answers
B: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 RPF asymmetry after IGP cost change and the confirming observation is: The multicast source ingress matches current RPF route selection and forwarding resumes.
C:Inspect multicast RPF table selection and the approved source routing policy. This is a plausible diagnostic check for a different IP Multicast condition, specifically Multicast RPF policy separation. Multicast RPF may use explicitly controlled multicast routing information where Junos supports separate RPF lookup. In this scenario, however, the distinguishing issue is RPF asymmetry after IGP cost change and the confirming observation is: The multicast source ingress matches current RPF route selection and forwarding resumes.
D: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 RPF asymmetry after IGP cost change and the confirming observation is: The multicast source ingress matches current RPF route selection and forwarding resumes.
Question 642
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: Multicast streams stopped after an IGP cost adjustment even though unicast traffic still reaches the server through a different path. Which routing or service mechanism best explains the reported behavior?
- Multicast RPF may use explicitly controlled multicast routing information where Junos supports separate RPF lookup.
- An IGP change can alter RPF selection, invalidating multicast arriving on an old interface even when unicast service succeeds.
- RP register acceptance is a control-plane admission point separate from generic unicast route filtering.
- Reverse-path forwarding rejects traffic received away from the interface selected as the path toward the multicast source.
Explanation
Correct Answer
B:An IGP change can alter RPF selection, invalidating multicast arriving on an old interface even when unicast service succeeds. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The multicast source ingress matches current RPF route selection and forwarding resumes. The targeted correction is: Correct multicast path placement or source RPF design to agree with the intended unicast topology.
Incorrect Answers
A:Multicast RPF may use explicitly controlled multicast routing information where Junos supports separate RPF lookup. This is a plausible protocol explanation for a different IP Multicast condition, specifically Multicast RPF policy separation. Multicast RPF may use explicitly controlled multicast routing information where Junos supports separate RPF lookup. In this scenario, however, the distinguishing issue is RPF asymmetry after IGP cost change and the confirming observation is: The multicast source ingress matches current RPF route selection and forwarding resumes.
C: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 RPF asymmetry after IGP cost change and the confirming observation is: The multicast source ingress matches current RPF route selection and forwarding resumes.
D: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 RPF asymmetry after IGP cost change and the confirming observation is: The multicast source ingress matches current RPF route selection and forwarding resumes.
Question 643
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: Multicast streams stopped after an IGP cost adjustment even though unicast traffic still reaches the server through a different path. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The configured RPF selection points to the intended valid upstream interface without disturbing ordinary unicast forwarding.
- The RP rejects unauthorized register sources while approved sources still establish traffic.
- 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.
Explanation
Correct Answer
C:The multicast source ingress matches current RPF route selection and forwarding resumes. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: An IGP change can alter RPF selection, invalidating multicast arriving on an old interface even when unicast service succeeds.
Incorrect Answers
A:The configured RPF selection points to the intended valid upstream interface without disturbing ordinary unicast forwarding. This is a plausible observed evidence for a different IP Multicast condition, specifically Multicast RPF policy separation. Multicast RPF may use explicitly controlled multicast routing information where Junos supports separate RPF lookup. In this scenario, however, the distinguishing issue is RPF asymmetry after IGP cost change and the confirming observation is: The multicast source ingress matches current RPF route selection and forwarding resumes.
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 RPF asymmetry after IGP cost change and the confirming observation is: The multicast source ingress matches current RPF route selection and forwarding resumes.
D: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 RPF asymmetry after IGP cost change and the confirming observation is: The multicast source ingress matches current RPF route selection and forwarding resumes.
Question 644
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: Multicast streams stopped after an IGP cost adjustment even though unicast traffic still reaches the server through a different path. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Implement a supported source-specific RPF control only when justified and tested.
- Apply a targeted register policy for the permitted source and group scope.
- Correct source reachability, RPF policy or topology so valid multicast traffic arrives on the selected RPF interface.
- Correct multicast path placement or source RPF design to agree with the intended unicast topology.
Explanation
Correct Answer
D:Correct multicast path placement or source RPF design to agree with the intended unicast topology. The change addresses the root behavior described here: An IGP change can alter RPF selection, invalidating multicast arriving on an old interface even when unicast service succeeds. Verify success with: The multicast source ingress matches current RPF route selection and forwarding resumes.
Incorrect Answers
A:Implement a supported source-specific RPF control only when justified and tested. This is a plausible configuration or operational fix for a different IP Multicast condition, specifically Multicast RPF policy separation. Multicast RPF may use explicitly controlled multicast routing information where Junos supports separate RPF lookup. In this scenario, however, the distinguishing issue is RPF asymmetry after IGP cost change and the confirming observation is: The multicast source ingress matches current RPF route selection and forwarding resumes.
B: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 RPF asymmetry after IGP cost change and the confirming observation is: The multicast source ingress matches current RPF route selection and forwarding resumes.
C: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 RPF asymmetry after IGP cost change and the confirming observation is: The multicast source ingress matches current RPF route selection and forwarding resumes.
Question 645
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: Multicast streams stopped after an IGP cost adjustment even though unicast traffic still reaches the server through a different path. Which operational control would best prevent a recurrence of this exact failure mode?
- Include multicast RPF tests in every core metric migration.
- Audit multicast and unicast route tables independently during asymmetric routing changes.
- Test registered-source admission after group-range policy updates.
- Audit RPF path changes whenever unicast routing policy changes.
Explanation
Correct Answer
A:Include multicast RPF tests in every core metric migration. The control limits repetition of the described root condition: An IGP change can alter RPF selection, invalidating multicast arriving on an old interface even when unicast service succeeds. During audits, confirm: The multicast source ingress matches current RPF route selection and forwarding resumes.
Incorrect Answers
B:Audit multicast and unicast route tables independently during asymmetric routing changes. This is a plausible preventive practice for a different IP Multicast condition, specifically Multicast RPF policy separation. Multicast RPF may use explicitly controlled multicast routing information where Junos supports separate RPF lookup. In this scenario, however, the distinguishing issue is RPF asymmetry after IGP cost change and the confirming observation is: The multicast source ingress matches current RPF route selection and forwarding resumes.
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 RPF asymmetry after IGP cost change and the confirming observation is: The multicast source ingress matches current RPF route selection and forwarding resumes.
D: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 RPF asymmetry after IGP cost change and the confirming observation is: The multicast source ingress matches current RPF route selection and forwarding resumes.
Question 646
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: A receiver's source-specific subscription names the wrong source IPv4 address; group state exists but no traffic arrives. 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 IGMPv3 included source address and the actual content server's source IP.
- Inspect source DR registration and RP source-state updates separately from receiver joins.
- Inspect IGMP version and whether the host can express source filters.
Explanation
Correct Answer
B:Inspect IGMPv3 included source address and the actual content server's source IP. This check examines the decisive condition for SSM source address typo before any unrelated changes are made. The underlying mechanism is: SSM membership is bound to a source and group pair; membership for the wrong source does not authorize the actual source stream. The confirming observation is: The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface.
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 SSM source address typo and the confirming observation is: The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface.
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 SSM source address typo and the confirming observation is: The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface.
D:Inspect IGMP version and whether the host can express source filters. This is a plausible diagnostic check for a different IP Multicast condition, specifically IGMPv2 limitations for SSM. Native IGMPv3 carries source-specific membership information required for straightforward IPv4 SSM subscriptions. In this scenario, however, the distinguishing issue is SSM source address typo and the confirming observation is: The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface.
Question 647
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: A receiver's source-specific subscription names the wrong source IPv4 address; group state exists but no traffic arrives. 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.
- Native IGMPv3 carries source-specific membership information required for straightforward IPv4 SSM subscriptions.
- SSM membership is bound to a source and group pair; membership for the wrong source does not authorize the actual source stream.
- A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source.
Explanation
Correct Answer
C:SSM membership is bound to a source and group pair; membership for the wrong source does not authorize the actual source stream. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface. The targeted correction is: Correct the source address in the subscription or authorized SSM mapping.
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 SSM source address typo and the confirming observation is: The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface.
B:Native IGMPv3 carries source-specific membership information required for straightforward IPv4 SSM subscriptions. This is a plausible protocol explanation for a different IP Multicast condition, specifically IGMPv2 limitations for SSM. Native IGMPv3 carries source-specific membership information required for straightforward IPv4 SSM subscriptions. In this scenario, however, the distinguishing issue is SSM source address typo and the confirming observation is: The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface.
D: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 SSM source address typo and the confirming observation is: The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface.
Question 648
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: A receiver's source-specific subscription names the wrong source IPv4 address; group state exists but no traffic arrives. 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.
- An IGMPv3 (S,G) membership entry appears for the intended source and group.
- The RP learns the moved source and traffic begins flowing down the established receiver tree.
- The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface.
Explanation
Correct Answer
D:The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: SSM membership is bound to a source and group pair; membership for the wrong source does not authorize the actual source stream.
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 SSM source address typo and the confirming observation is: The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface.
B:An IGMPv3 (S,G) membership entry appears for the intended source and group. This is a plausible observed evidence for a different IP Multicast condition, specifically IGMPv2 limitations for SSM. Native IGMPv3 carries source-specific membership information required for straightforward IPv4 SSM subscriptions. In this scenario, however, the distinguishing issue is SSM source address typo and the confirming observation is: The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface.
C: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 SSM source address typo and the confirming observation is: The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface.
Question 649
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: A receiver's source-specific subscription names the wrong source IPv4 address; group state exists but no traffic arrives. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Correct the source address in the subscription or authorized SSM mapping.
- Restore the IGP or static route to the RP address instead of changing receiver group membership.
- Upgrade the receiver to IGMPv3 or use an approved SSM mapping solution where supported.
- Correct the source DR and RP discovery path without rebuilding healthy downstream joins.
Explanation
Correct Answer
A:Correct the source address in the subscription or authorized SSM mapping. The change addresses the root behavior described here: SSM membership is bound to a source and group pair; membership for the wrong source does not authorize the actual source stream. Verify success with: The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface.
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 SSM source address typo and the confirming observation is: The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface.
C:Upgrade the receiver to IGMPv3 or use an approved SSM mapping solution where supported. This is a plausible configuration or operational fix for a different IP Multicast condition, specifically IGMPv2 limitations for SSM. Native IGMPv3 carries source-specific membership information required for straightforward IPv4 SSM subscriptions. In this scenario, however, the distinguishing issue is SSM source address typo and the confirming observation is: The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface.
D: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 SSM source address typo and the confirming observation is: The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface.
Question 650
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: A receiver's source-specific subscription names the wrong source IPv4 address; group state exists but no traffic arrives. Which operational control would best prevent a recurrence of this exact failure mode?
- Track RP loopback availability from each multicast island.
- Validate channel source and group pairs from the application inventory.
- Check IGMP source-filter capability before migrating a group range to SSM.
- Test source failover and relocation independently of receiver join success.
Explanation
Correct Answer
B:Validate channel source and group pairs from the application inventory. The control limits repetition of the described root condition: SSM membership is bound to a source and group pair; membership for the wrong source does not authorize the actual source stream. During audits, confirm: The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface.
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 SSM source address typo and the confirming observation is: The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface.
C:Check IGMP source-filter capability before migrating a group range to SSM. This is a plausible preventive practice for a different IP Multicast condition, specifically IGMPv2 limitations for SSM. Native IGMPv3 carries source-specific membership information required for straightforward IPv4 SSM subscriptions. In this scenario, however, the distinguishing issue is SSM source address typo and the confirming observation is: The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface.
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 SSM source address typo and the confirming observation is: The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests