Juniper JN0-664 Practice Test 45
Question 440
A Junos service-provider routing engineer investigates this service-provider network scenario. One PE enables pseudowire control-word handling and the remote PE uses a mismatched expectation, causing otherwise healthy transport to misinterpret payloads. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.
- Validate Designated Intermediate System behavior on a LAN segment rather than confusing it with the OSPF DR/BDR algorithm.
- Implement intended full-mesh or hub-and-spoke VPN reachability with precise route-target and policy behavior, including explicitly approved Internet access.
- Compare CE frame sizes, attachment-circuit encapsulation, pseudowire MTU, control-word configuration, interface drops and forwarding test results at both PEs.
- Inspect VPLS instance configuration, signaling session state, remote PE discovery, VPLS route or LDP label distribution and actual MAC reachability.
- Verify service MTU and any supported pseudowire encapsulation/control-word expectations when a pseudowire is signaled Up but customer frames fail.
Explanation
Correct Answers
C:The direct discriminating observation is: Compare CE frame sizes, attachment-circuit encapsulation, pseudowire MTU, control-word configuration, interface drops and forwarding test results at both PEs.
E:The case-specific routing and services action is: Verify service MTU and any supported pseudowire encapsulation/control-word expectations when a pseudowire is signaled Up but customer frames fail.
Incorrect Answers
A: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 Layer 2 pseudowire MTU and control-word interworking.
B:This alternative proposes: Implement intended full-mesh or hub-and-spoke VPN reachability with precise route-target and policy behavior, including explicitly approved Internet access. It concerns a different Junos engineering issue Layer 3 VPN hub spoke topology and controlled Internet breakout, not the directly tested provider-network issue Layer 2 pseudowire MTU and control-word interworking.
D: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 Layer 2 pseudowire MTU and control-word interworking.
Question 441
A Junos service-provider routing engineer investigates the following routing and service incident: Two edge nodes can ping each other's loopbacks but their BGP Layer 2 VPN never comes Up because the required signaling family was not negotiated. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Verify service MTU and any supported pseudowire encapsulation/control-word expectations when a pseudowire is signaled Up but customer frames fail.
- Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings.
- 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.
Explanation
Correct Answer
B:The case-specific routing and services action is: Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings. The governing Junos routing/service principle is: A BGP-signaled Layer 2 VPN advertises service-related NLRI and label reachability; route-target and instance-policy behavior determine which remote service participates.
Incorrect Answers
A: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 BGP-signaled Layer 2 VPN NLRI and route target import.
C:This alternative proposes: Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop. It concerns a different Junos engineering issue VPLS site identifiers multihoming and service convergence, not the directly tested provider-network issue BGP-signaled Layer 2 VPN NLRI and route target import.
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 BGP-signaled Layer 2 VPN NLRI and route target import.
Question 442
A provider routing design review considers this situation. Two edge nodes can ping each other's loopbacks but their BGP Layer 2 VPN never comes Up because the required signaling family was not negotiated. A colleague proposes: Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings. Which technical principle BEST supports that action? Select ONE best answer.
- 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.
- A BGP-signaled Layer 2 VPN advertises service-related NLRI and label reachability; route-target and instance-policy behavior determine which remote service participates.
- Pseudowire transport can impose encapsulation overhead and require compatible payload/MTU or control-word behavior; signaling Up does not guarantee all customer frame sizes are successfully delivered.
- 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
B:The relevant Junos service-provider networking principle is: A BGP-signaled Layer 2 VPN advertises service-related NLRI and label reachability; route-target and instance-policy behavior determine which remote service participates. In the described provider-network case (Two edge nodes can ping each other's loopbacks but their BGP Layer 2 VPN never comes Up because the required signaling family was not negotiated.), it supports the planned action: Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings.
Incorrect Answers
A: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 BGP-signaled Layer 2 VPN NLRI and route target import.
C:This alternative proposes: Pseudowire transport can impose encapsulation overhead and require compatible payload/MTU or control-word behavior; signaling Up does not guarantee all customer frame sizes are successfully delivered. It concerns a different Junos engineering issue Layer 2 pseudowire MTU and control-word interworking, not the directly tested provider-network issue BGP-signaled Layer 2 VPN NLRI and route target import.
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 BGP-signaled Layer 2 VPN NLRI and route target import.
Question 443
A Juniper service-provider engineer needs decisive verification evidence for this situation. Two edge nodes can ping each other's loopbacks but their BGP Layer 2 VPN never comes Up because the required signaling family was not negotiated. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- 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.
- Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state.
- Inspect BGP family negotiation, received Layer 2 VPN routes, RD/RT communities, service site identifiers, label mapping and per-instance state.
Explanation
Correct Answer
D:The direct discriminating observation is: Inspect BGP family negotiation, received Layer 2 VPN routes, RD/RT communities, service site identifiers, label mapping and per-instance state. In the stated situation (Two edge nodes can ping each other's loopbacks but their BGP Layer 2 VPN never comes Up because the required signaling family was not negotiated.), the intended acceptance outcome is: The appropriate PEs establish only the requested customer Layer 2 connections and do not merge different customer switching domains.
Incorrect Answers
A:This alternative proposes: Check service-site IDs, multihoming preference, attachment circuits, signaling reachability, MAC moves and measured forwarding during failover. It concerns a different Junos engineering issue VPLS site identifiers multihoming and service convergence, not the directly tested provider-network issue BGP-signaled Layer 2 VPN NLRI and route target import.
B: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 BGP-signaled Layer 2 VPN NLRI and route target import.
C:This alternative proposes: Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state. It concerns a different Junos engineering issue BGP export import policy and prefix controls, not the directly tested provider-network issue BGP-signaled Layer 2 VPN NLRI and route target import.
Question 444
A service-provider acceptance team reviews the result of a provider-service change. Two edge nodes can ping each other's loopbacks but their BGP Layer 2 VPN never comes Up because the required signaling family was not negotiated. The intended verification is: Inspect BGP family negotiation, received Layer 2 VPN routes, RD/RT communities, service site identifiers, label mapping and per-instance state. Which outcome BEST demonstrates success? Select ONE best answer.
- Participating customer sites exchange permitted Ethernet frames through a correctly signaled multipoint service without bridging unrelated tenants.
- The configured mode serves actual receivers without uncontrolled multicast flood in sparsely subscribed provider regions.
- The authorized CE service survives a primary PE outage with the expected alternate active and without creating duplicated Ethernet forwarding.
- The appropriate PEs establish only the requested customer Layer 2 connections and do not merge different customer switching domains.
Explanation
Correct Answer
D:The verified success outcome is: The appropriate PEs establish only the requested customer Layer 2 connections and do not merge different customer switching domains. Confirm this by: Inspect BGP family negotiation, received Layer 2 VPN routes, RD/RT communities, service site identifiers, label mapping and per-instance state.
Incorrect Answers
A:That option concerns VPLS service control plane LDP versus BGP distribution. The related controlled intervention is: Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings.
B:That option concerns PIM dense mode versus sparse mode interface deployment. The related controlled intervention is: Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings.
C:This alternative proposes: The authorized CE service survives a primary PE outage with the expected alternate active and without creating duplicated Ethernet forwarding. It concerns a different Junos engineering issue VPLS site identifiers multihoming and service convergence, not the directly tested provider-network issue BGP-signaled Layer 2 VPN NLRI and route target import.
Question 445
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. Two edge nodes can ping each other's loopbacks but their BGP Layer 2 VPN never comes Up because the required signaling family was not negotiated. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Declare a pseudowire healthy based only on an Up connection flag despite large tagged frames being dropped on a transport link with insufficient payload MTU.
- Assume an Established IPv4-unicast-only BGP session automatically distributes BGP Layer 2 VPN NLRI and labels to every PE.
- Assume a core link with more bandwidth automatically has the lowest IS-IS metric when no operator metric policy has been configured.
- Assume every MAC learned on an EVPN remote PE must be discovered exclusively by data-plane flood without any BGP MAC/IP advertisement.
Explanation
Correct Answer
B:That conflicts with the edge-to-cloud principle: A BGP-signaled Layer 2 VPN advertises service-related NLRI and label reachability; route-target and instance-policy behavior determine which remote service participates.
Incorrect Answers
A:This alternative proposes: Declare a pseudowire healthy based only on an Up connection flag despite large tagged frames being dropped on a transport link with insufficient payload MTU. It concerns a different Junos engineering issue Layer 2 pseudowire MTU and control-word interworking, not the directly tested provider-network issue BGP-signaled Layer 2 VPN NLRI and route target import.
C:This alternative proposes: Assume a core link with more bandwidth automatically has the lowest IS-IS metric when no operator metric policy has been configured. It concerns a different Junos engineering issue IS-IS wide metrics traffic engineering and cost selection, not the directly tested provider-network issue BGP-signaled Layer 2 VPN NLRI and route target import.
D:This alternative proposes: Assume every MAC learned on an EVPN remote PE must be discovered exclusively by data-plane flood without any BGP MAC/IP advertisement. It concerns a different Junos engineering issue EVPN MAC IP route type two control plane and learning, not the directly tested provider-network issue BGP-signaled Layer 2 VPN NLRI and route target import.
Question 446
A Junos service-provider routing engineer investigates the following routing and service incident: A customer circuit's BGP service route is received on a remote PE but is excluded from the correct instance by a route-target import mismatch. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings.
- Use reverse-path forwarding checks to determine why an arriving multicast packet is accepted on one interface but discarded on another.
- Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs.
- Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop.
Explanation
Correct Answer
A:The case-specific routing and services action is: Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings. The governing Junos routing/service principle is: A BGP-signaled Layer 2 VPN advertises service-related NLRI and label reachability; route-target and instance-policy behavior determine which remote service participates. Verify the decision through: Inspect BGP family negotiation, received Layer 2 VPN routes, RD/RT communities, service site identifiers, label mapping and per-instance state.
Incorrect Answers
B: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 BGP-signaled Layer 2 VPN NLRI and route target import.
C: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 BGP-signaled Layer 2 VPN NLRI and route target import.
D:This alternative proposes: Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop. It concerns a different Junos engineering issue VPLS site identifiers multihoming and service convergence, not the directly tested provider-network issue BGP-signaled Layer 2 VPN NLRI and route target import.
Question 447
A provider routing design review considers this situation. A customer circuit's BGP service route is received on a remote PE but is excluded from the correct instance by a route-target import mismatch. A colleague proposes: Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings. Which technical principle BEST supports that action? Select ONE best answer.
- 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.
- A BGP-signaled Layer 2 VPN advertises service-related NLRI and label reachability; route-target and instance-policy behavior determine which remote service participates.
- IS-IS uses LSPs to distribute link-state topology and SNP mechanisms to synchronize databases; incomplete flooding can leave routers computing different SPF paths.
- VPLS site identification and multihoming mechanisms help coordinate PE access, but customer-facing redundant paths need a supported convergence and loop-control design.
Explanation
Correct Answer
B:The relevant Junos service-provider networking principle is: A BGP-signaled Layer 2 VPN advertises service-related NLRI and label reachability; route-target and instance-policy behavior determine which remote service participates. In the described provider-network case (A customer circuit's BGP service route is received on a remote PE but is excluded from the correct instance by a route-target import mismatch.), it supports the planned action: Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings.
Incorrect Answers
A: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 BGP-signaled Layer 2 VPN NLRI and route target import.
C:This alternative proposes: IS-IS uses LSPs to distribute link-state topology and SNP mechanisms to synchronize databases; incomplete flooding can leave routers computing different SPF paths. It concerns a different Junos engineering issue IS-IS link-state packet flooding and database consistency, not the directly tested provider-network issue BGP-signaled Layer 2 VPN NLRI and route target import.
D:This alternative proposes: VPLS site identification and multihoming mechanisms help coordinate PE access, but customer-facing redundant paths need a supported convergence and loop-control design. It concerns a different Junos engineering issue VPLS site identifiers multihoming and service convergence, not the directly tested provider-network issue BGP-signaled Layer 2 VPN NLRI and route target import.
Question 448
A Juniper service-provider engineer needs decisive verification evidence for this situation. A customer circuit's BGP service route is received on a remote PE but is excluded from the correct instance by a route-target import mismatch. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Inspect BGP family negotiation, received Layer 2 VPN routes, RD/RT communities, service site identifiers, label mapping and per-instance state.
- Inspect show route table bgp.l3vpn.0, instance.inet.0, accepted RT communities, next-hop resolution and label information at both PEs.
- Inspect Ethernet segment configuration, ESI values, DF election or relevant designated-forwarder state, ES routes, BGP reachability and measured failover forwarding.
- Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability.
Explanation
Correct Answer
A:The direct discriminating observation is: Inspect BGP family negotiation, received Layer 2 VPN routes, RD/RT communities, service site identifiers, label mapping and per-instance state. In the stated situation (A customer circuit's BGP service route is received on a remote PE but is excluded from the correct instance by a route-target import mismatch.), the intended acceptance outcome is: The appropriate PEs establish only the requested customer Layer 2 connections and do not merge different customer switching domains.
Incorrect Answers
B:This alternative proposes: Inspect show route table bgp.l3vpn.0, instance.inet.0, accepted RT communities, next-hop resolution and label information at both PEs. It concerns a different Junos engineering issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables, not the directly tested provider-network issue BGP-signaled Layer 2 VPN NLRI and route target import in the stated situation (A customer circuit's BGP service route is received on a remote PE but is excluded from the correct instance by a route-target import mismatch.). A better case-specific check is: Inspect BGP family negotiation, received Layer 2 VPN routes, RD/RT communities, service site identifiers, label mapping and per-instance state. The more targeted action is: Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings.
C:This alternative proposes: Inspect Ethernet segment configuration, ESI values, DF election or relevant designated-forwarder state, ES routes, BGP reachability and measured failover forwarding. It concerns a different Junos engineering issue EVPN Ethernet segment multihoming and designated forwarder, not the directly tested provider-network issue BGP-signaled Layer 2 VPN NLRI and route target import.
D: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 BGP-signaled Layer 2 VPN NLRI and route target import.
Question 449
A service-provider acceptance team reviews the result of a provider-service change. A customer circuit's BGP service route is received on a remote PE but is excluded from the correct instance by a route-target import mismatch. The intended verification is: Inspect BGP family negotiation, received Layer 2 VPN routes, RD/RT communities, service site identifiers, label mapping and per-instance state. Which outcome BEST demonstrates success? Select ONE best answer.
- Clients receive authorized routes without a full iBGP mesh and no reflected route loops or unreachable forwarding next hops develop.
- The appropriate PEs establish only the requested customer Layer 2 connections and do not merge different customer switching domains.
- The authorized CE service survives a primary PE outage with the expected alternate active and without creating duplicated Ethernet forwarding.
- The two attachment circuits join only their authorized sites and the pseudowire status and customer traffic counters remain stable.
Explanation
Correct Answer
B:The verified success outcome is: The appropriate PEs establish only the requested customer Layer 2 connections and do not merge different customer switching domains. Confirm this by: Inspect BGP family negotiation, received Layer 2 VPN routes, RD/RT communities, service site identifiers, label mapping and per-instance state. The related controlled intervention is: Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings.
Incorrect Answers
A:This alternative proposes: Clients receive authorized routes without a full iBGP mesh and no reflected route loops or unreachable forwarding next hops develop. It concerns a different Junos engineering issue BGP route reflectors originator and cluster loop prevention, not the directly tested provider-network issue BGP-signaled Layer 2 VPN NLRI and route target import.
C:This alternative proposes: The authorized CE service survives a primary PE outage with the expected alternate active and without creating duplicated Ethernet forwarding. It concerns a different Junos engineering issue VPLS site identifiers multihoming and service convergence, not the directly tested provider-network issue BGP-signaled Layer 2 VPN NLRI and route target import.
D:That option concerns LDP signaled Layer 2 circuit pseudowire status and VC identifiers. The related controlled intervention is: Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings.
Question 450
A Junos service-provider routing engineer investigates this service-provider network scenario. A customer circuit's BGP service route is received on a remote PE but is excluded from the correct instance by a route-target import mismatch. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.
- Inspect BGP family negotiation, received Layer 2 VPN routes, RD/RT communities, service site identifiers, label mapping and per-instance state.
- Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings.
- Check service-site IDs, multihoming preference, attachment circuits, signaling reachability, MAC moves and measured forwarding during failover.
- Classify subscriber traffic with an appropriate behavior-aggregate or multifield classifier and confirm forwarding-class assignments at ingress.
- Validate multicast VPN control and data-plane dependencies before claiming a customer group's IP multicast stream should traverse an MPLS provider backbone.
Explanation
Correct Answers
A:The direct discriminating observation is: Inspect BGP family negotiation, received Layer 2 VPN routes, RD/RT communities, service site identifiers, label mapping and per-instance state.
B:The case-specific routing and services action is: Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings.
Incorrect Answers
C:This alternative proposes: Check service-site IDs, multihoming preference, attachment circuits, signaling reachability, MAC moves and measured forwarding during failover. It concerns a different Junos engineering issue VPLS site identifiers multihoming and service convergence, not the directly tested provider-network issue BGP-signaled Layer 2 VPN NLRI and route target import.
D:This alternative proposes: Classify subscriber traffic with an appropriate behavior-aggregate or multifield classifier and confirm forwarding-class assignments at ingress. It concerns a different Junos engineering issue Junos CoS behavior aggregate versus multifield classifiers, not the directly tested provider-network issue BGP-signaled Layer 2 VPN NLRI and route target import.
E: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 BGP-signaled Layer 2 VPN NLRI and route target import.