Juniper JN0-664 Practice Test 31
Question 300
A Junos service-provider routing engineer investigates this service-provider network scenario. An RP address can be pinged through the management VRF yet multicast joins fail because the PIM routing instance lacks actual RP reachability. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.
- Validate that all nonbackbone OSPF areas have a supported logical connection to area 0, and use virtual links only as a documented transitional design.
- Confirm appropriate PIM sparse-mode RP reachability and registration for any-source multicast groups before treating receiver membership as full service health.
- Validate Designated Intermediate System behavior on a LAN segment rather than confusing it with the OSPF DR/BDR algorithm.
- Review show pim neighbors, RP mapping, IGMP membership, PIM joins, source registration and multicast forwarding entries for affected groups.
- Inspect source route lookup, multicast RPF information, arrival interface, show multicast route details and topology symmetry.
Explanation
Correct Answers
B:The case-specific routing and services action is: Confirm appropriate PIM sparse-mode RP reachability and registration for any-source multicast groups before treating receiver membership as full service health.
D:The direct discriminating observation is: Review show pim neighbors, RP mapping, IGMP membership, PIM joins, source registration and multicast forwarding entries for affected groups.
Incorrect Answers
A:This alternative proposes: Validate that all nonbackbone OSPF areas have a supported logical connection to area 0, and use virtual links only as a documented transitional design. It concerns a different Junos engineering issue OSPF multi-area backbone connectivity and virtual-link limitations, not the directly tested provider-network issue PIM sparse mode rendezvous point and shared tree operation.
C:This alternative proposes: Validate Designated Intermediate System behavior on a LAN segment rather than confusing it with the OSPF DR/BDR algorithm. It concerns a different Junos engineering issue IS-IS DIS pseudonode and broadcast circuit election, not the directly tested provider-network issue PIM sparse mode rendezvous point and shared tree operation.
E:This alternative proposes: Inspect source route lookup, multicast RPF information, arrival interface, show multicast route details and topology symmetry. It concerns a different Junos engineering issue Multicast RPF validation and source reachability, not the directly tested provider-network issue PIM sparse mode rendezvous point and shared tree operation in the stated situation (An RP address can be pinged through the management VRF yet multicast joins fail because the PIM routing instance lacks actual RP reachability.). A better case-specific check is: Review show pim neighbors, RP mapping, IGMP membership, PIM joins, source registration and multicast forwarding entries for affected groups.
Question 301
A Junos service-provider routing engineer investigates the following routing and service incident: An IPTV subscriber expects one broadcaster's 232.1.1.10 stream but its access equipment has only group-wide IGMPv2 membership. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Build resilient ASM rendezvous-point service using supported Anycast RP design and validate source and receiver registration continuity under failover.
- Restrict interlevel IS-IS route advertisements to the intended prefixes with controlled L1/L2 policy and verify return reachability.
- Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it.
- Confirm appropriate PIM sparse-mode RP reachability and registration for any-source multicast groups before treating receiver membership as full service health.
Explanation
Correct Answer
C:The case-specific routing and services action is: Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it. The governing Junos routing/service principle is: PIM SSM builds a source-rooted tree without an RP and uses IGMPv3 source inclusion on IPv4 receiver links for explicit source selection.
Incorrect Answers
A:This alternative proposes: Build resilient ASM rendezvous-point service using supported Anycast RP design and validate source and receiver registration continuity under failover. It concerns a different Junos engineering issue Anycast RP resilient multicast service and routing policy, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
B:This alternative proposes: Restrict interlevel IS-IS route advertisements to the intended prefixes with controlled L1/L2 policy and verify return reachability. It concerns a different Junos engineering issue IS-IS Level 2 to Level 1 route leaking and summaries, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
D:This alternative proposes: Confirm appropriate PIM sparse-mode RP reachability and registration for any-source multicast groups before treating receiver membership as full service health. It concerns a different Junos engineering issue PIM sparse mode rendezvous point and shared tree operation, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
Question 302
A provider routing design review considers this situation. An IPTV subscriber expects one broadcaster's 232.1.1.10 stream but its access equipment has only group-wide IGMPv2 membership. A colleague proposes: Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it. Which technical principle BEST supports that action? Select ONE best answer.
- PIM SSM builds a source-rooted tree without an RP and uses IGMPv3 source inclusion on IPv4 receiver links for explicit source selection.
- ASM PIM-SM may use a rendezvous point for rendezvous and shared tree creation, after which routers can move eligible traffic onto source-based trees.
- Anycast RP can let multiple RPs share an RP address with protocol mechanisms to coordinate state, but a reachable shared address alone does not prove group information is synchronized.
- VPLS presents multipoint Ethernet LAN semantics across provider nodes, while LDP or BGP signaling can distribute service state and labels; mixing models requires supported interworking.
Explanation
Correct Answer
A:The relevant Junos service-provider networking principle is: PIM SSM builds a source-rooted tree without an RP and uses IGMPv3 source inclusion on IPv4 receiver links for explicit source selection. In the described provider-network case (An IPTV subscriber expects one broadcaster's 232.1.1.10 stream but its access equipment has only group-wide IGMPv2 membership.), it supports the planned action: Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it.
Incorrect Answers
B:This alternative proposes: ASM PIM-SM may use a rendezvous point for rendezvous and shared tree creation, after which routers can move eligible traffic onto source-based trees. It concerns a different Junos engineering issue PIM sparse mode rendezvous point and shared tree operation, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
C:This alternative proposes: Anycast RP can let multiple RPs share an RP address with protocol mechanisms to coordinate state, but a reachable shared address alone does not prove group information is synchronized. It concerns a different Junos engineering issue Anycast RP resilient multicast service and routing policy, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
D:This alternative proposes: VPLS presents multipoint Ethernet LAN semantics across provider nodes, while LDP or BGP signaling can distribute service state and labels; mixing models requires supported interworking. It concerns a different Junos engineering issue VPLS service control plane LDP versus BGP distribution, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
Question 303
A Juniper service-provider engineer needs decisive verification evidence for this situation. An IPTV subscriber expects one broadcaster's 232.1.1.10 stream but its access equipment has only group-wide IGMPv2 membership. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Inspect RP node reachability, anycast route advertisement, appropriate state synchronization, peer status, group registration and service traffic during failover.
- Review show pim neighbors, RP mapping, IGMP membership, PIM joins, source registration and multicast forwarding entries for affected groups.
- Inspect IS-IS metric configuration on both ends, extended TLV capability, show isis route, and SPF results before changing costs.
- Inspect SSM group range, IGMPv3 (S,G) membership, source unicast route, RPF state, PIM joins and actual packet counts.
Explanation
Correct Answer
D:The direct discriminating observation is: Inspect SSM group range, IGMPv3 (S,G) membership, source unicast route, RPF state, PIM joins and actual packet counts. In the stated situation (An IPTV subscriber expects one broadcaster's 232.1.1.10 stream but its access equipment has only group-wide IGMPv2 membership.), the intended acceptance outcome is: Only the subscribed sender's multicast stream reaches intended receivers without relying on an any-source rendezvous point.
Incorrect Answers
A:This alternative proposes: Inspect RP node reachability, anycast route advertisement, appropriate state synchronization, peer status, group registration and service traffic during failover. It concerns a different Junos engineering issue Anycast RP resilient multicast service and routing policy, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
B:This alternative proposes: Review show pim neighbors, RP mapping, IGMP membership, PIM joins, source registration and multicast forwarding entries for affected groups. It concerns a different Junos engineering issue PIM sparse mode rendezvous point and shared tree operation, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
C:This alternative proposes: Inspect IS-IS metric configuration on both ends, extended TLV capability, show isis route, and SPF results before changing costs. It concerns a different Junos engineering issue IS-IS wide metrics traffic engineering and cost selection, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
Question 304
A service-provider acceptance team reviews the result of a provider-service change. An IPTV subscriber expects one broadcaster's 232.1.1.10 stream but its access equipment has only group-wide IGMPv2 membership. The intended verification is: Inspect SSM group range, IGMPv3 (S,G) membership, source unicast route, RPF state, PIM joins and actual packet counts. Which outcome BEST demonstrates success? Select ONE best answer.
- The configured mode serves actual receivers without uncontrolled multicast flood in sparsely subscribed provider regions.
- Only the subscribed sender's multicast stream reaches intended receivers without relying on an any-source rendezvous point.
- The traffic arrives on an eligible RPF interface and reaches subscribed downstream links without introducing a multicast loop.
- Access routers learn only authorized leaked routes, continue using their correct area exit and do not create interlevel routing loops.
Explanation
Correct Answer
B:The verified success outcome is: Only the subscribed sender's multicast stream reaches intended receivers without relying on an any-source rendezvous point. Confirm this by: Inspect SSM group range, IGMPv3 (S,G) membership, source unicast route, RPF state, PIM joins and actual packet counts.
Incorrect Answers
A:That option concerns PIM dense mode versus sparse mode interface deployment. The related controlled intervention is: Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it.
C:This alternative proposes: The traffic arrives on an eligible RPF interface and reaches subscribed downstream links without introducing a multicast loop. It concerns a different Junos engineering issue Multicast RPF validation and source reachability, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
D:That option concerns IS-IS Level 2 to Level 1 route leaking and summaries. The related controlled intervention is: Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it.
Question 305
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. An IPTV subscriber expects one broadcaster's 232.1.1.10 stream but its access equipment has only group-wide IGMPv2 membership. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Assume an ASM PIM-SM network never needs any RP configuration or discovery because IGMP listeners exist at the leaf router.
- Configure a 232/8 SSM channel for a receiver that only sends unspecified-source IGMPv2 joins and assume it identifies the desired video source.
- Create a custom classifier in configuration but omit the interface association and assume all access ports will automatically use the new map.
- Enable dense-mode flooding across the entire sparse subscriber backbone solely to correct one missing video stream without evaluating blast radius.
Explanation
Correct Answer
B:The directly relevant unsafe assumption is: Configure a 232/8 SSM channel for a receiver that only sends unspecified-source IGMPv2 joins and assume it identifies the desired video source. That conflicts with the edge-to-cloud principle: PIM SSM builds a source-rooted tree without an RP and uses IGMPv3 source inclusion on IPv4 receiver links for explicit source selection.
Incorrect Answers
A:This alternative proposes: Assume an ASM PIM-SM network never needs any RP configuration or discovery because IGMP listeners exist at the leaf router. It concerns a different Junos engineering issue PIM sparse mode rendezvous point and shared tree operation, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
C:This alternative proposes: Create a custom classifier in configuration but omit the interface association and assume all access ports will automatically use the new map. It concerns a different Junos engineering issue Junos CoS behavior aggregate versus multifield classifiers, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
D:This alternative proposes: Enable dense-mode flooding across the entire sparse subscriber backbone solely to correct one missing video stream without evaluating blast radius. It concerns a different Junos engineering issue PIM dense mode versus sparse mode interface deployment, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
Question 306
A Junos service-provider routing engineer investigates the following routing and service incident: A provider migrates an ASM multicast channel to SSM and forgets the source-specific receiver signaling needed for the new design. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Use reverse-path forwarding checks to determine why an arriving multicast packet is accepted on one interface but discarded on another.
- Build resilient ASM rendezvous-point service using supported Anycast RP design and validate source and receiver registration continuity under failover.
- Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it.
- Verify address-family negotiation and route transport for IPv4 unicast, VPNv4, VPNv6 or EVPN separately rather than treating Established BGP TCP state as proof each family works.
Explanation
Correct Answer
C:The case-specific routing and services action is: Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it. The governing Junos routing/service principle is: PIM SSM builds a source-rooted tree without an RP and uses IGMPv3 source inclusion on IPv4 receiver links for explicit source selection. Verify the decision through: Inspect SSM group range, IGMPv3 (S,G) membership, source unicast route, RPF state, PIM joins and actual packet counts.
Incorrect Answers
A:This alternative proposes: Use reverse-path forwarding checks to determine why an arriving multicast packet is accepted on one interface but discarded on another. It concerns a different Junos engineering issue Multicast RPF validation and source reachability, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
B:This alternative proposes: Build resilient ASM rendezvous-point service using supported Anycast RP design and validate source and receiver registration continuity under failover. It concerns a different Junos engineering issue Anycast RP resilient multicast service and routing policy, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
D:This alternative proposes: Verify address-family negotiation and route transport for IPv4 unicast, VPNv4, VPNv6 or EVPN separately rather than treating Established BGP TCP state as proof each family works. It concerns a different Junos engineering issue Multiprotocol BGP family negotiations and VPN routes, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
Question 307
A provider routing design review considers this situation. A provider migrates an ASM multicast channel to SSM and forgets the source-specific receiver signaling needed for the new design. A colleague proposes: Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it. Which technical principle BEST supports that action? Select ONE best answer.
- PIM SSM builds a source-rooted tree without an RP and uses IGMPv3 source inclusion on IPv4 receiver links for explicit source selection.
- Dense-mode forwarding generally begins by flooding and pruning, while sparse-mode forwarding builds explicit join-based trees; PIM neighbors and group reachability depend on configuration and topology.
- Forwarding class selects an appropriate queue and packet-loss priority influences treatment such as drop precedence, but priority marking cannot create unavailable physical bandwidth.
- ASM PIM-SM may use a rendezvous point for rendezvous and shared tree creation, after which routers can move eligible traffic onto source-based trees.
Explanation
Correct Answer
A:The relevant Junos service-provider networking principle is: PIM SSM builds a source-rooted tree without an RP and uses IGMPv3 source inclusion on IPv4 receiver links for explicit source selection. In the described provider-network case (A provider migrates an ASM multicast channel to SSM and forgets the source-specific receiver signaling needed for the new design.), it supports the planned action: Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it.
Incorrect Answers
B:This alternative proposes: Dense-mode forwarding generally begins by flooding and pruning, while sparse-mode forwarding builds explicit join-based trees; PIM neighbors and group reachability depend on configuration and topology. It concerns a different Junos engineering issue PIM dense mode versus sparse mode interface deployment, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
C:This alternative proposes: Forwarding class selects an appropriate queue and packet-loss priority influences treatment such as drop precedence, but priority marking cannot create unavailable physical bandwidth. It concerns a different Junos engineering issue CoS forwarding classes packet-loss priority and egress queue binding, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
D:This alternative proposes: ASM PIM-SM may use a rendezvous point for rendezvous and shared tree creation, after which routers can move eligible traffic onto source-based trees. It concerns a different Junos engineering issue PIM sparse mode rendezvous point and shared tree operation, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
Question 308
A Juniper service-provider engineer needs decisive verification evidence for this situation. A provider migrates an ASM multicast channel to SSM and forgets the source-specific receiver signaling needed for the new design. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Inspect source route lookup, multicast RPF information, arrival interface, show multicast route details and topology symmetry.
- Compare area type on all routers, ASBR redistribution, Type 3 summaries, Type 5 or Type 7 database entries, and resulting route installation.
- Inspect SSM group range, IGMPv3 (S,G) membership, source unicast route, RPF state, PIM joins and actual packet counts.
- Inspect RP node reachability, anycast route advertisement, appropriate state synchronization, peer status, group registration and service traffic during failover.
Explanation
Correct Answer
C:The direct discriminating observation is: Inspect SSM group range, IGMPv3 (S,G) membership, source unicast route, RPF state, PIM joins and actual packet counts. In the stated situation (A provider migrates an ASM multicast channel to SSM and forgets the source-specific receiver signaling needed for the new design.), the intended acceptance outcome is: Only the subscribed sender's multicast stream reaches intended receivers without relying on an any-source rendezvous point.
Incorrect Answers
A:This alternative proposes: Inspect source route lookup, multicast RPF information, arrival interface, show multicast route details and topology symmetry. It concerns a different Junos engineering issue Multicast RPF validation and source reachability, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
B:This alternative proposes: Compare area type on all routers, ASBR redistribution, Type 3 summaries, Type 5 or Type 7 database entries, and resulting route installation. It concerns a different Junos engineering issue OSPF stub NSSA and external LSA handling, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
D:This alternative proposes: Inspect RP node reachability, anycast route advertisement, appropriate state synchronization, peer status, group registration and service traffic during failover. It concerns a different Junos engineering issue Anycast RP resilient multicast service and routing policy, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
Question 309
A service-provider acceptance team reviews the result of a provider-service change. A provider migrates an ASM multicast channel to SSM and forgets the source-specific receiver signaling needed for the new design. The intended verification is: Inspect SSM group range, IGMPv3 (S,G) membership, source unicast route, RPF state, PIM joins and actual packet counts. Which outcome BEST demonstrates success? Select ONE best answer.
- Subscribers receive the intended group from approved sources and traffic continues after a tested RP or upstream path change.
- Only the subscribed sender's multicast stream reaches intended receivers without relying on an any-source rendezvous point.
- The neighbor reaches Full, both routers synchronize the relevant link-state database, and no unrelated adjacencies are disrupted.
- Multicast subscribers continue receiving approved sources when one RP fails, with no duplicate or missing source registration state.
Explanation
Correct Answer
B:The verified success outcome is: Only the subscribed sender's multicast stream reaches intended receivers without relying on an any-source rendezvous point. Confirm this by: Inspect SSM group range, IGMPv3 (S,G) membership, source unicast route, RPF state, PIM joins and actual packet counts. The related controlled intervention is: Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it.
Incorrect Answers
A:That option concerns PIM sparse mode rendezvous point and shared tree operation. The related controlled intervention is: Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it.
C:That option concerns OSPF adjacency MTU and hello compatibility diagnosis. The related controlled intervention is: Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it.
D:That option concerns Anycast RP resilient multicast service and routing policy. The related controlled intervention is: Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it.
Question 310
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. A provider migrates an ASM multicast channel to SSM and forgets the source-specific receiver signaling needed for the new design. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Assume an ASM PIM-SM network never needs any RP configuration or discovery because IGMP listeners exist at the leaf router.
- Configure a 232/8 SSM channel for a receiver that only sends unspecified-source IGMPv2 joins and assume it identifies the desired video source.
- Treat an RD as an access-control filter and set identical RDs for every unrelated VPN while leaving permissive RT import policy unrestricted.
- Enable receiver IGMP membership on every LAN and assert RPF is irrelevant to the provider's upstream multicast forwarding decisions.
Explanation
Correct Answer
B:The directly relevant unsafe assumption is: Configure a 232/8 SSM channel for a receiver that only sends unspecified-source IGMPv2 joins and assume it identifies the desired video source. That conflicts with the edge-to-cloud principle: PIM SSM builds a source-rooted tree without an RP and uses IGMPv3 source inclusion on IPv4 receiver links for explicit source selection. Apply instead: Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it.
Incorrect Answers
A:This alternative proposes: Assume an ASM PIM-SM network never needs any RP configuration or discovery because IGMP listeners exist at the leaf router. It concerns a different Junos engineering issue PIM sparse mode rendezvous point and shared tree operation, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
C:This alternative proposes: Treat an RD as an access-control filter and set identical RDs for every unrelated VPN while leaving permissive RT import policy unrestricted. It concerns a different Junos engineering issue Layer 3 VPN route distinguishers versus route targets, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.
D:This alternative proposes: Enable receiver IGMP membership on every LAN and assert RPF is irrelevant to the provider's upstream multicast forwarding decisions. It concerns a different Junos engineering issue Multicast RPF validation and source reachability, not the directly tested provider-network issue Source-specific multicast and IGMPv3 source filtering.