JNCIA-Junos: Juniper Networks Certified Associate, Junos
The thing most candidates miss about JNCIA-Junos is not a domain gap. It is the commit model. Nearly everyone who comes from a Cisco background treats Junos configuration changes as immediate. They practice in a lab, type a config command, and wonder why the interface did not come up the way they expected. In Junos, changes enter a candidate configuration first. Nothing takes effect until you run commit. If you commit confirmed without following it up with a second commit, the device rolls back after a timer expires. Understanding this distinction, concretely and not just as a vocabulary term, separates candidates who read the right answer from candidates who understand why the other three options are wrong.
Junos also separates control plane from data plane at the hardware level. The routing engine handles protocol processing, policy evaluation, and management. The packet forwarding engine handles the actual forwarding of traffic using a copy of the forwarding table that the routing engine installed. This architecture shows up in multiple question types, not just the "what does the RE do" recall questions. It matters for understanding what continues to work when the RE is busy or temporarily unavailable, and that nuance is tested.
Exam at a glance
| Detail | Value |
|---|---|
| Provider | Juniper Networks |
| Exam code | JN0-105 |
| Full name | Juniper Networks Certified Associate, Junos (JNCIA-Junos) |
| Duration | 90 minutes |
| Question count | 65 questions |
| Question format | Multiple choice, multiple select |
| Passing score | ~70% (Juniper does not publish the exact cutoff) |
| Exam fee | ~$200 USD |
| Validity | 3 years |
| Delivery | Pearson VUE (in-person or online proctored) |
| Prerequisites | None |
| Retake policy | 30-day wait after a failed attempt |
What's tested
Networking Fundamentals. The exam opens with OSI model and TCP/IP fundamentals: how traffic moves between hosts, how routing decisions are made, and the basics of switching behavior. This section is not a heavy point of failure for candidates with any networking background, but the questions do assume you can reason through a scenario, not just name the layers. Spanning Tree Protocol and how broadcast domains differ from collision domains are tested here as well.
Junos OS Fundamentals. This is the heart of the exam. The routing engine versus packet forwarding engine separation is tested in multiple forms. You need to know which functions live on each plane, what happens to forwarding when the RE is restarting (the PFE continues forwarding using its existing table, even if protocol adjacencies drop), and how the Junos modular architecture differs from traditional monolithic OS designs. CLI hierarchy and navigation also fall into this section: understanding the difference between operational mode and configuration mode, how to move between hierarchy levels, and how Junos uses a structured configuration tree rather than a flat running-config.
User Interfaces. JN0-105 tests both the CLI and the J-Web graphical interface. CLI questions dominate in practice. You need to know how to commit, roll back, compare configurations, and use show commands to verify operational state. J-Web questions tend to be high-level, focused on what it is used for rather than specific menu paths.
Junos Routing Fundamentals. The routing table in Junos is separate from the forwarding table. The routing table (inet.0 for IPv4 unicast by default) holds all routes learned from all sources. The forwarding table holds the active routes that the PFE actually uses for forwarding decisions. Junos selects the active route using preference values (its term for administrative distance), then installs that route into the forwarding table. Static routes, OSPF, BGP, and direct routes each have a default preference value, and the exam tests whether you know them or can reason about which route wins when multiple sources learn the same prefix.
Junos Switching Fundamentals. VLAN configuration on Junos switches, STP behavior, port security mechanisms, and Integrated Routing and Bridging (IRB) interfaces. IRB is the Junos equivalent of a switched virtual interface. It provides a Layer 3 gateway for a VLAN at the device level. Candidates who have only worked with Cisco SVIs sometimes stumble on IRB syntax and behavior in scenario questions. STP port states and how Junos implements rapid STP are also tested.
Junos Security Fundamentals. Juniper's security model is zone-based. Traffic between zones is denied by default unless a security policy explicitly permits it. Traffic within the same zone uses intra-zone policy, which is permit-all by default. Screen options provide stateless protection against common attack types such as SYN floods and port scans, operating before the zone policy is evaluated. NAT basics, including source NAT and destination NAT, are covered at an introductory level. Candidates should know the difference between a security zone and a routing instance before sitting the exam.
Common exam traps
Routing engine failure and packet forwarding continuity. When the routing engine fails or is restarting, protocol adjacencies (OSPF, BGP) drop because they are maintained by the RE. However, the PFE continues forwarding traffic using the forwarding table that was installed before the RE went offline. Many candidates assume traffic stops entirely when the RE is unavailable. It does not. The forwarding table persists on the PFE until it is updated or the device reboots. This is explicitly tested, and getting it wrong costs points in the Junos OS Fundamentals section.
Commit confirmed timer behavior. commit confirmed starts a rollback timer (default 10 minutes). If you do not run a second commit before the timer expires, Junos rolls back to the previous confirmed configuration automatically. The intended use is safe remote commits: if your change breaks connectivity, the device rolls back on its own and you can reconnect. What trips candidates up is the assumption that a second commit confirmed resets the timer. It does. What they miss is that only a plain commit (without the confirmed keyword) actually finalizes the change and cancels the rollback. This distinction appears in scenario questions where you need to identify what happens next given a specific sequence of commands.
Junos preference values are not the same as Cisco administrative distance. Both use lower-is-better logic, but the specific values differ. In Junos, directly connected interfaces have preference 0, static routes default to 5, OSPF internal routes are 10, BGP external routes are 170, and OSPF external (Type 2) routes are 150. Cisco uses 110 for OSPF internal. Candidates who have studied Cisco and now sit JNCIA-Junos routinely write down 110 for OSPF and get route preference questions wrong. The Junos values are worth memorizing as a separate table rather than trying to map them to Cisco equivalents.
show route versus show route table inet.0. Running show route without arguments displays all routing tables, including inet.0, inet6.0, mpls.0, and others. Running show route table inet.0 scopes the output to the IPv4 unicast routing table. In a lab with minimal configuration these commands produce similar output, so candidates practice them interchangeably. On the exam, a question will describe a device with multiple routing tables and ask what a specific command shows. Knowing the scope of each command matters.
deactivate does not delete configuration. A trap from TechExams.net discussions worth knowing: deactivate marks a configuration stanza as inactive, which means it is ignored during commit but remains visible in the configuration with an inactive: tag. delete removes the configuration entirely. Candidates who have only used Cisco IOS treat these differently but often assume Junos has no equivalent to deactivate. It does, and the distinction appears in questions about how to temporarily disable a policy or interface configuration without losing it.
How ARIA prepares you for JNCIA-Junos
My evaluation maps your starting point across each of the six JN0-105 domain areas before generating your roadmap. The pattern I see most often is that candidates with Cisco CCNA-level experience arrive strong on networking fundamentals but need significant work on the Junos-specific sections: the commit model, routing and forwarding table separation, preference values, and the zone-based security model. The evaluation catches this early and weights your roadmap accordingly.
For someone coming from a Cisco background with active hands-on experience, plan for 4 to 6 weeks. The Junos syntax and architecture take real practice time, but the networking fundamentals do not need to be re-learned from scratch. For someone newer to networking who is starting with JNCIA-Junos as their first vendor cert, plan for 10 to 14 weeks. The foundational networking section of the exam is smaller by weight, but you cannot skip it, and the Junos-specific material builds on it.
The roadmap I generate for JNCIA-Junos typically runs three phases: networking and OS fundamentals, routing and switching with hands-on Junos CLI practice, and security plus integration scenarios. Milestone validations include live Junos config scenarios, not just recall questions, because that is where the commit model and routing table distinctions become real.
Pass guarantee for JNCIA-Junos
JNCIA-Junos qualifies for the ClaudeLab pass guarantee. Full conditions here.
Related certifications
JNCIS-ENT (Juniper Networks Certified Specialist Enterprise Routing and Switching) is the natural next step after JNCIA-Junos. It builds directly on the foundational concepts tested in JN0-105 and goes deeper into OSPF, BGP, spanning tree variants, and advanced switching. If you are building a Juniper-focused career track, JNCIS-ENT is the immediate follow-on.
CCNA (200-301) is the Cisco equivalent and the most common comparison point for JNCIA-Junos. The two exams test overlapping networking knowledge but different vendor implementations. Candidates who pass one often pursue the other to demonstrate platform breadth. If you have CCNA already, JNCIA-Junos is achievable faster than starting from zero.
CCNP is relevant for candidates who are deciding whether to go deeper into Cisco or pivot toward Juniper. Some enterprise environments run both vendors, and holding JNCIA-Junos alongside a CCNP concentration makes a clear case for platform-agnostic networking knowledge.
Network+ is worth considering if your foundational networking knowledge is thin before starting JNCIA-Junos. The JN0-105 exam assumes comfort with OSI, TCP/IP, routing concepts, and basic switching. If those areas feel uncertain, spending four to six weeks on Network+ first produces a stronger foundation and a faster JNCIA-Junos prep cycle afterward.
Start your JNCIA-Junos roadmap
Start your JNCIA-Junos roadmap with ARIA → claudelab.me
The JN0-105 exam has no prerequisites, which makes it accessible, but also means the bar for "I'm ready" is easy to underestimate. I run a structured evaluation before building your plan so you are not guessing at your readiness. The Junos commit model and routing architecture questions have precisely written wrong answers that target common assumptions. You need deliberate practice against those specific traps, not just more reading time.