- The Five Domains at a Glance
- Version, Format and Registration Facts
- Domain 1: Platform Automation Overview
- Domain 2: gRPC
- Domain 3: Ansible
- Domain 4: Junos Automation Scripts
- Domain 5: YANG
- Sequencing the Domains in Your Prep
- Where the Specialist Credential Fits Professionally
- Renewal and Credential Lifecycle
- Frequently Asked Questions
- JN0-423 covers five published objectives: Platform Automation Overview, gRPC, Ansible, Junos Automation Scripts, and YANG, built on Junos OS 24.4.
- The exam is 65 multiple-choice questions in 90 minutes, delivered in English, with a USD 300 standard specialist voucher.
- Juniper publishes no domain weights, so do not assume equal weighting or a single heaviest domain.
- JNCIA-DevOps is the prerequisite, but associate preparation does not replace the specialist objectives.
The Five Domains at a Glance
The Juniper Networks Certified Specialist, Automation and DevOps (JNCIS-DevOps) exam is organized around five high-level objectives published on Juniper's certification overview page. Those headings are the official scope: Platform Automation Overview, gRPC, Ansible, Junos Automation Scripts, and YANG. Python and PyEZ also appear in the overview as supporting skills that run through the automation material.
One point deserves emphasis early: Juniper does not publish percentage weights for these domains. Five headings do not mean five equal slices, and nothing in the official material identifies a "highest-weighted" domain. Any guide that claims precise percentages for JN0-423 is guessing. If you want a broader orientation before diving into domain detail, the overview of what the JNCIS-DevOps certification is covers the credential's place in the Juniper track.
| Domain | Core subjects named in the official scope |
|---|---|
| Platform Automation Overview | MGD management-process automation, Terraform, Juniper Extension Toolkit (JET) and JSD service-process automation |
| gRPC | gRPC/gNMI for automation and telemetry, protocol buffers, the gRPC protocol, OpenConfig, sensor paths, gNMIc, TIG stack |
| Ansible | Supported files, playbooks, Vault, JSNAPy, Jinja2 templates |
| Junos Automation Scripts | Concepts, benefits and operation of commit, op, event and SNMP scripts |
| YANG | YANG implementation, OpenConfig configuration models, syntax and data types |
Version, Format and Registration Facts
Before studying any domain, confirm you are working from the right exam. The current exam is JN0-423, written against Junos OS 24.4. It launched on October 6, 2025, replacing JN0-422, which retired on October 5, 2025. That matters because cached outlines, older videos and forum posts often reference the previous code or Junos 21.3 behavior. Treat those materials as background at best, and never blend their scope into your JN0-423 plan.
- Format: 65 multiple-choice questions in 90 minutes, in English.
- Fee: the standard specialist-exam voucher is USD 300. No member versus nonmember price schedule was identified, so budget around the single figure. The JNCIS-DevOps certification cost breakdown goes through the surrounding expenses.
- Delivery: Pearson VUE provides test-center and OnVUE (remote) delivery. Current issuer instructions direct candidates to schedule, manage and launch written exams through Alpine CertMetrics using their hpe.com account.
- Program branding: the issuer renamed its certification program the HPE Networking Certification Program on September 15, 2026. Your credential identity is unchanged, but you will see the new name in portals.
- Scoring: the numerical passing score is not published; it appears on your score report, and initial passing results are provisional. See the JNCIS-DevOps passing score guide for how to interpret this.
Domain 1: Platform Automation Overview
This domain frames how automation reaches a Junos device. Rather than a single tool, it asks you to understand the different automation surfaces and which one fits a given task. The published subjects are MGD management-process automation, Terraform, and Juniper Extension Toolkit (JET) with JSD service-process automation.
Management process versus service process
A recurring distinction is where automation interacts with the platform. MGD is the Junos management process, the daemon behind the CLI, NETCONF and configuration management. JSD is the service daemon through which JET exposes programmable service-level interfaces.
- Know which interfaces ride on MGD and which ride on JSD.
- Be able to explain why you would choose an API-driven service interface over a configuration-oriented management path.
- Understand how Terraform treats Junos configuration as declarative infrastructure-as-code.
Expect scenario-style questions: given a goal such as pushing configuration at scale or exposing a programmable service, which mechanism fits? Python and PyEZ appear in the overview as part of the broader skill set, so be comfortable reading short PyEZ-style snippets and recognizing what they do, even though the verified assessment is written rather than hands-on.
Domain 2: gRPC
The gRPC domain has the most named technical vocabulary of the five, and much of it is interconnected. It covers gRPC and gNMI used for both automation and telemetry, which is worth stating explicitly because candidates sometimes study only one use.
Topics to master
Build a mental model of how data is described, transported, addressed and consumed.
- Protocol buffers: the serialization format used to define and encode messages.
- The gRPC protocol: how remote procedure calls are carried and how clients and servers interact.
- gNMI: the network management interface built on gRPC, used for configuration and state retrieval and for streaming telemetry.
- OpenConfig: vendor-neutral models that give gNMI paths consistent meaning.
- Sensor paths: how you specify exactly which operational data a telemetry subscription streams.
- gNMIc: the client tool for interacting with gNMI targets.
- TIG stack: the Telegraf, InfluxDB and Grafana pipeline for collecting, storing and visualizing telemetry.
A useful way to connect the pieces: YANG and OpenConfig define the data model, protocol buffers and gRPC move it, gNMI provides the operations, sensor paths select the data, and the TIG stack makes it visible. That chain is also why this domain overlaps conceptually with the YANG domain, and why studying them back to back pays off.
Key Takeaway
Do not treat telemetry as an afterthought. Questions can probe the difference between using gNMI to push or fetch configuration versus subscribing to streamed state, and how sensor paths and the TIG stack fit the streaming case.
Domain 3: Ansible
The Ansible domain is about operating Junos through Ansible rather than memorizing generic Ansible trivia. The official scope names supported files, playbooks, Vault, JSNAPy, and Jinja2 templates.
What each element means for Junos work
Think in terms of a workflow: inventory and variables describe devices, templates generate configuration, playbooks apply it, Vault protects secrets, and JSNAPy validates results.
- Supported files: know the file types an Ansible project uses and what each is for.
- Playbooks: structure, plays, tasks and how they target Junos devices.
- Vault: protecting sensitive values such as credentials rather than leaving them in plain text.
- Jinja2 templates: variable substitution, loops and conditionals to render device configuration from data.
- JSNAPy: taking snapshots and running tests to verify device state before and after a change.
The pairing of Jinja2 and JSNAPy is a good study anchor: one generates intended state, the other verifies actual state. Be ready to reason about which tool answers a given need, such as rendering a configuration from variables versus checking that a change produced the expected operational result.
Domain 4: Junos Automation Scripts
This domain concentrates on on-box automation. The objective names four script types: commit, op, event, and SNMP scripts, and it asks for their concepts, benefits and operation. That wording signals conceptual questions about what each script type is for and when it runs, not just syntax.
| Script type | Study focus |
|---|---|
| Commit scripts | Run during the commit process to inspect or modify configuration, enforcing standards before a change takes effect |
| Op scripts | Run on demand from the operational CLI to automate troubleshooting or custom commands |
| Event scripts | Triggered by system events, enabling reactive, self-healing behavior |
| SNMP scripts | Tied to SNMP interactions, extending how Junos responds to or exposes SNMP data |
The trigger is the key discriminator. For each script type, be able to state what causes it to run, what it can read or change, and the benefit it delivers. Questions in this style often describe a requirement, such as enforcing a naming rule on every commit or reacting automatically to a logged event, and ask you to pick the matching script type.
Domain 5: YANG
YANG is the data-modeling language underneath much of modern network automation, and this domain asks about YANG implementation, OpenConfig configuration models, syntax, and data types.
Reading YANG fluently
You should be able to read a short YANG module and describe what it models, even without writing one from scratch.
- Recognize the structural statements that organize a module and its hierarchy.
- Know the common data types and how types constrain values.
- Understand how OpenConfig models differ in intent from vendor-native models.
- Understand how Junos implements YANG-modeled data and how models relate to the interfaces you studied in the gRPC domain.
Because the gRPC domain leans on OpenConfig models and sensor paths, a solid grasp of YANG makes the telemetry material far less abstract. Candidates who skip YANG often find the gNMI path questions confusing for exactly that reason.
Sequencing the Domains in Your Prep
Since weights are unpublished, spread effort according to your own gaps rather than a guessed percentage. The ordering below follows conceptual dependencies: models first, then transport, then tooling, then on-box scripts. For a fuller plan, see the JNCIS-DevOps study guide.
Platform Automation Overview and YANG
- Map MGD, JSD/JET and Terraform to the tasks each handles.
- Learn YANG syntax and data types; read OpenConfig modules.
gRPC
- Connect protocol buffers, gRPC, gNMI and sensor paths.
- Sketch a TIG telemetry pipeline end to end.
Ansible and Junos Automation Scripts
- Trace a playbook with Jinja2, Vault and JSNAPy.
- Tabulate commit, op, event and SNMP script triggers.
Mixed review
- Take original practice questions across all five domains and revisit weak areas.
Hands-on labs help cement this material, though the verified assessment is a written multiple-choice exam. Use the JNCIS-DevOps practice tests to rehearse the question style, and keep a one-page recap using the JNCIS-DevOps cheat sheet for final review.
Where the Specialist Credential Fits Professionally
The specialist exam targets people who automate Juniper environments: network automation engineers, NetDevOps practitioners, and network engineers moving from CLI-centric work toward code-driven operations. The domains mirror real duties, including templated configuration with Ansible, streaming telemetry into dashboards, on-box scripting, and model-driven management. For a view of roles that reference these skills, see the JNCIS-DevOps jobs overview, and for the career-value question, the ROI analysis. We do not quote salary figures here because no verified numbers exist for this credential.
Renewal and Credential Lifecycle
The certification is active for three years. You can renew before expiration by passing an eligible examination or by completing a designated instructor-led or On-Demand course. The specialist course-renewal table lists Junos Platform Automation and NetDevOps or Advanced Junos Platform Automation and NetDevOps; only one eligible course is required, and Open Learning does not qualify for this route. If the credential expires, you must restart at the beginning of the track, so track your expiration date carefully.
On exam day, OnVUE delivery requires identity, equipment and room checks and prohibits unauthorized books, notes and other reference materials. Plan your room and hardware setup ahead of time, and review scheduling options in the exam dates guide.
Frequently Asked Questions
Juniper does not publish percentage weights for the five objectives, so you cannot assume equal weighting or identify a heaviest domain. Prepare all five and let your own weak spots guide the time you allocate.
Study for JN0-423, which is based on Junos OS 24.4. It replaced JN0-422 on October 6, 2025. Avoid older outlines and Junos 21.3 references, since they describe the retired exam.
The exam has 65 multiple-choice questions to be completed in 90 minutes, delivered in English. The scored versus unscored split was not verified, so treat every question as if it counts.
The standard specialist-exam voucher is USD 300. Pearson VUE provides test-center and OnVUE delivery, and current issuer instructions direct you to schedule, manage and launch exams through Alpine CertMetrics using your hpe.com account.
JNCIA-DevOps is the prerequisite certification, but associate preparation does not replace the specialist objectives. You still need to learn the five domains covered here, especially gRPC and YANG depth, in their own right.