JNCIS-DevOps study guide
JNCIS-DevOps · Work through your exam, one topic at a time.
The Juniper Networks Certified Specialist DevOps credential - commonly written JNCIS-DevOps - is a specialist-level certification aimed at network engineers, automation engineers and platform teams who build and operate Juniper-based networks through software rather than manual CLI work. The published blueprint splits the exam into five equally weighted domains of 20 percent each: DevOps fundamentals and culture; automation and configuration management; continuous integration and continuous delivery; infrastructure as code and network programmability; and monitoring, observability and operations. The JNCIS-DevOps study guide has 5 sections and about 1,823 words.
01DevOps Fundamentals and Culture
The DevOps fundamentals domain tests whether you can explain why network teams adopt DevOps practices, not just name tools. Expect questions on CALMS, the Three Ways, DORA metrics and blameless incident review, framed around Junos change workflows.
371 words, about 2 min02Automation and Configuration Management
Automation and configuration management tests your ability to change Junos devices safely and repeatably: the Junos commit model, Junos PyEZ, and configuration management tools such as Ansible and Salt. The Junos commit model is the safety net.
367 words, about 2 min03Continuous Integration and Continuous Delivery
CI/CD tests pipeline design for network change: source control, automated validation, artefact promotion, safe deployment patterns and rollback. Config templates, YAML data, tests and pipeline definitions live in version control; the pipeline itself is code (Jenkinsfile, .gitlab-ci.yml ).
375 words, about 2 min04Infrastructure as Code and Network Programmability
This domain covers describing infrastructure as code and the programmatic interfaces on Junos: YANG and OpenConfig data models, NETCONF, REST, gNMI and templating. Declarative vs imperative.
354 words, about 2 min05Monitoring, Observability and Operations
Monitoring, observability and operations tests how you know a network is healthy: telemetry collection, alert design, SLOs and incident response on Junos. Monitoring answers known questions; observability lets you ask new ones.
356 words, about 2 min