Question 590
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: An access network with few multicast subscribers experiences unnecessary initial multicast flooding because PIM dense mode is enabled across every branch. Which operational control would best prevent a recurrence of this exact failure mode?
- Include querier availability in access VLAN multicast acceptance tests.
- Measure uninterested branch traffic before choosing multicast operating mode.
- Monitor outgoing-interface lists alongside source packet counters.
- Monitor membership table ages during endpoint power-save and VLAN changes.
Explanation
Correct Answer
B:Measure uninterested branch traffic before choosing multicast operating mode. The control limits repetition of the described root condition: Dense mode initially floods along branches and prunes uninterested segments, unlike sparse mode's explicit interest model. During audits, confirm: Uninterested access links stop receiving unsolicited multicast when the service uses a suitable sparse design.
Incorrect Answers
A:Include querier availability in access VLAN multicast acceptance tests. This is a plausible preventive practice 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 Dense-mode flood and prune and the confirming observation is: Uninterested access links stop receiving unsolicited multicast when the service uses a suitable sparse design.
C: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 Dense-mode flood and prune and the confirming observation is: Uninterested access links stop receiving unsolicited multicast when the service uses a suitable sparse design.
D: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 Dense-mode flood and prune and the confirming observation is: Uninterested access links stop receiving unsolicited multicast when the service uses a suitable sparse design.
Question 591
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: The first-hop router and last-hop router run PIM correctly, but one intermediate core hop has no PIM participation and multicast tree state stops there. 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 PIM neighbor and join state at each transit interface along the RPF path.
- Check querier presence, membership report refresh and snooping table expiration.
Explanation
Correct Answer
C:Inspect PIM neighbor and join state at each transit interface along the RPF path. This check examines the decisive condition for Missing PIM on transit before any unrelated changes are made. The underlying mechanism is: Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path. The confirming observation is: PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP.
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 Missing PIM on transit and the confirming observation is: PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP.
B: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 Missing PIM on transit and the confirming observation is: PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP.
D: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 Missing PIM on transit and the confirming observation is: PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP.
Question 592
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: The first-hop router and last-hop router run PIM correctly, but one intermediate core hop has no PIM participation and multicast tree state stops there. 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.
- A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source.
- Snooping relies on IGMP control messages to learn receiver ports and preserve correct memberships.
- Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path.
Explanation
Correct Answer
D:Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP. The targeted correction is: Enable the intended multicast routing protocol on all required transit interfaces.
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 Missing PIM on transit and the confirming observation is: PIM neighbor state and join entries traverse the intermediate hop to reach the source or 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 Missing PIM on transit and the confirming observation is: PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP.
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 Missing PIM on transit and the confirming observation is: PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP.
Question 593
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: The first-hop router and last-hop router run PIM correctly, but one intermediate core hop has no PIM participation and multicast tree state stops there. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- 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.
- The RP learns the moved source and traffic begins flowing down the established receiver tree.
- The querier drives reports and only subscribed ports remain in the multicast forwarding list.
Explanation
Correct Answer
A:PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path.
Incorrect Answers
B: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 Missing PIM on transit and the confirming observation is: PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP.
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 Missing PIM on transit and the confirming observation is: PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP.
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 Missing PIM on transit and the confirming observation is: PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP.
Question 594
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: The first-hop router and last-hop router run PIM correctly, but one intermediate core hop has no PIM participation and multicast tree state stops there. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Configure an appropriate reachable RP mapping for the group range.
- Enable the intended multicast routing protocol on all required transit interfaces.
- Correct the source DR and RP discovery path without rebuilding healthy downstream joins.
- Restore a supported IGMP querier on the affected VLAN and verify snooping state.
Explanation
Correct Answer
B:Enable the intended multicast routing protocol on all required transit interfaces. The change addresses the root behavior described here: Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path. Verify success with: PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP.
Incorrect Answers
A: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 Missing PIM on transit and the confirming observation is: PIM neighbor state and join entries traverse the intermediate hop to reach the source or 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 Missing PIM on transit and the confirming observation is: PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP.
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 Missing PIM on transit and the confirming observation is: PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP.
Question 595
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: The first-hop router and last-hop router run PIM correctly, but one intermediate core hop has no PIM participation and multicast tree state stops there. 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.
- Trace every hop's group state before modifying endpoint subscriptions.
- Include querier availability in access VLAN multicast acceptance tests.
Explanation
Correct Answer
C:Trace every hop's group state before modifying endpoint subscriptions. The control limits repetition of the described root condition: Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path. During audits, confirm: PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP.
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 Missing PIM on transit and the confirming observation is: PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP.
B: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 Missing PIM on transit and the confirming observation is: PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP.
D:Include querier availability in access VLAN multicast acceptance tests. This is a plausible preventive practice 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 Missing PIM on transit and the confirming observation is: PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP.
Question 596
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: A receiver's multicast application stops periodically when its access switch or router ages out group membership despite continuing source transmissions. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect IGMP version and whether the host can express source filters.
- Inspect RPF validation, PIM joins and whether duplicate streams originate upstream rather than from routing itself.
- Inspect (S,G) state and the router's RP-tree-to-SPT transition settings.
- Inspect last-hop IGMP query and report counters plus membership timers.
Explanation
Correct Answer
D:Inspect last-hop IGMP query and report counters plus membership timers. This check examines the decisive condition for IGMP membership aging before any unrelated changes are made. The underlying mechanism is: Last-hop multicast forwarding depends on maintained group membership; missing queries or membership reports can allow entries to expire. The confirming observation is: The receiver group membership persists through several query cycles and traffic remains delivered.
Incorrect Answers
A: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 IGMP membership aging and the confirming observation is: The receiver group membership persists through several query cycles and traffic remains delivered.
B:Inspect RPF validation, PIM joins and whether duplicate streams originate upstream rather than from routing itself. This is a plausible diagnostic check 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 IGMP membership aging and the confirming observation is: The receiver group membership persists through several query cycles and traffic remains delivered.
C:Inspect (S,G) state and the router's RP-tree-to-SPT transition settings. This is a plausible diagnostic check 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 IGMP membership aging and the confirming observation is: The receiver group membership persists through several query cycles and traffic remains delivered.
Question 597
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A receiver's multicast application stops periodically when its access switch or router ages out group membership despite continuing source transmissions. Which routing or service mechanism best explains the reported behavior?
- Last-hop multicast forwarding depends on maintained group membership; missing queries or membership reports can allow entries to expire.
- Native IGMPv3 carries source-specific membership information required for straightforward IPv4 SSM subscriptions.
- A passing RPF check does not create downstream delivery without an interested outgoing interface.
- A correct RPF distribution tree limits accepted incoming source interfaces; duplicates can indicate source duplication or inconsistent topology.
Explanation
Correct Answer
A:Last-hop multicast forwarding depends on maintained group membership; missing queries or membership reports can allow entries to expire. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The receiver group membership persists through several query cycles and traffic remains delivered. The targeted correction is: Restore consistent IGMP querier behavior and receiver report processing.
Incorrect Answers
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 IGMP membership aging and the confirming observation is: The receiver group membership persists through several query cycles and traffic remains delivered.
C: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 IGMP membership aging and the confirming observation is: The receiver group membership persists through several query cycles and traffic remains delivered.
D:A correct RPF distribution tree limits accepted incoming source interfaces; duplicates can indicate source duplication or inconsistent topology. This is a plausible protocol explanation 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 IGMP membership aging and the confirming observation is: The receiver group membership persists through several query cycles and traffic remains delivered.
Question 598
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A receiver's multicast application stops periodically when its access switch or router ages out group membership despite continuing source transmissions. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- An IGMPv3 (S,G) membership entry appears for the intended source and group.
- The receiver group membership persists through several query cycles and traffic remains delivered.
- The RP learns the moved source and traffic begins flowing down the established receiver tree.
- A packet capture and forwarding state identify a single accepted (S,G) stream on the intended path.
Explanation
Correct Answer
B:The receiver group membership persists through several query cycles and traffic remains delivered. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Last-hop multicast forwarding depends on maintained group membership; missing queries or membership reports can allow entries to expire.
Incorrect Answers
A: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 IGMP membership aging and the confirming observation is: The receiver group membership persists through several query cycles and traffic remains delivered.
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 IGMP membership aging and the confirming observation is: The receiver group membership persists through several query cycles and traffic remains delivered.
D:A packet capture and forwarding state identify a single accepted (S,G) stream on the intended path. This is a plausible observed evidence 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 IGMP membership aging and the confirming observation is: The receiver group membership persists through several query cycles and traffic remains delivered.
Question 599
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A receiver's multicast application stops periodically when its access switch or router ages out group membership despite continuing source transmissions. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Upgrade the receiver to IGMPv3 or use an approved SSM mapping solution where supported.
- Repair IGMP last-hop membership or PIM downstream join signaling.
- Restore consistent IGMP querier behavior and receiver report processing.
- Correct the source DR and RP discovery path without rebuilding healthy downstream joins.
Explanation
Correct Answer
C:Restore consistent IGMP querier behavior and receiver report processing. The change addresses the root behavior described here: Last-hop multicast forwarding depends on maintained group membership; missing queries or membership reports can allow entries to expire. Verify success with: The receiver group membership persists through several query cycles and traffic remains delivered.
Incorrect Answers
A: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 IGMP membership aging and the confirming observation is: The receiver group membership persists through several query cycles and traffic remains delivered.
B: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 IGMP membership aging and the confirming observation is: The receiver group membership persists through several query cycles and traffic remains delivered.
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 IGMP membership aging and the confirming observation is: The receiver group membership persists through several query cycles and traffic remains delivered.
Question 600
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A receiver's multicast application stops periodically when its access switch or router ages out group membership despite continuing source transmissions. Which operational control would best prevent a recurrence of this exact failure mode?
- Check IGMP source-filter capability before migrating a group range to SSM.
- Monitor outgoing-interface lists alongside source packet counters.
- Test source failover and relocation independently of receiver join success.
- Monitor membership table ages during endpoint power-save and VLAN changes.
Explanation
Correct Answer
D:Monitor membership table ages during endpoint power-save and VLAN changes. The control limits repetition of the described root condition: Last-hop multicast forwarding depends on maintained group membership; missing queries or membership reports can allow entries to expire. During audits, confirm: The receiver group membership persists through several query cycles and traffic remains delivered.
Incorrect Answers
A: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 IGMP membership aging and the confirming observation is: The receiver group membership persists through several query cycles and traffic remains delivered.
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 IGMP membership aging and the confirming observation is: The receiver group membership persists through several query cycles and traffic remains delivered.
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 IGMP membership aging and the confirming observation is: The receiver group membership persists through several query cycles and traffic remains delivered.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests