JN0-650 Premium File
- 107 Questions & Answers
- Last Update: Nov 8, 2026
A multicast receiver stops after a WAN failover because the new unicast best path to the source uses another interface. The proposed correction is: Re-evaluate PIM RPF entries and unicast reachability after the routing convergence. Which observation MOST directly confirms this fault is resolved?
The multicast incoming interface matches the new RPF path and data forwarding resumes. This is the direct acceptance evidence for the observed failure: A multicast receiver stops after a WAN failover because the new unicast best path to the source uses another interface. The mechanism being validated is: PIM relies on unicast or explicit multicast RPF routing information that can change during failover.
The PIM (*,G) Join follows the RPF interface and shared tree state reaches the RP. That would validate a different condition: A PIM sparse-mode router receives an IGMP join but the upstream link toward its configured RP is absent from the unicast routing table. The decisive check for the current issue is: The multicast incoming interface matches the new RPF path and data forwarding resumes.
Neighbor and join output shows PIM active on all links on the selected multicast path. That would validate a different condition: Two PIM neighbors run across the same interface but multicast joins never propagate because PIM is disabled on the receiver-facing transit. The decisive check for the current issue is: The multicast incoming interface matches the new RPF path and data forwarding resumes.
The PIM join distribution and forwarding counters reflect the intended balanced upstream selection. That would validate a different condition: A campus routes one multicast group across two parallel links but all joins flow across a congested upstream even though equal-cost alternatives exist. The decisive check for the current issue is: The multicast incoming interface matches the new RPF path and data forwarding resumes.
A Junos engineer proposes this response: Re-evaluate PIM RPF entries and unicast reachability after the routing convergence. The situation is: A multicast receiver stops after a WAN failover because the new unicast best path to the source uses another interface. Which technical principle BEST justifies the response?
PIM relies on unicast or explicit multicast RPF routing information that can change during failover. This is the controlling mechanism in the specific case: A multicast receiver stops after a WAN failover because the new unicast best path to the source uses another interface. It predicts the acceptance result: The multicast incoming interface matches the new RPF path and data forwarding resumes.
PIM chooses an upstream interface using reverse-path forwarding lookups. This principle explains a separate situation: A PIM sparse-mode router receives an IGMP join but the upstream link toward its configured RP is absent from the unicast routing table. For this issue the relevant mechanism is: PIM relies on unicast or explicit multicast RPF routing information that can change during failover.
Multicast control uses PIM joins across intermediate routers independently of local host IGMP. This principle explains a separate situation: A firewall drops PIM join packets on an intermediate router while standard unicast traffic and IGMP receiver registration succeed. For this issue the relevant mechanism is: PIM relies on unicast or explicit multicast RPF routing information that can change during failover.
IGMPv3 source filtering allows receivers to specify an (S,G) interest for SSM. This principle explains a separate situation: An IGMPv3 receiver requests traffic only from source 198.51.100.9 for group 232.10.1.1, yet the operator checks only group-wide (*,G) state. For this issue the relevant mechanism is: PIM relies on unicast or explicit multicast RPF routing information that can change during failover.
A multicast receiver stops after a WAN failover because the new unicast best path to the source uses another interface. If the team bypasses or fails to implement the targeted correction (Re-evaluate PIM RPF entries and unicast reachability after the routing convergence.), which direct operational risk or residual exposure is MOST relevant?
Assuming static reverse paths after routing convergence can cause silent multicast drops. This is the consequence linked to the observed situation: A multicast receiver stops after a WAN failover because the new unicast best path to the source uses another interface. It is prevented by: Re-evaluate PIM RPF entries and unicast reachability after the routing convergence. The underlying reason is: PIM relies on unicast or explicit multicast RPF routing information that can change during failover.
A healthy IGMP membership cannot compensate for missing RPF connectivity to the RP. This risk belongs to a different operational problem: A PIM sparse-mode router receives an IGMP join but the upstream link toward its configured RP is absent from the unicast routing table. The stated condition instead exposes this direct risk: Assuming static reverse paths after routing convergence can cause silent multicast drops. The appropriate mitigation is: Re-evaluate PIM RPF entries and unicast reachability after the routing convergence.
Unicast ping and valid IGMP membership do not prove the end-to-end multicast tree is built. This risk belongs to a different operational problem: A firewall drops PIM join packets on an intermediate router while standard unicast traffic and IGMP receiver registration succeed. The stated condition instead exposes this direct risk: Assuming static reverse paths after routing convergence can cause silent multicast drops. The appropriate mitigation is: Re-evaluate PIM RPF entries and unicast reachability after the routing convergence.
Ignoring source filtering can admit unwanted sources or misdiagnose missing SSM traffic. This risk belongs to a different operational problem: An IGMPv3 receiver requests traffic only from source 198.51.100.9 for group 232.10.1.1, yet the operator checks only group-wide (*,G) state. The stated condition instead exposes this direct risk: Assuming static reverse paths after routing convergence can cause silent multicast drops. The appropriate mitigation is: Re-evaluate PIM RPF entries and unicast reachability after the routing convergence.
Two PIM routers disagree on the RP learned through bootstrap-router discovery after a BSR domain partition. Which targeted engineering change is MOST directly justified by the observed evidence?
Inspect BSR candidate and RP advertisements and verify consistent group-to-RP mapping across the partition. This change specifically addresses the reported evidence: Two PIM routers disagree on the RP learned through bootstrap-router discovery after a BSR domain partition. The relevant protocol mechanism is: PIM bootstrap mechanisms distribute RP-set information used for ASM group mapping. A decisive acceptance test would be: The same group resolves to the intended RP throughout the joined PIM domain.
Configure a supported RP mapping for the intended ASM multicast groups across the PIM domain. This is a valid solution to a different Junos situation: An ASM receiver joins a multicast group through PIM sparse mode, but no rendezvous point mapping exists for that group range. It does not directly correct the specific failure evidence here: Two PIM routers disagree on the RP learned through bootstrap-router discovery after a BSR domain partition. The required targeted change is: Inspect BSR candidate and RP advertisements and verify consistent group-to-RP mapping across the partition.
Configure and verify the necessary MSDP source-active exchange between the intended RPs. This is a valid solution to a different Junos situation: Two Anycast RP routers learn sources locally but receivers attached to the other RP miss those sources in a design that depends on MSDP. It does not directly correct the specific failure evidence here: Two PIM routers disagree on the RP learned through bootstrap-router discovery after a BSR domain partition. The required targeted change is: Inspect BSR candidate and RP advertisements and verify consistent group-to-RP mapping across the partition.
Use an IGMPv3-capable receiver or a supported SSM mapping design that supplies the missing source address. This is a valid solution to a different Junos situation: A network receives an IPv4 SSM group in the 232.0.0.0/8 range but client software only sends IGMPv2 group-only membership. It does not directly correct the specific failure evidence here: Two PIM routers disagree on the RP learned through bootstrap-router discovery after a BSR domain partition. The required targeted change is: Inspect BSR candidate and RP advertisements and verify consistent group-to-RP mapping across the partition.
Two PIM routers disagree on the RP learned through bootstrap-router discovery after a BSR domain partition. The proposed correction is: Inspect BSR candidate and RP advertisements and verify consistent group-to-RP mapping across the partition. Which observation MOST directly confirms this fault is resolved?
The same group resolves to the intended RP throughout the joined PIM domain. This is the direct acceptance evidence for the observed failure: Two PIM routers disagree on the RP learned through bootstrap-router discovery after a BSR domain partition. The mechanism being validated is: PIM bootstrap mechanisms distribute RP-set information used for ASM group mapping.
The last-hop router discovers the RP and joins the (*,G) shared distribution tree. That would validate a different condition: An ASM receiver joins a multicast group through PIM sparse mode, but no rendezvous point mapping exists for that group range. The decisive check for the current issue is: The same group resolves to the intended RP throughout the joined PIM domain.
Each RP learns the relevant remote active-source advertisements and receivers can join their sources. That would validate a different condition: Two Anycast RP routers learn sources locally but receivers attached to the other RP miss those sources in a design that depends on MSDP. The decisive check for the current issue is: The same group resolves to the intended RP throughout the joined PIM domain.
The last-hop router builds the intended (S,G) join rather than relying on group-only ASM discovery. That would validate a different condition: A network receives an IPv4 SSM group in the 232.0.0.0/8 range but client software only sends IGMPv2 group-only membership. The decisive check for the current issue is: The same group resolves to the intended RP throughout the joined PIM domain.
A Junos engineer proposes this response: Inspect BSR candidate and RP advertisements and verify consistent group-to-RP mapping across the partition. The situation is: Two PIM routers disagree on the RP learned through bootstrap-router discovery after a BSR domain partition. Which technical principle BEST justifies the response?
PIM bootstrap mechanisms distribute RP-set information used for ASM group mapping. This is the controlling mechanism in the specific case: Two PIM routers disagree on the RP learned through bootstrap-router discovery after a BSR domain partition. It predicts the acceptance result: The same group resolves to the intended RP throughout the joined PIM domain.
PIM sparse mode uses a rendezvous point for shared-tree source discovery in ASM. This principle explains a separate situation: An ASM receiver joins a multicast group through PIM sparse mode, but no rendezvous point mapping exists for that group range. For this issue the relevant mechanism is: PIM bootstrap mechanisms distribute RP-set information used for ASM group mapping.
MSDP can convey active-source information across separate RP domains or Anycast RP peers. This principle explains a separate situation: Two Anycast RP routers learn sources locally but receivers attached to the other RP miss those sources in a design that depends on MSDP. For this issue the relevant mechanism is: PIM bootstrap mechanisms distribute RP-set information used for ASM group mapping.
IPv4 SSM requires source-specific membership information for the intended stream. This principle explains a separate situation: A network receives an IPv4 SSM group in the 232.0.0.0/8 range but client software only sends IGMPv2 group-only membership. For this issue the relevant mechanism is: PIM bootstrap mechanisms distribute RP-set information used for ASM group mapping.
Two PIM routers disagree on the RP learned through bootstrap-router discovery after a BSR domain partition. If the team bypasses or fails to implement the targeted correction (Inspect BSR candidate and RP advertisements and verify consistent group-to-RP mapping across the partition.), which direct operational risk or residual exposure is MOST relevant?
Inconsistent RP sets can split multicast source discovery and leave one receiver population isolated. This is the consequence linked to the observed situation: Two PIM routers disagree on the RP learned through bootstrap-router discovery after a BSR domain partition. It is prevented by: Inspect BSR candidate and RP advertisements and verify consistent group-to-RP mapping across the partition. The underlying reason is: PIM bootstrap mechanisms distribute RP-set information used for ASM group mapping.
Without an RP for the ASM group, the normal shared tree cannot be established. This risk belongs to a different operational problem: An ASM receiver joins a multicast group through PIM sparse mode, but no rendezvous point mapping exists for that group range. The stated condition instead exposes this direct risk: Inconsistent RP sets can split multicast source discovery and leave one receiver population isolated. The appropriate mitigation is: Inspect BSR candidate and RP advertisements and verify consistent group-to-RP mapping across the partition.
An Anycast address alone does not synchronize active-source discovery in an MSDP-based design. This risk belongs to a different operational problem: Two Anycast RP routers learn sources locally but receivers attached to the other RP miss those sources in a design that depends on MSDP. The stated condition instead exposes this direct risk: Inconsistent RP sets can split multicast source discovery and leave one receiver population isolated. The appropriate mitigation is: Inspect BSR candidate and RP advertisements and verify consistent group-to-RP mapping across the partition.
Group-only joins without mapping cannot unambiguously select a source for the SSM group. This risk belongs to a different operational problem: A network receives an IPv4 SSM group in the 232.0.0.0/8 range but client software only sends IGMPv2 group-only membership. The stated condition instead exposes this direct risk: Inconsistent RP sets can split multicast source discovery and leave one receiver population isolated. The appropriate mitigation is: Inspect BSR candidate and RP advertisements and verify consistent group-to-RP mapping across the partition.
An IGMPv3 receiver joins a group with an EXCLUDE list while a new design requires an explicit single allowed source. Which targeted engineering change is MOST directly justified by the observed evidence?
Change the receiver membership to an INCLUDE list for the specified SSM source. This change specifically addresses the reported evidence: An IGMPv3 receiver joins a group with an EXCLUDE list while a new design requires an explicit single allowed source. The relevant protocol mechanism is: IGMPv3 INCLUDE lists express positive source membership for source-specific reception. A decisive acceptance test would be: The multicast entry includes the named source and excludes other senders for the same group.
Use an IGMPv3-capable receiver or a supported SSM mapping design that supplies the missing source address. This is a valid solution to a different Junos situation: A network receives an IPv4 SSM group in the 232.0.0.0/8 range but client software only sends IGMPv2 group-only membership. It does not directly correct the specific failure evidence here: An IGMPv3 receiver joins a group with an EXCLUDE list while a new design requires an explicit single allowed source. The required targeted change is: Change the receiver membership to an INCLUDE list for the specified SSM source.
Build a valid source-specific multicast tree using IGMPv3 source membership and PIM SSM, without requiring an RP. This is a valid solution to a different Junos situation: An SSM-only multicast video service was given an RP address although every subscriber explicitly knows the source address. It does not directly correct the specific failure evidence here: An IGMPv3 receiver joins a group with an EXCLUDE list while a new design requires an explicit single allowed source. The required targeted change is: Change the receiver membership to an INCLUDE list for the specified SSM source.
Check the supported shortest-path-tree switchover and (S,G) state for interested last-hop routers. This is a valid solution to a different Junos situation: A sparse-mode group reaches receivers through an inefficient path via the RP after the source becomes known. It does not directly correct the specific failure evidence here: An IGMPv3 receiver joins a group with an EXCLUDE list while a new design requires an explicit single allowed source. The required targeted change is: Change the receiver membership to an INCLUDE list for the specified SSM source.
An IGMPv3 receiver joins a group with an EXCLUDE list while a new design requires an explicit single allowed source. The proposed correction is: Change the receiver membership to an INCLUDE list for the specified SSM source. Which observation MOST directly confirms this fault is resolved?
The multicast entry includes the named source and excludes other senders for the same group. This is the direct acceptance evidence for the observed failure: An IGMPv3 receiver joins a group with an EXCLUDE list while a new design requires an explicit single allowed source. The mechanism being validated is: IGMPv3 INCLUDE lists express positive source membership for source-specific reception.
The multicast state shows the exact (source,group) pair requested by the receiver. That would validate a different condition: An IGMPv3 receiver requests traffic only from source 198.51.100.9 for group 232.10.1.1, yet the operator checks only group-wide (*,G) state. The decisive check for the current issue is: The multicast entry includes the named source and excludes other senders for the same group.
The requested (S,G) stream reaches subscribers directly along its source tree. That would validate a different condition: An SSM-only multicast video service was given an RP address although every subscriber explicitly knows the source address. The decisive check for the current issue is: The multicast entry includes the named source and excludes other senders for the same group.
Source traffic follows the intended shortest-path tree without unnecessary RP transit. That would validate a different condition: A sparse-mode group reaches receivers through an inefficient path via the RP after the source becomes known. The decisive check for the current issue is: The multicast entry includes the named source and excludes other senders for the same group.
A Junos engineer proposes this response: Change the receiver membership to an INCLUDE list for the specified SSM source. The situation is: An IGMPv3 receiver joins a group with an EXCLUDE list while a new design requires an explicit single allowed source. Which technical principle BEST justifies the response?
IGMPv3 INCLUDE lists express positive source membership for source-specific reception. This is the controlling mechanism in the specific case: An IGMPv3 receiver joins a group with an EXCLUDE list while a new design requires an explicit single allowed source. It predicts the acceptance result: The multicast entry includes the named source and excludes other senders for the same group.
IGMPv3 source filtering allows receivers to specify an (S,G) interest for SSM. This principle explains a separate situation: An IGMPv3 receiver requests traffic only from source 198.51.100.9 for group 232.10.1.1, yet the operator checks only group-wide (*,G) state. For this issue the relevant mechanism is: IGMPv3 INCLUDE lists express positive source membership for source-specific reception.
IGMP lets hosts indicate interest in IPv4 multicast groups to adjacent multicast routers. This principle explains a separate situation: An IPTV receiver joins an IPv4 ASM group but the attached Junos router has no current IGMP membership state for the interface. For this issue the relevant mechanism is: IGMPv3 INCLUDE lists express positive source membership for source-specific reception.
PIM-SM receivers may transition from an RP shared tree to a source-specific shortest-path tree. This principle explains a separate situation: A sparse-mode group reaches receivers through an inefficient path via the RP after the source becomes known. For this issue the relevant mechanism is: IGMPv3 INCLUDE lists express positive source membership for source-specific reception.
An IGMPv3 receiver joins a group with an EXCLUDE list while a new design requires an explicit single allowed source. If the team bypasses or fails to implement the targeted correction (Change the receiver membership to an INCLUDE list for the specified SSM source.), which direct operational risk or residual exposure is MOST relevant?
An EXCLUDE-style group request may admit unintended source traffic in the wrong service design. This is the consequence linked to the observed situation: An IGMPv3 receiver joins a group with an EXCLUDE list while a new design requires an explicit single allowed source. It is prevented by: Change the receiver membership to an INCLUDE list for the specified SSM source. The underlying reason is: IGMPv3 INCLUDE lists express positive source membership for source-specific reception.
Ignoring source filtering can admit unwanted sources or misdiagnose missing SSM traffic. This risk belongs to a different operational problem: An IGMPv3 receiver requests traffic only from source 198.51.100.9 for group 232.10.1.1, yet the operator checks only group-wide (*,G) state. The stated condition instead exposes this direct risk: An EXCLUDE-style group request may admit unintended source traffic in the wrong service design. The appropriate mitigation is: Change the receiver membership to an INCLUDE list for the specified SSM source.
With no valid receiver membership, the router may not build the intended downstream multicast branch. This risk belongs to a different operational problem: An IPTV receiver joins an IPv4 ASM group but the attached Junos router has no current IGMP membership state for the interface. The stated condition instead exposes this direct risk: An EXCLUDE-style group request may admit unintended source traffic in the wrong service design. The appropriate mitigation is: Change the receiver membership to an INCLUDE list for the specified SSM source.
Remaining on an unsuitable RP-centered path can increase multicast transit latency and bandwidth. This risk belongs to a different operational problem: A sparse-mode group reaches receivers through an inefficient path via the RP after the source becomes known. The stated condition instead exposes this direct risk: An EXCLUDE-style group request may admit unintended source traffic in the wrong service design. The appropriate mitigation is: Change the receiver membership to an INCLUDE list for the specified SSM source.
Please check your mailbox for a message from support@examlabs.com and follow the directions.