Question 630
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: Static RP configuration was removed but the network cannot discover the new RP because bootstrap-router advertisements fail to reach remote routers. Which operational control would best prevent a recurrence of this exact failure mode?
- Track RP loopback availability from each multicast island.
- Check RP mapping consistency in multiple POPs after BSR changes.
- Include distant-hop TTL validation in multicast application deployment.
- Test failover for duplicate packets as well as packet loss.
Explanation
Correct Answer
B:Check RP mapping consistency in multiple POPs after BSR changes. The control limits repetition of the described root condition: Bootstrap-based PIM RP discovery depends on successful propagation of candidate and bootstrap information. During audits, confirm: Remote routers independently show the same expected RP mapping for the affected multicast group.
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 BSR elected RP and the confirming observation is: Remote routers independently show the same expected RP mapping for the affected multicast group.
C:Include distant-hop TTL validation in multicast application deployment. This is a plausible preventive practice for a different IP Multicast condition, specifically Multicast TTL boundary. IP multicast forwarding still decrements TTL at routed hops; a packet can expire before distant receivers even with valid PIM state. In this scenario, however, the distinguishing issue is PIM BSR elected RP and the confirming observation is: Remote routers independently show the same expected RP mapping for the affected multicast group.
D:Test failover for duplicate packets as well as packet loss. This is a plausible preventive practice for a different IP Multicast condition, specifically Multicast packet duplicate delivery. A correct RPF distribution tree limits accepted incoming source interfaces; duplicates can indicate source duplication or inconsistent topology. In this scenario, however, the distinguishing issue is PIM BSR elected RP and the confirming observation is: Remote routers independently show the same expected RP mapping for the affected multicast group.
Question 631
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A dormant access branch receives recurring bursts of dense-mode multicast traffic even without interested receivers. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect source/group register filters and the offending DR's PIM register counters.
- Check querier presence, membership report refresh and snooping table expiration.
- Inspect PIM dense-mode prune and periodic reflood behavior on the branch.
- Compare source RPF route and actual incoming multicast interface using group and source forwarding state.
Explanation
Correct Answer
C:Inspect PIM dense-mode prune and periodic reflood behavior on the branch. This check examines the decisive condition for PIM dense-mode prune expiry before any unrelated changes are made. The underlying mechanism is: Dense mode may periodically refresh distribution and prune state, so temporary unwanted traffic can occur before pruning. The confirming observation is: Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver.
Incorrect Answers
A: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 PIM dense-mode prune expiry and the confirming observation is: Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver.
B:Check querier presence, membership report refresh and snooping table expiration. This is a plausible diagnostic check for a different IP Multicast condition, specifically IGMP snooping without querier. Snooping relies on IGMP control messages to learn receiver ports and preserve correct memberships. In this scenario, however, the distinguishing issue is PIM dense-mode prune expiry and the confirming observation is: Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver.
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 PIM dense-mode prune expiry and the confirming observation is: Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver.
Question 632
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A dormant access branch receives recurring bursts of dense-mode multicast traffic even without interested receivers. Which routing or service mechanism best explains the reported behavior?
- IP multicast forwarding still decrements TTL at routed hops; a packet can expire before distant receivers even with valid PIM state.
- RP register acceptance is a control-plane admission point separate from generic unicast route filtering.
- Snooping relies on IGMP control messages to learn receiver ports and preserve correct memberships.
- Dense mode may periodically refresh distribution and prune state, so temporary unwanted traffic can occur before pruning.
Explanation
Correct Answer
D:Dense mode may periodically refresh distribution and prune state, so temporary unwanted traffic can occur before pruning. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver. The targeted correction is: Select sparse mode when the service cannot tolerate periodic uninterested flooding.
Incorrect Answers
A:IP multicast forwarding still decrements TTL at routed hops; a packet can expire before distant receivers even with valid PIM state. This is a plausible protocol explanation for a different IP Multicast condition, specifically Multicast TTL boundary. IP multicast forwarding still decrements TTL at routed hops; a packet can expire before distant receivers even with valid PIM state. In this scenario, however, the distinguishing issue is PIM dense-mode prune expiry and the confirming observation is: Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver.
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 PIM dense-mode prune expiry and the confirming observation is: Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver.
C:Snooping relies on IGMP control messages to learn receiver ports and preserve correct memberships. This is a plausible protocol explanation for a different IP Multicast condition, specifically IGMP snooping without querier. Snooping relies on IGMP control messages to learn receiver ports and preserve correct memberships. In this scenario, however, the distinguishing issue is PIM dense-mode prune expiry and the confirming observation is: Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver.
Question 633
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A dormant access branch receives recurring bursts of dense-mode multicast traffic even without interested receivers. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver.
- Distant receivers obtain packets with a validated TTL budget and no TTL-expired counter growth.
- The RP rejects unauthorized register sources while approved sources still establish traffic.
- The querier drives reports and only subscribed ports remain in the multicast forwarding list.
Explanation
Correct Answer
A:Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Dense mode may periodically refresh distribution and prune state, so temporary unwanted traffic can occur before pruning.
Incorrect Answers
B:Distant receivers obtain packets with a validated TTL budget and no TTL-expired counter growth. This is a plausible observed evidence for a different IP Multicast condition, specifically Multicast TTL boundary. IP multicast forwarding still decrements TTL at routed hops; a packet can expire before distant receivers even with valid PIM state. In this scenario, however, the distinguishing issue is PIM dense-mode prune expiry and the confirming observation is: Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver.
C: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 PIM dense-mode prune expiry and the confirming observation is: Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver.
D:The querier drives reports and only subscribed ports remain in the multicast forwarding list. This is a plausible observed evidence for a different IP Multicast condition, specifically IGMP snooping without querier. Snooping relies on IGMP control messages to learn receiver ports and preserve correct memberships. In this scenario, however, the distinguishing issue is PIM dense-mode prune expiry and the confirming observation is: Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver.
Question 634
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A dormant access branch receives recurring bursts of dense-mode multicast traffic even without interested receivers. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Set an appropriate application TTL under security policy and keep unwanted distribution boundaries explicit.
- Select sparse mode when the service cannot tolerate periodic uninterested flooding.
- Apply a targeted register policy for the permitted source and group scope.
- Restore a supported IGMP querier on the affected VLAN and verify snooping state.
Explanation
Correct Answer
B:Select sparse mode when the service cannot tolerate periodic uninterested flooding. The change addresses the root behavior described here: Dense mode may periodically refresh distribution and prune state, so temporary unwanted traffic can occur before pruning. Verify success with: Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver.
Incorrect Answers
A:Set an appropriate application TTL under security policy and keep unwanted distribution boundaries explicit. This is a plausible configuration or operational fix for a different IP Multicast condition, specifically Multicast TTL boundary. IP multicast forwarding still decrements TTL at routed hops; a packet can expire before distant receivers even with valid PIM state. In this scenario, however, the distinguishing issue is PIM dense-mode prune expiry and the confirming observation is: Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver.
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 PIM dense-mode prune expiry and the confirming observation is: Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver.
D:Restore a supported IGMP querier on the affected VLAN and verify snooping state. This is a plausible configuration or operational fix for a different IP Multicast condition, specifically IGMP snooping without querier. Snooping relies on IGMP control messages to learn receiver ports and preserve correct memberships. In this scenario, however, the distinguishing issue is PIM dense-mode prune expiry and the confirming observation is: Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver.
Question 635
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: A dormant access branch receives recurring bursts of dense-mode multicast traffic even without interested receivers. Which operational control would best prevent a recurrence of this exact failure mode?
- Monitor membership table ages during endpoint power-save and VLAN changes.
- Include distant-hop TTL validation in multicast application deployment.
- Compare observed branch load against actual subscriber distribution before accepting dense mode.
- Test registered-source admission after group-range policy updates.
Explanation
Correct Answer
C:Compare observed branch load against actual subscriber distribution before accepting dense mode. The control limits repetition of the described root condition: Dense mode may periodically refresh distribution and prune state, so temporary unwanted traffic can occur before pruning. During audits, confirm: Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver.
Incorrect Answers
A:Monitor membership table ages during endpoint power-save and VLAN changes. This is a plausible preventive practice for a different IP Multicast condition, specifically IGMP membership aging. Last-hop multicast forwarding depends on maintained group membership; missing queries or membership reports can allow entries to expire. In this scenario, however, the distinguishing issue is PIM dense-mode prune expiry and the confirming observation is: Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver.
B:Include distant-hop TTL validation in multicast application deployment. This is a plausible preventive practice for a different IP Multicast condition, specifically Multicast TTL boundary. IP multicast forwarding still decrements TTL at routed hops; a packet can expire before distant receivers even with valid PIM state. In this scenario, however, the distinguishing issue is PIM dense-mode prune expiry and the confirming observation is: Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver.
D: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 PIM dense-mode prune expiry and the confirming observation is: Observed flooding aligns with dense-mode refresh behavior instead of indicating a new receiver.
Question 636
During a backbone POP acceptance review, 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 targeted check most directly distinguishes the likely cause before a configuration change?
- 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.
- Inspect IGMP version and whether the host can express source filters.
- Compare intended SSM group-range policy against actual application destinations.
Explanation
Correct Answer
D:Compare intended SSM group-range policy against actual application destinations. This check examines the decisive condition for Multicast group range mismatch before any unrelated changes are made. The underlying mechanism is: Multicast source-specific versus any-source behavior is selected by group range and configuration policy. The confirming observation is: The application uses a supported SSM group and receivers issue source-aware joins as designed.
Incorrect Answers
A: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 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: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 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: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 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 637
During an overnight NOC investigation, 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 routing or service mechanism best explains the reported behavior?
- Multicast source-specific versus any-source behavior is selected by group range and configuration policy.
- A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source.
- RP register acceptance is a control-plane admission point separate from generic unicast route filtering.
- Native IGMPv3 carries source-specific membership information required for straightforward IPv4 SSM subscriptions.
Explanation
Correct Answer
A:Multicast source-specific versus any-source behavior is selected by group range and configuration policy. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The application uses a supported SSM group and receivers issue source-aware joins as designed. The targeted correction is: Align application group addresses and network SSM range mapping.
Incorrect Answers
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 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: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 Multicast group range mismatch and the confirming observation is: The application uses a supported SSM group and receivers issue source-aware joins as designed.
D: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 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 638
During a customer service restoration, 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. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The RP learns the moved source and traffic begins flowing down the established receiver tree.
- The application uses a supported SSM group and receivers issue source-aware joins as designed.
- The RP rejects unauthorized register sources while approved sources still establish traffic.
- An IGMPv3 (S,G) membership entry appears for the intended source and group.
Explanation
Correct Answer
B:The application uses a supported SSM group and receivers issue source-aware joins as designed. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Multicast source-specific versus any-source behavior is selected by group range and configuration policy.
Incorrect Answers
A: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 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: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 Multicast group range mismatch and the confirming observation is: The application uses a supported SSM group and receivers issue source-aware joins as designed.
D: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 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 639
During an edge-to-core 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 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.
- Apply a targeted register policy for the permitted source and group scope.
- Align application group addresses and network SSM range mapping.
- Upgrade the receiver to IGMPv3 or use an approved SSM mapping solution where supported.
Explanation
Correct Answer
C:Align application group addresses and network SSM range mapping. The change addresses the root behavior described here: Multicast source-specific versus any-source behavior is selected by group range and configuration policy. Verify success with: The application uses a supported SSM group and receivers issue source-aware joins as designed.
Incorrect Answers
A: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 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: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 Multicast group range mismatch and the confirming observation is: The application uses a supported SSM group and receivers issue source-aware joins as designed.
D: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 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 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.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests