Question 570
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: Receivers join an ASM multicast group but no shared tree develops because the last-hop router cannot determine an RP for that group. Which operational control would best prevent a recurrence of this exact failure mode?
- Track RP loopback availability from each multicast island.
- Verify RP discovery and mapping on each receiver POP after configuration changes.
- Test source failover and relocation independently of receiver join success.
- Trace every hop's group state before modifying endpoint subscriptions.
Explanation
Correct Answer
B:Verify RP discovery and mapping on each receiver POP after configuration changes. The control limits repetition of the described root condition: PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over. During audits, confirm: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
Incorrect Answers
A:Track RP loopback availability from each multicast island. This is a plausible preventive practice for a different IP Multicast condition, specifically RP unreachable by unicast. PIM joins are sent toward the RP using unicast-derived RPF paths; a configured RP with no route is not usable. In this scenario, however, the distinguishing issue is PIM sparse RP mapping absent and the confirming observation is: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
C:Test source failover and relocation independently of receiver join success. This is a plausible preventive practice for a different IP Multicast condition, specifically ASM shared-tree source loss. A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source. In this scenario, however, the distinguishing issue is PIM sparse RP mapping absent and the confirming observation is: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
D:Trace every hop's group state before modifying endpoint subscriptions. This is a plausible preventive practice for a different IP Multicast condition, specifically Missing PIM on transit. Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path. In this scenario, however, the distinguishing issue is PIM sparse RP mapping absent and the confirming observation is: A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
Question 571
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: A newly connected ASM source emits traffic but the RP never learns it because its first-hop designated router fails to register the source. 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 PIM neighbor and join state at each transit interface along the RPF path.
- Inspect PIM register behavior and source-DR relationship to the configured RP.
- Inspect multicast RPF table selection and the approved source routing policy.
Explanation
Correct Answer
C:Inspect PIM register behavior and source-DR relationship to the configured RP. This check examines the decisive condition for ASM register from source DR before any unrelated changes are made. The underlying mechanism is: PIM sparse mode source discovery can require the first-hop DR to register a source with the RP for ASM distribution. The confirming observation is: The RP receives expected source information and starts delivering data to interested shared-tree receivers.
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 ASM register from source DR and the confirming observation is: The RP receives expected source information and starts delivering data to interested shared-tree receivers.
B:Inspect PIM neighbor and join state at each transit interface along the RPF path. This is a plausible diagnostic check for a different IP Multicast condition, specifically Missing PIM on transit. Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path. In this scenario, however, the distinguishing issue is ASM register from source DR and the confirming observation is: The RP receives expected source information and starts delivering data to interested shared-tree receivers.
D: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 ASM register from source DR and the confirming observation is: The RP receives expected source information and starts delivering data to interested shared-tree receivers.
Question 572
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: A newly connected ASM source emits traffic but the RP never learns it because its first-hop designated router fails to register the source. Which routing or service mechanism best explains the reported behavior?
- A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source.
- Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path.
- A passing RPF check does not create downstream delivery without an interested outgoing interface.
- PIM sparse mode source discovery can require the first-hop DR to register a source with the RP for ASM distribution.
Explanation
Correct Answer
D:PIM sparse mode source discovery can require the first-hop DR to register a source with the RP for ASM distribution. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The RP receives expected source information and starts delivering data to interested shared-tree receivers. The targeted correction is: Restore source DR register delivery and the source-to-RP unicast and PIM path.
Incorrect Answers
A: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 ASM register from source DR and the confirming observation is: The RP receives expected source information and starts delivering data to interested shared-tree receivers.
B:Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path. This is a plausible protocol explanation for a different IP Multicast condition, specifically Missing PIM on transit. Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path. In this scenario, however, the distinguishing issue is ASM register from source DR and the confirming observation is: The RP receives expected source information and starts delivering data to interested shared-tree receivers.
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 ASM register from source DR and the confirming observation is: The RP receives expected source information and starts delivering data to interested shared-tree receivers.
Question 573
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: A newly connected ASM source emits traffic but the RP never learns it because its first-hop designated router fails to register the source. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The RP receives expected source information and starts delivering data to interested shared-tree receivers.
- The RP learns the moved source and traffic begins flowing down the established receiver tree.
- PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP.
- The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface.
Explanation
Correct Answer
A:The RP receives expected source information and starts delivering data to interested shared-tree receivers. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: PIM sparse mode source discovery can require the first-hop DR to register a source with the RP for ASM distribution.
Incorrect Answers
B:The RP learns the moved source and traffic begins flowing down the established receiver tree. This is a plausible observed evidence for a different IP Multicast condition, specifically ASM shared-tree source loss. A healthy receiver shared tree does not prove the RP has discovered a currently active ASM source. In this scenario, however, the distinguishing issue is ASM register from source DR and the confirming observation is: The RP receives expected source information and starts delivering data to interested shared-tree receivers.
C:PIM neighbor state and join entries traverse the intermediate hop to reach the source or RP. This is a plausible observed evidence for a different IP Multicast condition, specifically Missing PIM on transit. Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path. In this scenario, however, the distinguishing issue is ASM register from source DR and the confirming observation is: The RP receives expected source information and starts delivering data to interested shared-tree receivers.
D:The IGMP (S,G) entry matches the active server's source and packets arrive through the correct RPF interface. This is a plausible observed evidence for a different IP Multicast condition, specifically SSM source address typo. SSM membership is bound to a source and group pair; membership for the wrong source does not authorize the actual source stream. In this scenario, however, the distinguishing issue is ASM register from source DR and the confirming observation is: The RP receives expected source information and starts delivering data to interested shared-tree receivers.
Question 574
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: A newly connected ASM source emits traffic but the RP never learns it because its first-hop designated router fails to register the source. 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.
- Restore source DR register delivery and the source-to-RP unicast and PIM path.
- Enable the intended multicast routing protocol on all required transit interfaces.
- Correct the source address in the subscription or authorized SSM mapping.
Explanation
Correct Answer
B:Restore source DR register delivery and the source-to-RP unicast and PIM path. The change addresses the root behavior described here: PIM sparse mode source discovery can require the first-hop DR to register a source with the RP for ASM distribution. Verify success with: The RP receives expected source information and starts delivering data to interested shared-tree receivers.
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 ASM register from source DR and the confirming observation is: The RP receives expected source information and starts delivering data to interested shared-tree receivers.
C:Enable the intended multicast routing protocol on all required transit interfaces. This is a plausible configuration or operational fix for a different IP Multicast condition, specifically Missing PIM on transit. Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path. In this scenario, however, the distinguishing issue is ASM register from source DR and the confirming observation is: The RP receives expected source information and starts delivering data to interested shared-tree receivers.
D:Correct the source address in the subscription or authorized SSM mapping. This is a plausible configuration or operational fix for a different IP Multicast condition, specifically SSM source address typo. SSM membership is bound to a source and group pair; membership for the wrong source does not authorize the actual source stream. In this scenario, however, the distinguishing issue is ASM register from source DR and the confirming observation is: The RP receives expected source information and starts delivering data to interested shared-tree receivers.
Question 575
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A newly connected ASM source emits traffic but the RP never learns it because its first-hop designated router fails to register the source. Which operational control would best prevent a recurrence of this exact failure mode?
- Test source failover and relocation independently of receiver join success.
- Trace every hop's group state before modifying endpoint subscriptions.
- Test initial source discovery separately from steady-state multicast forwarding.
- Include multicast RPF tests in every core metric migration.
Explanation
Correct Answer
C:Test initial source discovery separately from steady-state multicast forwarding. The control limits repetition of the described root condition: PIM sparse mode source discovery can require the first-hop DR to register a source with the RP for ASM distribution. During audits, confirm: The RP receives expected source information and starts delivering data to interested shared-tree receivers.
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 ASM register from source DR and the confirming observation is: The RP receives expected source information and starts delivering data to interested shared-tree receivers.
B:Trace every hop's group state before modifying endpoint subscriptions. This is a plausible preventive practice for a different IP Multicast condition, specifically Missing PIM on transit. Multicast routing requires compatible upstream/downstream PIM signaling along the intended distribution path. In this scenario, however, the distinguishing issue is ASM register from source DR and the confirming observation is: The RP receives expected source information and starts delivering data to interested shared-tree receivers.
D:Include multicast RPF tests in every core metric migration. This is a plausible preventive practice for a different IP Multicast condition, specifically RPF asymmetry after IGP cost change. An IGP change can alter RPF selection, invalidating multicast arriving on an old interface even when unicast service succeeds. In this scenario, however, the distinguishing issue is ASM register from source DR and the confirming observation is: The RP receives expected source information and starts delivering data to interested shared-tree receivers.
Question 576
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A deployment uses IGMPv3 receivers requesting a specific source and group but engineers keep troubleshooting RP election as if it were ASM. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect IGMP version and whether the host can express source filters.
- Check RP address resolution and RPF route on every affected last-hop router.
- Inspect group-to-RP mapping and the PIM join state on receiver-facing and upstream routers.
- Verify SSM (S,G) receiver subscriptions and source reachability rather than searching for an RP.
Explanation
Correct Answer
D:Verify SSM (S,G) receiver subscriptions and source reachability rather than searching for an RP. This check examines the decisive condition for SSM RP unnecessary before any unrelated changes are made. The underlying mechanism is: Source-specific multicast builds source-specific trees and does not require ASM rendezvous point discovery. The confirming observation is: An (S,G) join follows source RPF reachability and multicast arrives without a configured RP.
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 SSM RP unnecessary and the confirming observation is: An (S,G) join follows source RPF reachability and multicast arrives without a configured RP.
B: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 RP unnecessary and the confirming observation is: An (S,G) join follows source RPF reachability and multicast arrives without a configured RP.
C: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 SSM RP unnecessary and the confirming observation is: An (S,G) join follows source RPF reachability and multicast arrives without a configured RP.
Question 577
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: A deployment uses IGMPv3 receivers requesting a specific source and group but engineers keep troubleshooting RP election as if it were ASM. Which routing or service mechanism best explains the reported behavior?
- Source-specific multicast builds source-specific trees and does not require ASM rendezvous point discovery.
- Native IGMPv3 carries source-specific membership information required for straightforward IPv4 SSM subscriptions.
- PIM joins are sent toward the RP using unicast-derived RPF paths; a configured RP with no route is not usable.
- PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over.
Explanation
Correct Answer
A:Source-specific multicast builds source-specific trees and does not require ASM rendezvous point discovery. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: An (S,G) join follows source RPF reachability and multicast arrives without a configured RP. The targeted correction is: Enable consistent SSM treatment and IGMPv3 source-aware membership on participating receivers and routers.
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 SSM RP unnecessary and the confirming observation is: An (S,G) join follows source RPF reachability and multicast arrives without a configured RP.
C: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 RP unnecessary and the confirming observation is: An (S,G) join follows source RPF reachability and multicast arrives without a configured RP.
D:PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over. This is a plausible protocol explanation for a different IP Multicast condition, specifically PIM sparse RP mapping absent. PIM sparse mode ASM uses an RP mapping for shared-tree joins before source-specific tree behavior may take over. In this scenario, however, the distinguishing issue is SSM RP unnecessary and the confirming observation is: An (S,G) join follows source RPF reachability and multicast arrives without a configured RP.
Question 578
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: A deployment uses IGMPv3 receivers requesting a specific source and group but engineers keep troubleshooting RP election as if it were ASM. 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.
- An (S,G) join follows source RPF reachability and multicast arrives without a configured RP.
- A group-specific RP mapping exists and the (*,G) join reaches the mapped RP.
- The RP rejects unauthorized register sources while approved sources still establish traffic.
Explanation
Correct Answer
B:An (S,G) join follows source RPF reachability and multicast arrives without a configured RP. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Source-specific multicast builds source-specific trees and does not require ASM rendezvous point discovery.
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 SSM RP unnecessary and the confirming observation is: An (S,G) join follows source RPF reachability and multicast arrives without a configured RP.
C: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 SSM RP unnecessary and the confirming observation is: An (S,G) join follows source RPF reachability and multicast arrives without a configured RP.
D: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 SSM RP unnecessary and the confirming observation is: An (S,G) join follows source RPF reachability and multicast arrives without a configured RP.
Question 579
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: A deployment uses IGMPv3 receivers requesting a specific source and group but engineers keep troubleshooting RP election as if it were ASM. 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.
- Restore the IGP or static route to the RP address instead of changing receiver group membership.
- Enable consistent SSM treatment and IGMPv3 source-aware membership on participating receivers and routers.
- Configure an appropriate reachable RP mapping for the group range.
Explanation
Correct Answer
C:Enable consistent SSM treatment and IGMPv3 source-aware membership on participating receivers and routers. The change addresses the root behavior described here: Source-specific multicast builds source-specific trees and does not require ASM rendezvous point discovery. Verify success with: An (S,G) join follows source RPF reachability and multicast arrives without a configured RP.
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 SSM RP unnecessary and the confirming observation is: An (S,G) join follows source RPF reachability and multicast arrives without a configured RP.
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 RP unnecessary and the confirming observation is: An (S,G) join follows source RPF reachability and multicast arrives without a configured RP.
D: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 SSM RP unnecessary and the confirming observation is: An (S,G) join follows source RPF reachability and multicast arrives without a configured RP.
Question 580
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: A deployment uses IGMPv3 receivers requesting a specific source and group but engineers keep troubleshooting RP election as if it were ASM. 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.
- Check IGMP source-filter capability before migrating a group range to SSM.
- Track RP loopback availability from each multicast island.
- Document SSM versus ASM group policies to prevent unnecessary RP dependencies.
Explanation
Correct Answer
D:Document SSM versus ASM group policies to prevent unnecessary RP dependencies. The control limits repetition of the described root condition: Source-specific multicast builds source-specific trees and does not require ASM rendezvous point discovery. During audits, confirm: An (S,G) join follows source RPF reachability and multicast arrives without a configured 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 SSM RP unnecessary and the confirming observation is: An (S,G) join follows source RPF reachability and multicast arrives without a configured RP.
B: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 RP unnecessary and the confirming observation is: An (S,G) join follows source RPF reachability and multicast arrives without a configured RP.
C: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 RP unnecessary and the confirming observation is: An (S,G) join follows source RPF reachability and multicast arrives without a configured RP.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests