Juniper JN0-664 Practice Test 48
Question 470
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. A new CE cannot reach remote peers until its source MAC is learned, and a technician misinterprets initial unknown-unicast flooding as uncontrolled Internet broadcast. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Disable all split-horizon checks and bridge every pseudowire to every other pseudowire as a first response to one unknown MAC address.
- Create two circuits with different VC identifiers and assume LDP can automatically infer they belong to the same customer service because the physical ports are Up.
- Assign identical customer site IDs to unrelated participating VPLS sites and assume unique identification is unimportant because the PEs have different loopbacks.
- Assume an established VPNv4 BGP session automatically advertises the IPv6 prefix 2001:db8:50::/48 into every remote instance.inet6.0.
Explanation
Correct Answer
A:That conflicts with the edge-to-cloud principle: Multipoint Ethernet services learn source MAC locations and flood unknown unicast, broadcast and multicast within permitted service boundaries; split-horizon rules limit loop-causing PW-to-PW forwarding.
Incorrect Answers
B:This alternative proposes: Create two circuits with different VC identifiers and assume LDP can automatically infer they belong to the same customer service because the physical ports are Up. It concerns a different Junos engineering issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers, not the directly tested provider-network issue VPLS MAC learning flooding and split-horizon safeguards.
C:This alternative proposes: Assign identical customer site IDs to unrelated participating VPLS sites and assume unique identification is unimportant because the PEs have different loopbacks. It concerns a different Junos engineering issue VPLS site identifiers multihoming and service convergence, not the directly tested provider-network issue VPLS MAC learning flooding and split-horizon safeguards.
D:This alternative proposes: Assume an established VPNv4 BGP session automatically advertises the IPv6 prefix 2001:db8:50::/48 into every remote instance.inet6.0. It concerns a different Junos engineering issue IPv6 Layer 3 VPN VPNv6 route families and forwarding, not the directly tested provider-network issue VPLS MAC learning flooding and split-horizon safeguards.
Question 471
A Junos service-provider routing engineer investigates the following routing and service incident: A large customer dual-homes one campus to two PEs and experiences repeated MAC relearning whenever both attachments are active without proper redundancy handling. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Use BGP EVPN MAC/IP reachability information to explain how remote PE devices learn and advertise Ethernet endpoints without relying only on flooding.
- Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop.
- Confirm appropriate PIM sparse-mode RP reachability and registration for any-source multicast groups before treating receiver membership as full service health.
- Verify service MTU and any supported pseudowire encapsulation/control-word expectations when a pseudowire is signaled Up but customer frames fail.
Explanation
Correct Answer
B:The case-specific routing and services action is: Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop. The governing Junos routing/service principle is: VPLS site identification and multihoming mechanisms help coordinate PE access, but customer-facing redundant paths need a supported convergence and loop-control design.
Incorrect Answers
A:This alternative proposes: Use BGP EVPN MAC/IP reachability information to explain how remote PE devices learn and advertise Ethernet endpoints without relying only on flooding. It concerns a different Junos engineering issue EVPN MAC IP route type two control plane and learning, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.
C: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 VPLS site identifiers multihoming and service convergence.
D:This alternative proposes: Verify service MTU and any supported pseudowire encapsulation/control-word expectations when a pseudowire is signaled Up but customer frames fail. It concerns a different Junos engineering issue Layer 2 pseudowire MTU and control-word interworking, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.
Question 472
A provider routing design review considers this situation. A large customer dual-homes one campus to two PEs and experiences repeated MAC relearning whenever both attachments are active without proper redundancy handling. A colleague proposes: Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop. Which technical principle BEST supports that action? Select ONE best answer.
- VPLS site identification and multihoming mechanisms help coordinate PE access, but customer-facing redundant paths need a supported convergence and loop-control design.
- EVPN all-active or single-active multihoming uses a shared ESI and appropriate DF/aliasing coordination to prevent BUM duplication and maintain reachable paths under failure.
- PE/CE exchange can use a supported static, BGP, OSPF or other mechanism; the customer interface must belong to the intended VRF and outbound policy determines what enters VPN reachability.
- A BGP-signaled Layer 2 VPN advertises service-related NLRI and label reachability; route-target and instance-policy behavior determine which remote service participates.
Explanation
Correct Answer
A:The relevant Junos service-provider networking principle is: VPLS site identification and multihoming mechanisms help coordinate PE access, but customer-facing redundant paths need a supported convergence and loop-control design. In the described provider-network case (A large customer dual-homes one campus to two PEs and experiences repeated MAC relearning whenever both attachments are active without proper redundancy handling.), it supports the planned action: Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop.
Incorrect Answers
B:This alternative proposes: EVPN all-active or single-active multihoming uses a shared ESI and appropriate DF/aliasing coordination to prevent BUM duplication and maintain reachable paths under failure. It concerns a different Junos engineering issue EVPN Ethernet segment multihoming and designated forwarder, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.
C:This alternative proposes: PE/CE exchange can use a supported static, BGP, OSPF or other mechanism; the customer interface must belong to the intended VRF and outbound policy determines what enters VPN reachability. It concerns a different Junos engineering issue PE to CE routing and customer route redistribution, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.
D:This alternative proposes: A BGP-signaled Layer 2 VPN advertises service-related NLRI and label reachability; route-target and instance-policy behavior determine which remote service participates. It concerns a different Junos engineering issue BGP-signaled Layer 2 VPN NLRI and route target import, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.
Question 473
A Juniper service-provider engineer needs decisive verification evidence for this situation. A large customer dual-homes one campus to two PEs and experiences repeated MAC relearning whenever both attachments are active without proper redundancy handling. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability.
- Review CE dual-homing advertisements, SoO community tags, OSPF route type/cost, sham-link endpoint reachability and import/export policy.
- Check service-site IDs, multihoming preference, attachment circuits, signaling reachability, MAC moves and measured forwarding during failover.
- Compare CE frame sizes, attachment-circuit encapsulation, pseudowire MTU, control-word configuration, interface drops and forwarding test results at both PEs.
Explanation
Correct Answer
C:The direct discriminating observation is: Check service-site IDs, multihoming preference, attachment circuits, signaling reachability, MAC moves and measured forwarding during failover. In the stated situation (A large customer dual-homes one campus to two PEs and experiences repeated MAC relearning whenever both attachments are active without proper redundancy handling.), the intended acceptance outcome is: The authorized CE service survives a primary PE outage with the expected alternate active and without creating duplicated Ethernet forwarding.
Incorrect Answers
A:This alternative proposes: Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability. It concerns a different Junos engineering issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.
B:This alternative proposes: Review CE dual-homing advertisements, SoO community tags, OSPF route type/cost, sham-link endpoint reachability and import/export policy. It concerns a different Junos engineering issue Site of Origin and OSPF sham-link loop control, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.
D:This alternative proposes: Compare CE frame sizes, attachment-circuit encapsulation, pseudowire MTU, control-word configuration, interface drops and forwarding test results at both PEs. It concerns a different Junos engineering issue Layer 2 pseudowire MTU and control-word interworking, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.
Question 474
A service-provider acceptance team reviews the result of a provider-service change. A large customer dual-homes one campus to two PEs and experiences repeated MAC relearning whenever both attachments are active without proper redundancy handling. The intended verification is: Check service-site IDs, multihoming preference, attachment circuits, signaling reachability, MAC moves and measured forwarding during failover. Which outcome BEST demonstrates success? Select ONE best answer.
- The customer transports frames within the agreed service MTU without unexplained fragmentation, truncation or interworking incompatibility.
- A moved customer endpoint is reachable through its current PE and stale advertised paths are withdrawn or updated according to supported mobility behavior.
- The authorized CE service survives a primary PE outage with the expected alternate active and without creating duplicated Ethernet forwarding.
- All site prefixes move between areas without routing loops, and the proposed backbone topology survives its agreed failure test.
Explanation
Correct Answer
C:The verified success outcome is: The authorized CE service survives a primary PE outage with the expected alternate active and without creating duplicated Ethernet forwarding. Confirm this by: Check service-site IDs, multihoming preference, attachment circuits, signaling reachability, MAC moves and measured forwarding during failover.
Incorrect Answers
A:That option concerns Layer 2 pseudowire MTU and control-word interworking. The related controlled intervention is: Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop.
B:That option concerns EVPN MAC IP route type two control plane and learning. The related controlled intervention is: Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop.
D:That option concerns OSPF multi-area backbone connectivity and virtual-link limitations. The related controlled intervention is: Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop.
Question 475
A Junos service-provider routing engineer investigates this service-provider network scenario. A large customer dual-homes one campus to two PEs and experiences repeated MAC relearning whenever both attachments are active without proper redundancy handling. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.
- Choose the correct OSPF stub or NSSA area design according to the requirement for redistributed external routes and verify supported Type 7 translation.
- Inspect MAC tables per VPLS instance, flood counters, PE attachment circuits, pseudowire membership, MAC aging and loop-protection state.
- Validate multicast VPN control and data-plane dependencies before claiming a customer group's IP multicast stream should traverse an MPLS provider backbone.
- Check service-site IDs, multihoming preference, attachment circuits, signaling reachability, MAC moves and measured forwarding during failover.
- Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop.
Explanation
Correct Answers
D:The direct discriminating observation is: Check service-site IDs, multihoming preference, attachment circuits, signaling reachability, MAC moves and measured forwarding during failover.
E:The case-specific routing and services action is: Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop. The governing Junos routing/service principle is: VPLS site identification and multihoming mechanisms help coordinate PE access, but customer-facing redundant paths need a supported convergence and loop-control design. Verify the decision through: Check service-site IDs, multihoming preference, attachment circuits, signaling reachability, MAC moves and measured forwarding during failover.
Incorrect Answers
A:This alternative proposes: Choose the correct OSPF stub or NSSA area design according to the requirement for redistributed external routes and verify supported Type 7 translation. It concerns a different Junos engineering issue OSPF stub NSSA and external LSA handling, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.
B:This alternative proposes: Inspect MAC tables per VPLS instance, flood counters, PE attachment circuits, pseudowire membership, MAC aging and loop-protection state. It concerns a different Junos engineering issue VPLS MAC learning flooding and split-horizon safeguards, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.
C:This alternative proposes: Validate multicast VPN control and data-plane dependencies before claiming a customer group's IP multicast stream should traverse an MPLS provider backbone. It concerns a different Junos engineering issue Multicast VPN provider and customer traffic separation, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.
Question 476
A Junos service-provider routing engineer investigates the following routing and service incident: A VPLS site stays reachable after PE maintenance, but the failover path has no documented service identifier or acceptance test, hiding a potential loop. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop.
- Verify service MTU and any supported pseudowire encapsulation/control-word expectations when a pseudowire is signaled Up but customer frames fail.
- Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion.
- Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs.
Explanation
Correct Answer
A:The case-specific routing and services action is: Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop.
Incorrect Answers
B:This alternative proposes: Verify service MTU and any supported pseudowire encapsulation/control-word expectations when a pseudowire is signaled Up but customer frames fail. It concerns a different Junos engineering issue Layer 2 pseudowire MTU and control-word interworking, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.
C:This alternative proposes: Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion. It concerns a different Junos engineering issue CoS schedulers scheduler-maps and bandwidth sharing, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.
D:This alternative proposes: Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs. It concerns a different Junos engineering issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.
Question 477
A provider routing design review considers this situation. A VPLS site stays reachable after PE maintenance, but the failover path has no documented service identifier or acceptance test, hiding a potential loop. A colleague proposes: Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop. Which technical principle BEST supports that action? Select ONE best answer.
- Multipoint Ethernet services learn source MAC locations and flood unknown unicast, broadcast and multicast within permitted service boundaries; split-horizon rules limit loop-causing PW-to-PW forwarding.
- EVPN commonly conveys MAC reachability through BGP route type 2; optional IP binding and policies support host learning and next-hop selection, while label or encapsulation rules depend on the deployment.
- VPLS site identification and multihoming mechanisms help coordinate PE access, but customer-facing redundant paths need a supported convergence and loop-control design.
- Junos routing policies match routes and apply actions at protocol boundaries; match order, accept/reject and explicit default behavior determine effective advertisements.
Explanation
Correct Answer
C:The relevant Junos service-provider networking principle is: VPLS site identification and multihoming mechanisms help coordinate PE access, but customer-facing redundant paths need a supported convergence and loop-control design. In the described provider-network case (A VPLS site stays reachable after PE maintenance, but the failover path has no documented service identifier or acceptance test, hiding a potential loop.), it supports the planned action: Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop.
Incorrect Answers
A:This alternative proposes: Multipoint Ethernet services learn source MAC locations and flood unknown unicast, broadcast and multicast within permitted service boundaries; split-horizon rules limit loop-causing PW-to-PW forwarding. It concerns a different Junos engineering issue VPLS MAC learning flooding and split-horizon safeguards, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.
B:This alternative proposes: EVPN commonly conveys MAC reachability through BGP route type 2; optional IP binding and policies support host learning and next-hop selection, while label or encapsulation rules depend on the deployment. It concerns a different Junos engineering issue EVPN MAC IP route type two control plane and learning, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.
D:This alternative proposes: Junos routing policies match routes and apply actions at protocol boundaries; match order, accept/reject and explicit default behavior determine effective advertisements. It concerns a different Junos engineering issue BGP export import policy and prefix controls, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.
Question 478
A Juniper service-provider engineer needs decisive verification evidence for this situation. A VPLS site stays reachable after PE maintenance, but the failover path has no documented service identifier or acceptance test, hiding a potential loop. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Inspect EVPN BGP family negotiation, MAC/IP advertisement, EVI/RT membership, remote PE next-hop reachability and learned MAC tables.
- Examine show route hidden, show route extensive, next-hop addresses, inet.0 or inet.3 as applicable, loopback IGP reachability and the labeled forwarding transport.
- Inspect VPLS instance configuration, signaling session state, remote PE discovery, VPLS route or LDP label distribution and actual MAC reachability.
- Check service-site IDs, multihoming preference, attachment circuits, signaling reachability, MAC moves and measured forwarding during failover.
Explanation
Correct Answer
D:The direct discriminating observation is: Check service-site IDs, multihoming preference, attachment circuits, signaling reachability, MAC moves and measured forwarding during failover. In the stated situation (A VPLS site stays reachable after PE maintenance, but the failover path has no documented service identifier or acceptance test, hiding a potential loop.), the intended acceptance outcome is: The authorized CE service survives a primary PE outage with the expected alternate active and without creating duplicated Ethernet forwarding.
Incorrect Answers
A:This alternative proposes: Inspect EVPN BGP family negotiation, MAC/IP advertisement, EVI/RT membership, remote PE next-hop reachability and learned MAC tables. It concerns a different Junos engineering issue EVPN MAC IP route type two control plane and learning, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.
B:This alternative proposes: Examine show route hidden, show route extensive, next-hop addresses, inet.0 or inet.3 as applicable, loopback IGP reachability and the labeled forwarding transport. It concerns a different Junos engineering issue BGP NEXT_HOP reachability and inet.3 recursion, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence in the stated situation (A VPLS site stays reachable after PE maintenance, but the failover path has no documented service identifier or acceptance test, hiding a potential loop.). A better case-specific check is: Check service-site IDs, multihoming preference, attachment circuits, signaling reachability, MAC moves and measured forwarding during failover. The more targeted action is: Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop.
C:This alternative proposes: Inspect VPLS instance configuration, signaling session state, remote PE discovery, VPLS route or LDP label distribution and actual MAC reachability. It concerns a different Junos engineering issue VPLS service control plane LDP versus BGP distribution, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.
Question 479
A service-provider acceptance team reviews the result of a provider-service change. A VPLS site stays reachable after PE maintenance, but the failover path has no documented service identifier or acceptance test, hiding a potential loop. The intended verification is: Check service-site IDs, multihoming preference, attachment circuits, signaling reachability, MAC moves and measured forwarding during failover. Which outcome BEST demonstrates success? Select ONE best answer.
- Customer dual-homing provides the intended redundancy without duplicate broadcast delivery or loss of reachability when either PE fails.
- The appropriate PEs establish only the requested customer Layer 2 connections and do not merge different customer switching domains.
- IPv6 customer and loopback prefixes are reachable along the intended paths while existing IPv4 OSPF operation is unchanged.
- The authorized CE service survives a primary PE outage with the expected alternate active and without creating duplicated Ethernet forwarding.
Explanation
Correct Answer
D:The verified success outcome is: The authorized CE service survives a primary PE outage with the expected alternate active and without creating duplicated Ethernet forwarding. Confirm this by: Check service-site IDs, multihoming preference, attachment circuits, signaling reachability, MAC moves and measured forwarding during failover. The related controlled intervention is: Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop.
Incorrect Answers
A:That option concerns EVPN Ethernet segment multihoming and designated forwarder. The related controlled intervention is: Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop.
B:That option concerns BGP-signaled Layer 2 VPN NLRI and route target import. The related controlled intervention is: Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop.
C:That option concerns OSPFv3 IPv6 neighbor and IPv4 separation. The related controlled intervention is: Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop.
Question 480
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. A VPLS site stays reachable after PE maintenance, but the failover path has no documented service identifier or acceptance test, hiding a potential loop. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Enable dense-mode flooding across the entire sparse subscriber backbone solely to correct one missing video stream without evaluating blast radius.
- Assume an Established IPv4-unicast-only BGP session automatically distributes BGP Layer 2 VPN NLRI and labels to every PE.
- Configure one PE for BGP-signaled VPLS and another for unrelated LDP service discovery then assume VLAN IDs alone create a multipoint interconnect.
- Assign identical customer site IDs to unrelated participating VPLS sites and assume unique identification is unimportant because the PEs have different loopbacks.
Explanation
Correct Answer
D:That conflicts with the edge-to-cloud principle: VPLS site identification and multihoming mechanisms help coordinate PE access, but customer-facing redundant paths need a supported convergence and loop-control design.
Incorrect Answers
A: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 VPLS site identifiers multihoming and service convergence.
B:This alternative proposes: Assume an Established IPv4-unicast-only BGP session automatically distributes BGP Layer 2 VPN NLRI and labels to every PE. It concerns a different Junos engineering issue BGP-signaled Layer 2 VPN NLRI and route target import, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.
C:This alternative proposes: Configure one PE for BGP-signaled VPLS and another for unrelated LDP service discovery then assume VLAN IDs alone create a multipoint interconnect. It concerns a different Junos engineering issue VPLS service control plane LDP versus BGP distribution, not the directly tested provider-network issue VPLS site identifiers multihoming and service convergence.