
JN0-364 Service Provider Routing and Switching, Specialist (JNCIS-SP)
The JN0-364 Service Provider Routing and Switching, Specialist Exam is designed
for networking professionals who want to demonstrate intermediate-level
knowledge of Juniper networking technologies and Junos OS in service provider
environments. The JNCIS-SP certification validates the ability to understand,
configure, monitor, and troubleshoot important routing, switching, MPLS, IPv6,
tunneling, and high-availability technologies.
According to the current Juniper certification overview, the JN0-364 exam is
associated with the JNCIS-SP certification, requires JNCIA-Junos as a
prerequisite, contains 65 multiple-choice questions, has a 90-minute duration,
is delivered through Pearson VUE, and currently references Junos OS 25.2.
Juniper announced an updated Service Provider Routing and Switching Specialist
exam effective February 2026.
For candidates searching for JN0-364 practice resources, Certkingdom.com
provides exam preparation materials designed to help learners review important
concepts, practice exam-style questions, and identify areas requiring additional
study. Certkingdom.com
Topics Covered in the JN0-364 Exam
The JN0-364 Service Provider Routing and Switching Specialist exam covers the
following major areas:
1. Protocol-Independent Routing
Candidates should understand:
Static routes
Aggregate routes
Generated routes
Martian addresses
Routing instances
Routing Information Base (RIB) groups
Load balancing
Filter-based forwarding
Configuration and troubleshooting of routing components
2. OSPF
Important OSPF topics include:
Link-state databases
OSPF packet types
Router ID
OSPF neighbors and adjacencies
DR and BDR election
OSPF areas
Router types
Link-State Advertisements
Interface configuration
Routing policies
OSPF troubleshooting
3. IS-IS
Students should prepare for:
IS-IS link-state databases
Protocol Data Units
TLVs
IS-IS neighbors and adjacencies
Levels and areas
Designated Intermediate System
IS-IS metrics
Interface configuration
Routing policy
IS-IS troubleshooting
4. BGP
Key BGP subjects include:
BGP operation
BGP message types
BGP attributes
Route selection
Path selection
IBGP
EBGP
BGP groups
BGP peers
Basic BGP options
Routing policy application
BGP monitoring and troubleshooting
5. Layer 2 Bridging and VLANs
Candidates should understand:
Service provider switching platforms
Bridging terminology
Frame processing
Virtual switches
Provider bridging
Q-in-Q tunneling
VLAN port modes
VLAN tagging
Integrated Routing and Bridging (IRB)
6. Spanning Tree Protocols
Topics include:
STP
RSTP
MSTP
VSTP
Port roles
Port states
BPDUs
Convergence
Reconvergence
BPDU protection
Loop protection
Root protection
7. MPLS
MPLS is an important section of JN0-364 preparation:
MPLS terminology
MPLS packet headers
Packet forwarding
MPLS labels
Label Information Base
MPLS routing tables
RSVP
LDP
Segment Routing with MPLS
MPLS forwarding
RSVP-signaled LSPs
LDP-signaled LSPs
Segment-routing LSPs
8. IPv6
Candidates should prepare for:
IPv6 static routes
OSPFv3
IS-IS for IPv6
BGP for IPv6
IPv6 troubleshooting
IPv6 over IPv4 tunneling
9. IP Tunnels
Important concepts include:
IP tunneling applications
Tunneling requirements
Generic Routing Encapsulation
GRE configuration
GRE monitoring
GRE troubleshooting
10. High Availability
Students should understand:
Link Aggregation Groups
Graceful Restart
Graceful Routing Engine Switchover
Nonstop Bridging
Nonstop Active Routing
Bidirectional Forwarding Detection
VRRP
High-availability monitoring
Redundancy troubleshooting
These objectives are based on Juniper's published JNCIS-SP exam objectives and preparation guidance.
JN0-364 Brain Dumps Exam + Online / Offline and Android Testing Engine & 4500+ other exams included
$50 - $25 (you save $25)
Buy Now
Question: 1
You are troubleshooting a Level 1 IS-IS router that has an adjacency with a
Level 1/2 router.
Which two statements are correct in this scenario? (Choose two.)
A. The Level 1/2 router merges Level 1 and Level 2 into one complete topology.
B. The Level 1 router will learn the full topology of the Level 2 network.
C. The Level 1/2 router sees the Level 1 network and the Level 2 network as two
separate topologies.
D. The Level 1 router will only learn the topology of the Level 1 network.
Answer: C, D
Explanation:
In the context of Juniper Networks Junos OS and the IS-IS (Intermediate System
to Intermediate
System) protocol, understanding the hierarchical relationship between router
levels is critical for
effective troubleshooting and design. IS-IS uses a two-level hierarchy to manage
scalability: Level 1
(L1), which represents intra-area routing, and Level 2 (L2), which represents
inter-area backbone routing.
When a router is configured as a Level 1/2 (L1/L2) device, it acts as a bridge
between the two levels.
According to Juniper technical documentation, an L1/L2 router maintains two
completely separate
Link-State Databases (LSDB)—one for Level 1 and one for Level 2. It does not
merge these into a
single topology. This separation ensures that local area topology changes (L1)
do not necessarily
flood into the backbone (L2) unless specific redistribution is configured, and
vice versa. Therefore,
statement C is correct because the L1/L2 router maintains distinct SPF (Shortest
Path First)
computations for each level.
Regarding the visibility of the Level 1 router, IS-IS is designed to keep L1
areas -stubby- by default. A
Level 1 router only possesses the topology information for its own area (the
Level 1 LSDB). It does
not receive specific L2 routes or the L2 topology. Instead, the L1/L2 router
sets the Attached (ATT) bit
in its L1 Link-State PDUs (LSPs) to signal to L1-only routers that it has a
connection to the backbone.
The L1 router then generates a default route pointing to the L1/L2 router to
reach inter-area
destinations. This confirms that statement D is correct: the L1 router's
knowledge is limited to its local L1 topology.
Conversely, statements A and B are incorrect because merging topologies would
violate the
hierarchical scaling principles of IS-IS, and L1 routers never learn the full L2
topology without explicit,
non-standard route leaking.
Question: 2
By default, which routing table contains a list of all ingress LSPs?
A. inet.2
B. inet.3
C. inet.1
D. inet.0
Answer: B
Explanation:
In the Juniper Networks Junos operating system, the management of routing
information is
partitioned into several distinct routing tables (RIBs), each serving a specific
architectural purpose.
When dealing with Multiprotocol Label Switching (MPLS), understanding the
distinction between
inet.0 and inet.3 is fundamental for troubleshooting and traffic engineering.
The inet.3 routing table is specifically designed to store the egress IPv4
addresses of Label-Switched
Paths (LSPs). When an ingress router successfully establishes an LSP (via RSVP
or LDP), it places the
host address of the egress router (the tail-end) into the inet.3 table. This
table is not used for general
packet forwarding; instead, it is primarily used by the Border Gateway Protocol
(BGP) for next-hop
resolution. When BGP receives a route, it checks both inet.0 and inet.3 to
resolve the next hop. If a
matching entry exists in inet.3, the router knows it can reach that destination
via an MPLS tunnel,
allowing for the encapsulation of BGP traffic within MPLS.
In contrast, inet.0 is the default unicast routing table used for standard IPv4
forwarding and contains
routes learned via IGPs (OSPF, IS-IS) or static routing. inet.1 is utilized for
multicast forwarding
(MBGP), and inet.2 is typically used for Multicast Source Discovery Protocol (MSDP)
or RPF checks in
multicast environments. By isolating LSP egress points in inet.3, Junos prevents
MPLS-specific paths
from interfering with standard IGP path selection unless the administrator
explicitly chooses to
merge them (e.g., using the traffic-engineering bgp-igp command). Therefore, by
default, the ingress
router maintains its list of reachable LSP endpoints in inet.3.
Question: 3
What are two types of BGP messages exchanged while in the Established state?
(Choose two.)
A. open
B. request
C. update
D. notification
Answer: C, D
Explanation:
In the Border Gateway Protocol (BGP) finite state machine (FSM), the Established
state is the final
and functional stage of a BGP peering session. According to Juniper Networks
technical
documentation, once a session reaches this state, the two peers have
successfully exchanged Open
messages and agreed upon session parameters (such as AS numbers, hold timers,
and BGP
identifiers). Only after the session is -Established- can the routers begin the
actual exchange of
network layer reachability information (NLRI).
The most frequent message type exchanged in the Established state is the UPDATE
message. These
messages are the heart of BGP operations; they are used to advertise new
feasible routes to a peer
or to withdraw routes that are no longer reachable. An UPDATE message contains
path attributes
(like AS-Path, Next-Hop, and Local Preference) and the associated prefixes. In a
stable network,
UPDATE messages are only sent when there is a change in the topology, adhering
to BGP’s
incremental update philosophy.
The second message type that can be exchanged in this state is the NOTIFICATION
message. While
ideally, a session stays established, any detected error—such as a hold timer
expiration, a malformed
update, or a manual -clear- command—will trigger the transmission of a
NOTIFICATION message.
This message informs the peer of the specific error code and immediately causes
the BGP session to
transition back to the Idle state, tearing down the TCP connection.
It is important to note that OPEN messages (Option A) are only used during the
session initialization
phase to transition from the OpenConfirm state to Established. REQUEST (Option
B) is not a valid BGP
message type defined in the standard (RFC 4271); the closest equivalent in
functionality would be a
Route-Refresh message, which is a separate extension. Therefore, in the context
of standard BGP
operations within the Established state, Updates and Notifications are the
correct answers.
Question: 4
What is the default route preference for an aggregate route?
A. 180
B. 150
C. 130
D. 5
Answer: C
Explanation:
In the Junos OS architecture, route preference (often referred to as
administrative distance in other
vendor platforms) is the primary metric used by the Routing Engine to select the
-best- path when
multiple protocols provide a route to the same destination. Each routing
protocol and route type is
assigned a default numeric value; the lower the value, the more preferred the
route.
According to Juniper Networks technical documentation, an aggregate route is
assigned a default
preference of 130. Aggregate routes are a form of static-like route used to
group specific routes into a
single, broader prefix to reduce the size of routing tables and limit the scope
of routing updates. They
are -protocol-independent- because they are not learned from a dynamic neighbor
but are manually
defined by the administrator.
To understand where 130 fits in the hierarchy, it is helpful to compare it with
other common Junos preferences:
Directly connected interfaces: 0
Static routes: 5
OSPF Internal: 10
IS-IS Level 1/2: 15/18
Aggregate routes: 130
OSPF AS External: 150
BGP (Internal and External): 170
Generated routes: 150
By setting the aggregate route preference to 130, Junos ensures that specific
routes learned via IGPs
(like OSPF or IS-IS) are preferred over the aggregate. This is essential because
an aggregate route is
often used as a -catch-all- or a discard route when more specific path
information is missing. If the
aggregate had a lower preference (like 5), it might override dynamic routing
information, leading to suboptimal routing or black-holed traffic.
Question: 5
What information is determined by using the AS path attribute included in the
BGP update message?
(Choose two.)
A. the origin of a route from IGP or EGP
B. the presence of a routing loop
C. the shortest AS path to reach a prefix
D. the total number of next-hop devices to reach a prefix
Answer: B, C
Explanation:
The AS_PATH attribute is a -well-known mandatory- attribute in BGP, meaning it
must be present in
every BGP Update message exchanged between External BGP (eBGP) peers. It records
the sequence
of Autonomous System numbers that a route has traversed. Per Juniper Networks
Service Provider
documentation, this attribute serves two fundamental purposes:
1. Loop Prevention (Option B):
This is the most critical function of the AS_PATH. When a BGP router receives an
update from an
eBGP peer, it scans the AS_PATH attribute for its own AS number. If the router
finds its local AS
number already listed in the path, it concludes that the route has already
passed through its network
and has -looped- back. To prevent an infinite routing loop, the router will
immediately discard the
update. This mechanism is the cornerstone of BGP's stability as a path-vector
protocol.
2. Path Selection / Shortest Path Determination (Option C):
BGP uses a complex -tie-breaking- algorithm to select the best path among
multiple candidates. One
of the highest-ranking criteria in this algorithm (after Weight, Local
Preference, and AS_PATH length)
is the length of the AS_PATH. A shorter AS_PATH (fewer AS numbers listed) is
generally preferred
over a longer one, as it typically represents a more direct path through the
internet hierarchy. Why other options are incorrect:
Student Testimonials – Certkingdom JN0-364
Daniel M. - Canada
"The JN0-364 practice material helped me organize my preparation around OSPF,
IS-IS and BGP.”
Sofia R. - Spain
"I found the practice questions useful for reviewing MPLS and Junos routing
concepts before my exam.”
Ahmed K. - United Arab Emirates
"The exam preparation resources helped me identify the topics where I needed
more hands-on practice.”
Liam B. - Ireland
"A useful way to review JNCIS-SP concepts and become familiar with
multiple-choice exam scenarios.”
Priya S. - India
"The routing and MPLS practice material helped me revise difficult concepts more
efficiently.”
Lucas M. - Brazil
"I appreciated the coverage of BGP, OSPF and service provider networking
topics.”
Emily T. - Australia
"The practice approach helped me find weaknesses before scheduling my JN0-364
exam.”
Michael O. - Nigeria
"Helpful preparation material for reviewing Junos technologies and routing
protocols.”
Hana K. - South Korea
"The questions encouraged me to study the official objectives in more detail.”
George P. - Greece
"I used the practice material alongside hands-on Junos labs, and the combination
was very useful.”
Fatima A. - Morocco
"The structured topic coverage made it easier to plan my JNCIS-SP study
schedule.”
Ethan W. - New Zealand
"A helpful revision resource for MPLS, IPv6, BGP and troubleshooting concepts.”
Valentina C. - Chile
"The practice questions helped me become more comfortable with exam-style
networking questions.”
Yusuf H. - Turkey
"I found the routing protocol coverage particularly useful while preparing for
JN0-364.”
Anna L. - Poland
"Good for reviewing important JNCIS-SP concepts before the exam and identifying
areas for further study.”
1. What is the JN0-364 exam?
JN0-364 is the exam associated with the Service Provider Routing and Switching
Specialist certification path and validates knowledge of Junos-based service
provider routing and switching technologies.
2. How many questions are on the JN0-364 exam?
The current Juniper exam overview lists 65 multiple-choice questions.
3. How long is the JN0-364 exam?
The listed exam duration is 90 minutes.
4. What certification is associated with JN0-364?
JN0-364 is associated with the JNCIS-SP Service Provider Routing and Switching
Specialist certification.
5. Is JNCIA-Junos required before taking JN0-364?
Juniper lists JNCIA-Junos as the prerequisite certification for the current
JNCIS-SP exam.
6. Does JN0-364 include OSPF?
Yes. OSPF concepts, configuration, monitoring, routing policies, and
troubleshooting are included in the published objectives.
7. Is IS-IS included in JN0-364?
Yes. Candidates should understand IS-IS concepts, PDUs, TLVs, adjacencies,
levels, areas, DIS operation, metrics, and troubleshooting.
8. Does the exam cover BGP?
Yes. BGP operation, messages, attributes, route selection, IBGP, EBGP, peers,
groups, and routing policies are included.
9. How important is MPLS for JN0-364?
MPLS is a major published exam objective, including forwarding, labels, RSVP,
LDP, and segment routing concepts.
10. Does JN0-364 include IPv6?
Yes. The objectives include IPv6 static routing, OSPFv3, IS-IS, BGP, tunneling,
and troubleshooting.
11. Are VLANs and Layer 2 bridging included?
Yes. Candidates should understand Layer 2 bridging, VLANs, port modes, tagging,
IRB, virtual switches, and provider bridging concepts.
12. Does JN0-364 include GRE tunnels?
Yes. Generic Routing Encapsulation and IP tunneling concepts are included in the
official objectives.
13. What high-availability technologies should I study?
Important topics include LAG, Graceful Restart, GRES, NSB, NSR, BFD, and VRRP.
14. What is the best way to prepare for JN0-364?
A strong approach is to study the official exam objectives, complete Junos
hands-on labs, review routing protocol theory, practice troubleshooting, and use
legitimate practice questions to identify knowledge gaps. Juniper recommends
training such as Junos Intermediate Routing, Junos Service Provider Switching,
and Junos MPLS Fundamentals.
15. Is JN0-364 suitable for service provider network engineers?
Yes. The certification is intended for networking professionals developing
intermediate knowledge of service provider routing and switching implementations
using Junos.