All Juniper JN0-364 certification exam dumps, study guide, training courses are Prepared by industry experts. PrepAway's ETE files povide the JN0-364 Service Provider Routing and Switching, Specialist (JNCIS-SP) practice test questions and answers & exam dumps, study guide and training courses help you study and pass hassle-free!

JN0-364 JNCIS-SP: Routing, MPLS, IPv6, and High Availability

JN0-364 is the current exam for Juniper Networks Certified Specialist, Service Provider Routing and Switching (JNCIS-SP). Juniper introduced it on February 2, 2026 after retiring JN0-363. The current exam is delivered through Pearson VUE, contains 65 multiple-choice questions in 90 minutes, requires JNCIA-Junos, and references Junos OS 25.2.

The blueprint covers protocol-independent routing, OSPF, IS-IS, BGP, Layer 2 bridging and VLANs, spanning-tree protocols, MPLS, IPv6, GRE tunnels, and high availability. That breadth reflects the reality of service-provider operations: a customer-facing service may depend simultaneously on an IP underlay, an IGP, BGP policy, label distribution, Layer 2 transport, and resiliency mechanisms.

Preparation is therefore strongest when candidates build layered mental models rather than study each acronym independently. The goal is to know what state each protocol creates, where that state is visible in Junos, how forwarding depends on it, and which evidence can isolate the first failed layer when traffic does not follow the intended service path.

JNCIA-Junos is the operating foundation for JN0-364

Juniper lists JNCIA-Junos as the prerequisite, and that makes practical sense. JN0-364 assumes the candidate can already navigate the CLI, interpret configuration hierarchy, commit changes safely, read routing and interface state, and understand basic IPv4/IPv6 routing. The JNCIA-Junos material should feel like operational vocabulary before specialist study begins.

If those skills are rusty, refresh them through the current JN0-106 scope and practical labs. Specialist preparation becomes inefficient when every routing-protocol exercise is interrupted by uncertainty about configuration groups, interface families, route tables, or operational commands. The more automatic Junos fundamentals become, the more attention can be spent on provider-specific behavior.

Protocol-independent routing explains the shape of the routing tables

Static, aggregate, and generated routes are not merely beginner topics. They can define reachability, summarize information, create controlled advertisements, or provide fallback paths. Routing instances and RIB groups determine where routes live and how information is shared between tables. Load balancing and filter-based forwarding can change traffic behavior even when the normal routing table appears correct.

Use a prefix as the unit of investigation. Identify every source that could create it, compare route preference, determine which candidate is active, and inspect any policy that alters import, export, or forwarding. If the route exists in the control plane but traffic still follows an unexpected path, move to the forwarding table and filters. This staged approach prevents dynamic protocols from becoming the default suspect for every routing symptom.

OSPF and IS-IS must be understood beyond neighbor-up status

OSPF objectives include the link-state database, packet types, router IDs, adjacencies, DR/BDR roles, area types, LSAs, configuration, policy, and troubleshooting. IS-IS objectives include its database, PDUs, TLVs, levels, areas, the DIS, metrics, adjacency behavior, policy, and operational verification. Both protocols create a topology view, but their terminology and hierarchy differ.

Study each protocol as a sequence: interface eligibility, neighbor discovery, adjacency formation, database exchange, shortest-path calculation, route installation, and policy interaction. Then break one stage at a time. An adjacency that forms but produces no desired route is a different problem from an interface that never discovers a neighbor. This decomposition is central to real service-provider troubleshooting.

BGP combines reachability, path attributes, and policy at scale

JN0-364 expects knowledge of BGP operation, messages, attributes, best-path selection, IBGP and EBGP interaction, groups, peers, routing policy, and troubleshooting. The safest way to learn BGP is to separate session state from route state. A peer can be reachable without a BGP session, and a session can be established without the desired prefix becoming active.

For any missing route, verify transport reachability to the peer, session state, received prefixes, import policy, attributes, next-hop resolution, active route selection, and export policy. This workflow turns BGP from a large memorization problem into a set of observable checkpoints. It also reinforces why routing policy is one of the most important transferable Junos skills.

Service-provider switching adds provider bridging and multiple spanning-tree variants

The Layer 2 portion covers service-provider switching platforms, bridging terminology and frame processing, virtual switches, Q-in-Q provider bridging, VLAN port modes and tagging, and Integrated Routing and Bridging. These features support service separation over shared infrastructure. Candidates should be able to follow how an incoming frame is classified, tagged, switched, or routed as it crosses the service edge.

STP, RSTP, MSTP, and VSTP add loop prevention across different designs. Learn port roles and states, BPDU behavior, convergence, and protections such as BPDU, loop, and root protection. The key is not to memorize every state in isolation, but to predict the forwarding topology and explain how it changes when a link, bridge, or control message disappears.

Segment routing adds another reason to separate intent from forwarding evidence. The network can calculate a path using segment identifiers while still relying on the IGP and label-forwarding infrastructure underneath. Study how the selected segment list relates to topology and how the data plane represents the result. If traffic deviates from the expected route, verify the advertised information and the installed forwarding state before assuming the tunnel itself is misconfigured.

MPLS requires you to think in both IP routes and label-switched paths

MPLS is a major differentiator for the service-provider specialist track. The current blueprint includes terminology, label headers, packet flow, the label information base, interaction with routing tables, RSVP, LDP, and segment routing with MPLS. Candidates should visualize how a packet receives a label, how that label is swapped or removed, and which control-plane mechanism created the forwarding state.

Practice with RSVP-signaled and LDP-signaled LSPs, then compare the operational information with segment-routing behavior. When an LSP fails, do not immediately alter MPLS configuration. Verify the IGP underlay, reachability between label-switching routers, signaling state, label bindings, and forwarding entries. MPLS depends on the health of layers below it, and troubleshooting should follow that dependency chain.

IPv6 and GRE extend the service-provider transport model

JN0-364 includes IPv6 static routing and dynamic routing with OSPFv3, IS-IS, and BGP, along with IPv6-over-IPv4 tunneling concepts. The most productive preparation treats IPv6 as an operational address family, not a theoretical side topic. Configure addressing, form adjacencies, verify routes, and trace traffic so the protocol differences become visible in practice.

GRE provides a general tunneling mechanism for carrying traffic across an IP underlay. Always prove the underlay reachability between tunnel endpoints first, then verify tunnel configuration, routes using the tunnel, and return traffic. This ordering avoids wasting time on overlay configuration when the actual failure is ordinary IP reachability beneath it.

High availability should be mapped to the exact state being protected

The blueprint includes LAGs, graceful restart, GRES, NSB, NSR, BFD, and VRRP. Each protects a different failure domain or reduces disruption in a different way. LAGs protect link capacity and connectivity; BFD improves failure detection; VRRP protects gateway availability; graceful restart and Routing Engine continuity mechanisms address control-plane transitions and forwarding preservation.

Build failure tests instead of only reading descriptions. Remove a member link, interrupt a routing adjacency, fail a redundant gateway role, or simulate a control-plane switchover in a safe lab. Record what state persists, what reconverges, and what user traffic experiences. This turns high availability from a vocabulary exercise into an understanding of service continuity.

Cross-domain labs are especially valuable for JN0-364 because provider services rarely fail inside a single protocol boundary. Build a topology in which an IGP supplies reachability for BGP and MPLS, then introduce a single interface or policy fault. Trace the symptom through neighbor state, route selection, label signaling, and the final forwarding path. The exercise teaches which dependency to verify first and prevents the habit of making simultaneous changes to unrelated protocols.

IPv6 should be included in those integrated labs rather than saved for a separate review day. Form at least one IPv6 routing adjacency, advertise a prefix through BGP, and verify the resulting forwarding path. Then compare the operational commands and failure clues with the IPv4 case. Similar protocol names can conceal differences in address families and configuration, and direct comparison makes those distinctions easier to remember.

The current objectives repeatedly ask candidates to configure, monitor, or troubleshoot technologies. A study plan should mirror that wording. For each domain, build a minimal working configuration, identify the operational commands that prove success, capture normal output, and then create a controlled failure. The ability to distinguish normal from abnormal state is more important than the number of commands memorized.

Keep a fault notebook organized by symptoms and evidence. Record why an OSPF neighbor failed, how an IS-IS level mismatch appears, which BGP output revealed policy rejection, what an MPLS signaling problem looked like, and how BFD changed convergence. This creates reusable diagnostic patterns that remain valuable long after the exam.

Before scheduling the exam, perform at least one end-to-end review in which each blueprint domain is tied to configuration, verification, and a failure case. The goal is not equal lab time for every topic; it is to eliminate domains where the candidate can define a feature but cannot recognize its operational state. That distinction is what turns broad syllabus coverage into specialist-level readiness.

JN0-364 is the current specialist bridge to deeper service-provider work

Candidates using older JN0-363 books or labs can reuse much of the conceptual material, but the current JN0-364 blueprint should control the final preparation plan. Pay special attention to changes in referenced software and newer emphasis such as segment routing with MPLS. Historical content should support the current objectives, not replace them.

After JNCIS-SP, JN0-664 represents the professional service-provider level in this progression. The broader Juniper certifications family provides context for adjacent tracks, but JN0-364 preparation should remain focused: master routing state, understand provider switching and labels, and practice isolating failures across the layered service path.

Juniper JN0-364 practice test questions and answers, training course, study guide are uploaded in ETE Files format by real users. Study and Pass JN0-364 Service Provider Routing and Switching, Specialist (JNCIS-SP) certification exam dumps & practice test questions and answers are to help students.