- Decoding the Acronym Piece by Piece
- Which JNCIS-SP We Mean (and Which We Don't)
- Where the Specialist Level Sits in the Juniper Track
- What the Credential Actually Proves
- The Ten Objective Headings Behind the Name
- Exam Mechanics: JN0-364 at a Glance
- Who Pays Attention to This Credential
- Service Provider vs. Enterprise: Why the Letters Matter
- Turning the Meaning Into a Study Sequence
- Frequently Asked Questions
- JNCIS-SP is Juniper Networks Certified Specialist, Service Provider Routing and Switching, tested through exam JN0-364 on Junos OS 25.2.
- "JNCIS" is the specialist level; "SP" is the service provider track, distinct from the enterprise (ENT) track.
- An active JNCIA-Junos is the stated prerequisite; the exam is 65 multiple-choice questions in 90 minutes.
- Ten official objective headings define the scope, from protocol-independent routing through MPLS, IPv6, tunnels and high availability.
Decoding the Acronym Piece by Piece
Search for "JNCIS-SP" and you will find the letters used casually, as though everyone already knows what they expand to. Let's slow down and take them apart, because each segment tells you something concrete about the exam you would be sitting.
- JN stands for Juniper Networks, the vendor that issues the credential. Current certification pages carry HPE Juniper Networking branding, but the credential name still reads Juniper Networks Certified Specialist.
- C means Certified, and the full title begins "Juniper Networks Certified Specialist."
- IS is the level marker: Specialist. In Juniper's ladder, the "IS" level sits above the associate tier and below the professional tier.
- SP names the track: Service Provider Routing and Switching.
Put together, the full official title is Juniper Networks Certified Specialist, Service Provider Routing and Switching (JNCIS-SP). If you want shorter explainers on the same question, we also cover what JNCIS-SP is and what JNCIS-SP stands for, but this article goes further by connecting the name to the actual exam content.
Which JNCIS-SP We Mean (and Which We Don't)
Acronyms get reused across the IT industry, and "JNCIS-SP" is no exception to the general hazard of look-alike credential names. On this site, the term refers exclusively to the Juniper Networks specialist credential described above. If you arrived here hoping to learn about a similarly abbreviated certificate from a different issuer, the exam details, fees and policies on this page will not apply to it.
Version drift is a related problem. Older Juniper material references exam codes such as JN0-360, JN0-362 and JN0-363, and some secondary resources still point to books published more than a decade ago. The current exam covered here is JN0-364 on Junos OS 25.2. Treat anything that does not name that exam code with healthy suspicion until you have compared it against the official objectives.
Where the Specialist Level Sits in the Juniper Track
The service provider track is a ladder, and the "S" in the middle of JNCIS tells you which rung you are on. The specialist level is aimed at networking professionals with beginner-to-intermediate Junos routing and switching knowledge. Before you can earn it, the credential overview states a prerequisite: an active JNCIA-Junos. No additional mandatory training hours, employment history or references are listed.
A few program rules from Juniper's general certification FAQs are worth knowing because they affect how people plan the sequence:
- Written exams may be taken in any order, but every prerequisite certification requirement must still be fulfilled; none is waived.
- Taking an exam before holding the prerequisite is not the same as being eligible to receive the credential.
- Earning a new certification, or recertifying one, also renews all active associate-level certifications.
For a closer look at eligibility, see our breakdown of JNCIS-SP requirements and prerequisites.
What the Credential Actually Proves
A specialist certification is a statement about knowledge, tested through a written examination. It is not a lab-based or practical demonstration. The JN0-364 objectives are written with two distinct verbs that appear again and again: candidates must identify concepts, operation or functionality, and they must demonstrate knowledge of configuration, monitoring or troubleshooting. Those are two different asks, and the exam treats them separately.
In practice, that means being able to recognize what an OSPF designated router does and also being able to reason about how you would configure, monitor or troubleshoot OSPF interfaces and neighbors on Junos. Candidates who study only definitions tend to struggle with the second half; candidates who only memorize commands tend to struggle with the first.
Key Takeaway
When you review any objective, ask two questions: "Can I explain how this works?" and "Can I reason through configuring, monitoring or troubleshooting it on Junos?" The exam objectives separate those skills, and so should your preparation.
The Ten Objective Headings Behind the Name
The "Routing and Switching" half of the title is spelled out in ten official objective headings. Percentage weights are not published for them, so no heading can honestly be called the "biggest" domain. What follows is a plain-language tour of what each one covers. For a deeper treatment, our complete guide to all 10 JNCIS-SP content areas goes domain by domain.
Domain 1: Protocol-Independent Routing
Concepts that apply regardless of routing protocol.
- Static, aggregate and generated routes
- Martian addresses
- Routing instances, including RIB and routing-table groups
- Load balancing and filter-based forwarding
Domain 2: Open Shortest Path First (OSPF)
Link-state routing in depth.
- Link-state database, packet types, router ID and adjacencies
- Designated and backup designated routers
- Area and router types, plus LSA packet types
- Configuration, monitoring and troubleshooting: interfaces, neighbors, routing-policy application and tools
Domain 3: Intermediate System to Intermediate System (IS-IS)
The other link-state protocol, long associated with service provider cores.
- Link-state database, PDUs and TLVs
- Adjacencies, levels and areas, the DIS and metrics
- Configuration, monitoring and troubleshooting for interfaces, adjacencies, policy and tools
Domain 4: Border Gateway Protocol (BGP)
Inter-domain routing fundamentals.
- Basic operation, message types and attributes
- Route and path selection
- IBGP and EBGP functionality and interaction
- Configuration of groups and peers, additional basic options and routing-policy application
Domain 5: Layer 2 Bridging or VLANs
Switching concepts on service provider platforms.
- Bridging elements, terminology and frame processing
- Virtual switches and provider bridging (Q-in-Q)
- Port modes, tagging and Integrated Routing and Bridging (IRB)
Domain 6: Spanning-Tree Protocols
Loop prevention across four variants.
- STP, RSTP, MSTP and VSTP
- Port roles and states, BPDUs, convergence and reconvergence
- Spanning-tree security, including BPDU, loop and root protection
Domain 7: Multiprotocol Label Switching (MPLS)
Label-based forwarding in the provider core.
- Terminology, packet header and end-to-end packet flow
- Labels, label information base, MPLS and routing tables
- RSVP, LDP and segment routing with MPLS
- Configuration, monitoring and troubleshooting for MPLS forwarding, LDP-signaled LSPs and shortest-path segment-routing LSPs
Domain 8: IPv6
IPv6 as it appears across the other routing topics.
- Static routes and dynamic routing with OSPFv3, IS-IS and BGP
- IPv6-over-IPv4 tunneling
- IPv6 configuration, monitoring and troubleshooting
Domain 9: Tunnels
IP tunneling concepts and GRE.
- Requirements, applications and considerations for IP tunnels
- GRE configuration, monitoring and troubleshooting
Domain 10: High Availability
Keeping a network forwarding through failures.
- LAGs, graceful restart (GR), graceful Routing Engine switchover (GRES)
- Nonstop bridging (NSB), nonstop active routing (NSR)
- BFD and VRRP
One note on source quality: the published MPLS configuration list includes an incomplete "RSVP-signaled" bullet. Rather than guess at what the official text intended to say, treat RSVP as an in-scope signaling protocol at the identification level and read the official objectives directly for the configuration wording.
Exam Mechanics: JN0-364 at a Glance
Knowing what the name stands for is only useful if you also know what you will face on test day. The principal logistics are summarized below.
| Item | JNCIS-SP (JN0-364) |
|---|---|
| Exam code and version | JN0-364, Junos OS 25.2 |
| Question count | 65 |
| Time allowed | 90 minutes |
| Format | English-language, written multiple choice |
| Delivery | Pearson VUE test center or OnVUE online, subject to local availability and technical checks |
| Published base fee | $300 plus applicable taxes |
| Prerequisite | Active JNCIA-Junos |
| Validity | Three years |
| Passing score | Statistically set for the exam and reported to the candidate; not a fixed published percentage |
Fees, scores and what is not published
The $300 figure is the published base examination fee; final checkout totals depend on region, taxes and any voucher you hold, and those were not verified here. Be careful not to confuse this fee with course charges. Our JNCIS-SP certification cost breakdown separates the exam fee from preparation spending.
The passing score is the other place where people go wrong. Juniper sets it statistically for the individual exam. A 70% figure you may have seen belongs to a separate practice-test or voucher-assessment page, not to the live exam. For the nuance, read our explainer on the JNCIS-SP passing score.
Retakes and renewal
After a first failure you may retry without a waiting period. After a second or later failure, you wait 14 calendar days, counted from the day after the failed attempt. After passing, you must wait at least 18 months before retaking the same exam. To renew, complete an eligible current exam or a specified qualifying course before the three-year expiry, or earn a higher-level credential in the same track. If it lapses, you restart the track. Timing details are covered in our guide to JNCIS-SP exam dates and scheduling.
Who Pays Attention to This Credential
The "SP" in JNCIS-SP points to the kind of employer for whom the content is most directly relevant: organizations that build and run carrier-style networks. The objective list reads like a job description for that environment: IS-IS and OSPF in the core, BGP at the edge, MPLS carrying traffic between sites, Q-in-Q for customer separation, and high-availability features that keep forwarding alive during failover.
Typical roles where this knowledge is relevant include network engineers and operations staff at telecommunications carriers, internet service providers, cable and fiber operators, managed network service companies and large data network operators that use Junos-based routers and switches. Hiring teams in those settings generally care more about whether you can reason about protocols and troubleshoot a Junos device than about the badge itself, but a specialist credential on top of an active JNCIA-Junos is a recognized way to signal that groundwork. For a look at job-market angles, see our overview of JNCIS-SP jobs.
On compensation, be skeptical of any source quoting a precise JNCIS-SP salary or a guaranteed uplift. Job-board aggregates tend to lump all JNCIS-level roles together, so they cannot isolate this credential. Our salary guide and ROI analysis walk through how to evaluate the value without leaning on made-up numbers.
Service Provider vs. Enterprise: Why the Letters Matter
The most common point of confusion once people understand the acronym is the difference between SP and ENT. Both are specialist-level Junos credentials, and both build on foundational Junos knowledge, which is why forum posts frequently ask which to pursue. The letters signal emphasis rather than a wall between them.
| Consideration | JNCIS-SP | JNCIS-ENT |
|---|---|---|
| Track | Service Provider Routing and Switching | Enterprise Routing and Switching |
| Content flavor in the objectives | Includes MPLS (with LDP, RSVP and segment routing), IS-IS, provider bridging/Q-in-Q and tunnels | Aimed at enterprise-style environments; consult its own official objectives |
| Best fit | Carrier, ISP and managed-service network roles | Corporate campus and branch roles |
Rather than relying on a summary, compare the two official objective lists against the work you actually do or want to do. If your daily reality involves label-switched paths and link-state cores, the SP objectives will feel familiar. If it involves campus switching and enterprise WAN, review the enterprise track instead.
Turning the Meaning Into a Study Sequence
Because the exam's ten headings have no published weights, a sensible plan builds from foundations upward rather than chasing a presumed "heavy" domain. The sequence below groups topics by dependency, so each week supports the next. It is a framework, not an official schedule.
Routing foundations
- Domain 1: static, aggregate and generated routes, routing instances, load balancing, filter-based forwarding
- Refresh JNCIA-Junos material you will lean on throughout
Link-state protocols
- Domain 2: OSPF databases, adjacencies, DR/BDR, area types and LSAs
- Domain 3: IS-IS PDUs, TLVs, levels and the DIS, compared directly with OSPF
Inter-domain routing
- Domain 4: BGP messages, attributes, path selection and IBGP versus EBGP
- Domain 8: carry the same protocols into IPv6 with OSPFv3, IS-IS and BGP
Layer 2 and the MPLS core
- Domains 5 and 6: bridging, VLANs, IRB, Q-in-Q and the four spanning-tree variants
- Domain 7: label operation, LDP, RSVP and segment routing, building on your IGP knowledge
Resilience and consolidation
- Domains 9 and 10: GRE tunnels, LAGs, GR/GRES/NSB/NSR, BFD and VRRP
- Mixed review of identification and configuration/monitoring/troubleshooting questions
This ordering puts MPLS after the IGPs and BGP because label distribution relies on an underlying routing foundation. For a fuller plan with resources, read the JNCIS-SP study guide, keep the one-page cheat sheet handy for revision, and consult the JNCIS-SP training overview for course options. When you are ready to test yourself, our JNCIS-SP practice tests let you check recall against independently written questions. Those are knowledge-preparation tools, not recalled exam items or an official mock.
Key Takeaway
Preparing for JN0-364 means mastering both halves of each objective: identify the concept, then reason about configuration, monitoring and troubleshooting on Junos. A name decoded is a syllabus understood.
If you are weighing whether the effort is manageable, our write-ups on how hard the exam is and the state of pass-rate data explain what can and cannot be said honestly. Keep in mind that the current pass rate is not published, so be wary of anyone claiming a figure. You can also revisit the main practice site to explore question formats across all ten domains.
Frequently Asked Questions
It stands for Juniper Networks Certified Specialist, Service Provider Routing and Switching. The "IS" marks the specialist level and "SP" marks the service provider track. It is earned by passing exam JN0-364, which is based on Junos OS 25.2.
No. They are separate specialist-level credentials in different tracks: Service Provider Routing and Switching versus Enterprise Routing and Switching. Their objectives overlap in some foundational areas, but SP includes topics such as MPLS, IS-IS and provider bridging. Compare the official objective lists for each before choosing.
Yes. The credential overview lists an active JNCIA-Junos as the prerequisite. No additional mandatory training hours, employment hours or references are stated, and recommended courses are optional rather than required.
The JN0-364 exam has 65 multiple-choice questions and a 90-minute time limit. It is delivered in English through Pearson VUE, either at a test center or via OnVUE online delivery, subject to local availability and technical checks.
It is valid for three years. You can renew by completing an eligible current exam or specified qualifying course before expiry, or by earning a higher-level credential in the same track. If it expires, you must restart the track.