Sign in
Home/Juniper/Service Provider Routing and Switching, Professional (JNCIP-SP)/Free questions

Service Provider Routing and Switching, Professional (JNCIP-SP) — Free Practice Questions

10 free sample questions from a bank of 59, with the correct answers and explanations. No signup required — start practising right now.

1Click the Exhibit button. R2 is receiving the same route from R1 and R3. You must ensure that you can load balance traffic for that route. Referring to the exhibit, which configuration change will allow load balancing?
Service Provider Routing and Switching, Professional (JNCIP-SP) question 1
  • Configure the multipath parameter under the global BGP configuration.
  • Apply the prepend policy as an import policy under group R1.
  • Configure the multipath multiple-as parameter under the global BGP configuration.
  • Apply the prepend policy as an import policy under group R3.
Answer: C

C is correct. Load balancing an eBGP prefix that arrives from two different AS numbers needs multipath multiple-as under protocols bgp, because Junos only balances equal-cost paths from a single AS by default.

The short version

Load balancing an eBGP prefix that arrives from two different AS numbers needs multipath multiple-as under protocols bgp, because Junos only balances equal-cost paths from a single AS by default.

Key concepts

BGP multipath installs equal-cost paths into the forwarding table, but by default it only compares paths whose originating AS is the same. multiple-as relaxes that. An import policy with load-balance per-packet or per-prefix is a separate control.

Why C are correct

R2 has 11.11.11.0/24 from R1 (AS 65001) as active and from R3 (AS 65003) as backup. Both paths are eBGP and originate in different autonomous systems, so Junos will not treat them as multipath candidates unless multiple-as is added to the multipath statement under protocols bgp. The exhibit also shows a load-balance per-packet policy that is never attached to the forwarding table, but that is about the hashing action, not about which paths are eligible.

Why the others are wrong

  • A. Plain multipath is the default behaviour and only balances paths from the same AS, so it cannot combine the AS 65001 and AS 65003 paths here.
  • B. The prepend policy exports an AS path with 65001 prepended. Applying it as an import policy on R1 makes the path longer, not equal-cost, so it discourages rather than enables load balancing.
  • D. Same objection as B: importing the prepend policy on R3 artificially lengthens that AS path, so the two paths stop being equal cost.

JN0-664 exam tip

If a prefix is learned from two eBGP peers in different AS numbers and you want ECMP, the missing keyword is multiple-as. Multipath on its own is a same-AS feature.

2Click the Exhibit button. You are troubleshooting the connection between AS 64496 and AS 64497 and notice that only one of the paths is being used for traffic forwarding. Referring to the exhibit, which three actions will ensure that R1 is configured properly for load balancing BGP routes? (Choose three.)
Service Provider Routing and Switching, Professional (JNCIP-SP) question 2
  • Verify that the routing table on R1 has BGP routes for 203.0.113.128/25 with multiple next hops.
  • Verify that the multipath option is configured under protocols bgp on both R2 and R3.
  • Verify that there is a load balancing export policy under routing-options for the received BGP routes on R1.
  • Verify that the multipath option is configured under protocols bgp on R1.
  • Verify that an import load balancing policy exists under protocols bgp for the received BGP routes on R1.
Answer: A, C, D

ACD is correct. Three checks on R1: the routes for 203.0.113.128/25 must have several next hops in the RIB, multipath must be enabled under protocols bgp on R1, and a load-balancing export policy must exist under routing-options for the forwarding table.

The short version

Three checks on R1: the routes for 203.0.113.128/25 must have several next hops in the RIB, multipath must be enabled under protocols bgp on R1, and a load-balancing export policy must exist under routing-options for the forwarding table.

Key concepts

BGP routes enter the RIB automatically, but the forwarding table is populated separately, so set routing-options forwarding-table export <policy> is what puts multiple next hops into the FIB. A load-balancing import policy is a different thing and is not required once the export policy exists.

Why ACD are correct

The exhibit shows show route forwarding-table matching 203.0.113.128/25 returning eight addresses that all resolve to the single next hop 10.1.1.1, which is the symptom of no load balancing. A: the RIB on R1 must in fact contain multiple next hops for the prefix or nothing downstream can balance it. D: multipath is a receiving-side knob and only R1 is receiving, so it belongs on R1. C: the forwarding table is built from the RIB by the policies exported under routing-options, so the load-balancing action has to be attached there for the extra next hops to be used.

Why the others are wrong

  • B. Multipath on R2 and R3 changes what those routers do with their own received paths. Neither is a receiver of this prefix from R1, so their configuration is irrelevant.
  • E. An import load-balancing policy affects acceptance and attributes of received routes. The forwarding table is driven by the routing-options forwarding-table export policy, so an import policy alone leaves the extra next hops unused.

JN0-664 exam tip

Distinguish the RIB from the forwarding table. Multipath plus routing-options forwarding-table export is the working combination; an import policy changes what is accepted, not what is installed for forwarding.

3After a recent power outage, your manager asks you to investigate ways to automatically reduce the impact caused by suboptimal routing in your OSPF and OSPFv3 network after devices reboot. Which three configuration statements accomplish this task? (Choose three.)
  • set protocols ospf3 realm ipv4-unicast overload timeout 900
  • set protocols ospf overload
  • set protocols ospf overload timeout 900
  • set protocols ospf3 overload
  • set protocols ospf3 overload timeout 900
Answer: A, C, E

ACE is correct. Use overload together with timeout 900 -- in the OSPF instance and in the OSPFv3 instance, with the OSPFv3 statement scoped to the ipv4-unicast realm.

The short version

Use overload together with timeout 900 -- in the OSPF instance and in the OSPFv3 instance, with the OSPFv3 statement scoped to the ipv4-unicast realm.

Key concepts

set protocols ospf overload [timeout <seconds>] marks the router LSDB bit and makes it wait for the SPF calculation to finish, suppressing LSAs while it is stale. If no timeout is given the state persists until the statement is deleted. Under protocols ospf3 the realm-qualified form realm ipv4-unicast overload timeout 900 covers IPv4 carried in an OSPFv3 process.

Why ACE are correct

The requirement is to reduce the impact automatically after a reboot, which means the overload state must time out on its own. C does that for OSPF and E does it for OSPFv3. A does the same thing for OSPFv3 but constrains it to the IPv4-unicast realm, which is exactly the IPv4 case the manager described, and it is the realm-qualified spelling Junos accepts under protocols ospf3.

Why the others are wrong

  • B. set protocols ospf overload with no timeout leaves the router overloaded until an administrator deletes the statement, so nothing recovers automatically after the reboot.
  • D. Same failure as B: set protocols ospf3 overload with no timeout never clears itself.

JN0-664 exam tip

Any overload statement without a timeout value is a manual fix. In these questions the word 'automatically' is the hint that the timeout is mandatory.

4You are configuring anycast RP for load balancing and redundancy in your PIM-SM domain. You want to share active sources between RPs. In this scenario, what are two solutions that will accomplish this task? (Choose two.)
  • Configure MSDP on each RP router.
  • Configure anycast PIM with the rp-set statement on each RP router.
  • Configure anycast PIM with the rp-set statement on each source DR router.
  • Configure MSDP on each source DR router.
Answer: A, B

AB is correct. Either configure MSDP on each RP, or run anycast PIM and put the rp-set statement on each RP listing the other RPs in the domain.

The short version

Either configure MSDP on each RP, or run anycast PIM and put the rp-set statement on each RP listing the other RPs in the domain.

Key concepts

MSDP (Multicast Source Discovery Protocol) runs between RPs and lets each RP learn the (S,G) state its peers have, so sources behind one RP are usable through another. Anycast PIM gives all RPs one address and uses the rp-set statement plus MSDP or PIM to keep the RPs aware of each other's active sources.

Why AB are correct

Both A and B operate on the RPs. MSDP on each RP is the classic mechanism for sharing active sources between RPs, and anycast PIM with rp-set on each RP is the alternative: every RP advertises the list of RPs in the domain (up to 15) so that a source discovered by one RP is not lost. The rp-set statement belongs on the RPs because they are the peers that need to know about each other.

Why the others are wrong

  • C. rp-set on the source DR routers does nothing: the source DR is not an RP and never participates in the RP-to-RP source sharing that anycast PIM relies on.
  • D. MSDP is a protocol between RPs. Configuring it on the source DRs creates sessions toward RPs that will not run MSDP, so no source information is ever exchanged.

JN0-664 exam tip

Ask where the protocol runs. MSDP and rp-set both belong on the RPs; anything placed on a source DR or receiver DR is a distractor.

5Which two statements are correct about VPLS tunnels? (Choose two.)
  • BGP-signaled VPLS tunnels require manual provisioning of sites.
  • LDP-signaled VPLS tunnels only support control bit 0.
  • LDP-signaled VPLS tunnels use auto-discovery to provision sites.
  • BGP-signaled VPLS tunnels can use either RSVP or LDP between the PE routers.
Answer: B, D

BD is correct. LDP-signalled VPLS is control-bit 0 only, and BGP-signalled VPLS decouples the service from the transport so the pseudowire can ride an RSVP or an LDP LSP.

The short version

LDP-signalled VPLS is control-bit 0 only, and BGP-signalled VPLS decouples the service from the transport so the pseudowire can ride an RSVP or an LDP LSP.

Key concepts

VPLS (RFC 4762) carries Ethernet frames over an MPLS LSP using a split-horizon label and a VC label. LDP signalling requires every remote PE to be configured manually, while BGP signalling (RFC 4761) uses BGP extended communities and autodiscovery to build the full mesh of pseudowires. Either way the pseudowire is just an MPLS LSP, so any label distribution protocol can create it.

Why BD are correct

B is correct because Junos documents LDP-based VPLS as supporting control bit 0 only -- control bit 1 (which blocks locally learned MACs) is not offered for LDP signalling. D is correct because BGP-signalled VPLS advertises the service endpoints over BGP but does not care how the transport LSP is built; the inner and outer labels ride an ordinary MPLS LSP, and LDP, RSVP-TE, BGP-LU and segment routing are all valid transport choices.

Why the others are wrong

  • A. It is the other way round. BGP-signalled VPLS uses autodiscovery and VNI-based service signalling, so sites do not need manual provisioning.
  • C. LDP-signalled VPLS has no autodiscovery mechanism at all; auto-discovery exists only for the BGP-signalled (RFC 4761) flavour.

JN0-664 exam tip

Learn the pairing: LDP signalling = manual site configuration, control bit 0. BGP signalling = autodiscovery, transport-agnostic pseudowires.

6Click the Exhibit button. Referring to the exhibit, which two statements are true? (Choose two.)
Service Provider Routing and Switching, Professional (JNCIP-SP) question 6
  • The devices advertising this route into EVPN are 10.0.2.12 and 10.0.2.22.
  • This route is learned through EBGP.
  • The device advertising this route into EVPN is 192.168.101.5.
  • This is an EVPN Type-2 route.
Answer: C, D

CD is correct. This is an EVPN Type 2 MAC/IP route learned over iBGP, and the device that advertised it into EVPN is 192.168.101.5.

The short version

This is an EVPN Type 2 MAC/IP route learned over iBGP, and the device that advertised it into EVPN is 192.168.101.5.

Key concepts

A Type 2 MAC/IP Advertisement route carries the MAC address, optionally the IP, the Ethernet Tag, the ESI label and the MAC Mobility extended community. In Junos show route extensive the originator of such a route appears as Originator ID, the BGP Protocol next hop, and the RD administrator, while Indirect path forwarding next hops are the resolved tunnel next hops on the local side.

Why CD are correct

D is right because the route is printed as MAC/IP (2 entries, 1 announced), which is how Junos labels Type 2 EVPN NLRI. C is right because the entry shows Originator ID: 192.168.101.5, Protocol next hop: 192.168.101.5 and an RD administered by 192.168.101.5, so that PE is the one that put the MAC into EVPN. B is wrong on the face of the output: Local AS: 65101 Peer AS: 65101 is identical, so this is an iBGP-learned route.

Why the others are wrong

  • A. 10.0.2.12 and 10.0.2.22 appear under Indirect path forwarding next hops as Next hop: ... via et-0/0/0.0 and et-0/0/1.0. They are local equal-cost paths toward the originator, not the devices that advertised the MAC.
  • B. Local AS: 65101 Peer AS: 65101 -- the AS numbers are identical, so the route was learned over iBGP, not eBGP.

JN0-664 exam tip

In EVPN output the advertiser is the Originator ID / Protocol next hop / RD administrator. Everything under Indirect path forwarding next hops is a local tunnel next hop to that originator.

7Click the Exhibit button. You are running a service provider network and must transport a customer's IPv6 traffic across your IPv4-based MPLS network using BGP. You have already configured mpls ipv6-tunneling on your PE routers. Which two statements are correct about the BGP configuration in this scenario? (Choose two.)
Service Provider Routing and Switching, Professional (JNCIP-SP) question 7
  • You must configure family inet6 labeled-unicast between PE routers.
  • You must configure family inet6 add-path between PE and CE routers.
  • You must configure family inet6 unicast between PE and CE routers.
  • You must configure family inet6 unicast between PE routers.
Answer: A, C

AC is correct. Configure family inet6 labeled-unicast between the PE routers and family inet6 unicast between PE and CE. mpls ipv6-tunneling is already in place.

The short version

Configure family inet6 labeled-unicast between the PE routers and family inet6 unicast between PE and CE. mpls ipv6-tunneling is already in place.

Key concepts

mpls ipv6-tunneling lets an MX encapsulate IPv6 packets with an MPLS label stack and an IPv4 header so they can cross an IPv4 core. That only provides the transport -- BGP still needs two address families: a labelled family for the PE-PE session and a plain unicast family for the customer-facing session.

Why AC are correct

A is correct because the PE-to-PE session is the only place the IPv6 prefix can be advertised with an MPLS label, and without the label the packet cannot be tunnelled across the IPv4 core. C is correct because the CE routers do their own forwarding and must receive ordinary, unlabelled IPv6 unicast routes from the PE. Together they cover both legs of the VPN: labelled inside the provider, unlabelled at the edge.

Why the others are wrong

  • B. Add-path advertises multiple paths for the same prefix to help load balancing. It plays no part in carrying IPv6 over an IPv4 core and adds nothing to the label encapsulation.
  • D. An unlabelled family inet6 unicast between PEs gives the PE-PE session no MPLS label to push, so the IPv6 traffic cannot be tunnelled through the IPv4 MPLS network even with mpls ipv6-tunneling enabled.

JN0-664 exam tip

Rule of thumb for IPv6-over-IPv4 MPLS: labelled-unicast on the core-facing session, plain unicast on the customer-facing session.

8When using 0SPFv3 for an IPv4 environment, which statement is correct?
  • OSPFv3 only supports IPv4.
  • OSPFv3 is not backward compatible with IPv4.
  • OSPFv3 supports both IPv6 and IPv4, but not in the same routing instance.
  • OSPFv3 supports IPv4 only on interfaces with family inet6 defined.
Answer: D

D is correct. OSPFv3 can carry IPv4 routes, but only on interfaces where family inet6 is configured, because the protocol itself runs over IPv6 link-local addresses.

The short version

OSPFv3 can carry IPv4 routes, but only on interfaces where family inet6 is configured, because the protocol itself runs over IPv6 link-local addresses.

Key concepts

OSPFv3 (RFC 5340) replaced the IPv4-specific protocol packets of OSPFv2 with generic IPv6 ones and derives the router ID from a link-local address. Junos therefore requires family inet6 on the interface before an OSPFv3 adjacency will form. IPv4 reachability inside an OSPFv3 process is handled by set protocols ospf3 realm ipv4-unicast, which advertises the IPv4 address family as an extended prefix TLV.

Why D are correct

OSPFv3's hello and database description packets are IPv6 packets sent to the reserved link-local multicast address ff02::5, and the interface must hold an IPv6 link-local address for that to happen. So even when the point of the process is to redistribute IPv4 prefixes, the interface has to be in the inet6 address family. The other three statements either invert the relationship or overstate it.

Why the others are wrong

  • A. Backwards. OSPFv3 is the IPv6-native version; it is OSPFv2 that only supports IPv4.
  • B. OSPFv3 is not 'not backward compatible' -- it can advertise both IPv6 and IPv4 in the same routing instance via realms, which is precisely why option D needs the family inet6 caveat.
  • C. It can do exactly that: set protocols ospf3 realm ipv4-unicast and the native IPv6 realm coexist in the same OSPFv3 routing instance.

JN0-664 exam tip

OSPFv3 needs IPv6 on the wire even when the payload is IPv4. If an adjacency will not come up, check for family inet6 on the interface first.

9You are a network architect for a service provider and want to offer Layer 2 services to your customers. You want to use EVPN for Layer 2 services in your existing MPLS network. Which two statements are correct in this scenario? (Choose two.)
  • Segment routing must be configured on all PE routers.
  • EVPN uses Type 2 routes to advertise MAC address and IP address pairs learned using ARP snooping.
  • EVPN uses Type 3 routes to join a multicast tree to flood traffic.
  • VXLAN must be configured on all PE routers.
Answer: B, C

BC is correct. Type 2 routes distribute MAC (and IP) bindings; Type 3 routes set up the inclusive-multicast tree that carries broadcast, unknown unicast and multicast. Nothing in the question requires segment routing or VXLAN.

The short version

Type 2 routes distribute MAC (and IP) bindings; Type 3 routes set up the inclusive-multicast tree that carries broadcast, unknown unicast and multicast. Nothing in the question requires segment routing or VXLAN.

Key concepts

EVPN (RFC 7432) reuses MP-BGP to signal an Ethernet service. Type 2 is MAC/IP Advertisement and is the control-plane replacement for MAC learning. Type 3 is Inclusive Multicast (Ethernet Tag) and is the ingress-replication control plane for BUM traffic. Type 1 and Type 4 handle autodiscovery, multihoming and fast convergence.

Why BC are correct

B is correct: Type 2 routes are how a PE learns which MAC lives behind which PE, which is exactly what is needed instead of flooding every unknown destination. C is correct: with ingress replication, a Type 3 route per EVI tells the remote PEs to join a P2MP tree for that EVI so broadcast, unknown unicast and multicast are forwarded along it. A and D describe transport choices, and EVPN in an MPLS network runs over plain BGP VPNv4 with no requirement for segment routing or for a VXLAN data plane.

Why the others are wrong

  • A. Segment routing is an MPLS transport option. EVPN control plane works fine with LDP or RSVP-TE pseudowires, so it is not a prerequisite.
  • D. VXLAN is a data-plane encapsulation used for EVPN-VXLAN in the data centre. An EVPN service carried over an MPLS core uses VPNv4 signalling and does not need VXLAN anywhere.

JN0-664 exam tip

Type 2 = MAC reachability, Type 3 = BUM replication. Anything that is a transport or encapsulation choice (segment routing, VXLAN) is never a prerequisite for EVPN itself.

10You are configuring a Layer 3 VPN between two sites. You are configuring the vrf-target target: 65100:100 statement in your routing instance. In this scenario, which two statements describe the vrf-target configuration? (Choose two.)
  • This value is used to identify BGP routes learned from the remote PE device.
  • This value is used to add a target community to BGP routes advertised to the local CE device.
  • This value is used to add a target community to BGP routes advertised to the remote PE device.
  • This value is used to identify BGP routes learned from the local CE device.
Answer: A, C

AC is correct. vrf-target target:65100:100 does two things: it tags routes advertised toward the remote PEs, and on import it selects which of those routes land in this VRF.

The short version

vrf-target target:65100:100 does two things: it tags routes advertised toward the remote PEs, and on import it selects which of those routes land in this VRF.

Key concepts

A route target is an extended community in the form target:<admin>:<assigned>. In an vrf-target statement Junos both attaches the community on export to the MP-BGP update sent to remote PEs and matches it on import. That is how the VPN stays private: routes from other VPNs simply do not carry your target, so they are not imported.

Why AC are correct

C is correct because when the PE exports VPN routes to its remote-PE peers it stamps target:65100:100 on them; without the community the remote site could not tell which routes belong to this VPN. A is the mirror of that statement: on the way in, the same value is used to identify which BGP-learned routes belong to this VRF, so it identifies routes learned from the remote PE. Together they are the two halves of one mechanism, which is why this is a choose-two.

Why the others are wrong

  • B. The community is never added to what is advertised to the local CE. PE-CE sessions are plain IPv4 or IPv6 unicast with no route-target community on them.
  • D. The value is not used to identify routes learned from the local CE -- those come in over the PE-CE session and are placed in the VRF by the routing protocol itself, with no target matching involved.

JN0-664 exam tip

Route targets are an MP-BGP control-plane mechanism. They only ever appear on PE-PE updates, never on PE-CE updates.

Want the full bank of 59 questions for Service Provider Routing and Switching, Professional (JNCIP-SP)? See all practice exams.