LEARN. PRACTICE. GROW.Concept and mechanism
Junos distinguishes candidate and active configuration. Editing the candidate does not immediately change service. In configuration mode, show | compare helps review differences against active configuration. In normal mode, operators can share the candidate; private allows separate preparation copies but does not eliminate conflicts when changes converge. Exclusive introduces locking and should be coordinated. Hierarchical navigation, contextual help, and output filtering reduce errors when used with attention to current mode and level. A show command in configuration context does not necessarily observe the same object as an operational command.
Guided application
In a fictional remote rehearsal, commit confirmed temporarily activates a change with a confirmation deadline. The team should define who confirms, which tests finish first, and how it recovers if access is lost. The Junos reference permits confirmation through commit or commit check; running the latter during testing is not neutral to pending rollback. Syntax validation does not prove functional traffic. Confirm new sessions and representative flows while retaining alternate access. Examples follow the Junos 21.2 exam baseline; documentation for 24.2R1 and later adds commit-comment requirements that should be checked for the installed version. J-Web offers another interface for common functions without removing the need to understand candidate, activation, and state. Operational discipline depends on outcomes rather than the chosen interface.
Premature commit check can confirm a change before testing finishes.
Common pitfalls
Editing as activation; private as no conflicts; old session as acceptance; check as always effect-free.
Related topics: Addressing and capacity · Junos planes and state interpretation · Access, inheritance, and recovery
Coordinate confirmation with functional evidence.
Reference: Commit workflow and confirmed rollback · JN0-106, effective 2026-04-06; Junos OS 21.2 exam baseline