Juniper Service Provider Routing and Switching, Specialist (JNCIS-SP) JN0-363 Exam Dumps: Updated Questions & Answers (November 2025)

For IS-IS to form adjacencies, the 'family iso' statement must be configured on the interface. This is required because IS-IS operates over the connectionless network service (CLNS) and not over IP. Without the 'family iso' configuration, IS-IS cannot form adjacencies over the interface.

To influence the path taken through an autonomous system, the Multi-Exit Discriminator (MED) attribute can be used. By setting a lower MED on R2 for routes advertised to R1 and R3, it will make the path through R2 to the 203.0.113.0/24 network more preferable.

Filter-based forwarding in Junos requires the creation of a routing policy to specify the match conditions and actions and the application of a match filter to classify traffic to use the policy.

Referring to the configuration in the exhibit, R1 is set to export the 3rd_Policy to the neighbor at 192.168.1.5. Since 3rd_Policy permits the 10.200.3.0/24 prefix, only that prefix will be advertised to the neighbor.

Considering the bandwidth reservations shown, the only path from R4 to R6 that has sufficient available bandwidth for a new LSP with 400 Mbps reservation is via R1, R2, and R5. This is because the R4-R5 direct link and the R4-R1-R2-R3-R6 path do not have enough unreserved bandwidth to accommodate an additional 400 Mbps LSP.

In the exhibit, the interface is configured with the native-vlan-id 20 parameter. This means that any untagged frames arriving on this interface will be associated with VLAN 20. The native VLAN serves as the default VLAN for untagged frames on a trunk port.

https://www.networkfuntimes.com/junos-aggregate-routes-vs-generate-routes-how-to-summarise-on-juniper-routers/

Generated routes are a type of route that can be created to summarize and generate more specific routes within the routing table. Unlike aggregate routes, which summarize existing routes and inherit a next-hop, generated routes do not necessarily have to match an existing route and will have a next-hop of reject by default unless specified otherwise.

References

Juniper Networks Technical Documentation on Routing Policies and Route Generation

BGP selects the active route based on an ordered list of attributes. The correct order is:

Weight (Cisco proprietary, not listed in the options)

Local Preference

Network (route) originated from the BGP router itself

Shortest AS Path

Lowest Origin Type

Lowest MED

eBGP over iBGP paths

Closest IGP Neighbor

Lowest Router ID

The next hop is checked for reachability but is not part of the BGP decision process for selecting the best path.

References

Juniper Networks Technical Documentation on BGP

To configure OSPFv3 (the version of OSPF that supports IPv6), you would use the set protocols ospf3 command with the appropriate area and interface. OSPFv3 requires a 32-bit router ID just like OSPFv2, which is typically an IPv4 address. OSPF does not use a 128-bit router ID, so answer D is incorrect.

By default, the router that originally sourced the route into BGP places its peer address into the attribute field. The next-hop value is then typically changed when the route is transmitted across external gGP (EBGP) links. Internal BGP (IBGP) peers do not alter the next-hop value between themselves.

B. By default, the next-hop value is changed when a route is passed from an EBGP peer to another EBGP peer.

C. By default, the next-hop value is retained when a route is advertised across IBGP links.