JN0-106 Junos Configuration Basics Practice Question
A network engineer needs to make a change to a Junos device and ensure the change can be reverted if it causes issues. Which feature should be used?
⚠ Common exam trap
Test-takers frequently confuse `commit confirmed` with `rollback 0`, thinking both revert changes, but `rollback 0` is a manual step that does not provide automatic, time-based reversion.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
commit confirmed
The `commit confirmed` command allows an engineer to commit a configuration change with a timer (default 10 minutes). If the change causes issues and the engineer does not confirm the commit within the timer, the device automatically reverts to the previous active configuration. This provides a safety net to revert changes without manual intervention.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
configure exclusive
Why it's wrong here
The `configure exclusive` command acquires an exclusive lock on the configuration database at the `configure` prompt, blocking other users from editing. However, it only prevents concurrent modifications; it does not schedule any automatic rollback if the applied changes fail. A manual `rollback` or a separate `commit confirmed` would be needed to recover, so it is not the correct choice for a self-reverting change.
- ✓
commit confirmed
Why this is correct
The `commit confirmed` operation commits the candidate configuration and starts a rollback timer (default 10 minutes, up to 285 minutes with `commit confirmed <minutes>`). If the engineer does not issue a confirming `commit` or `commit confirm` before the timer expires, Junos automatically reverts to the previous active configuration. This provides a safety net for testing break-fix changes, making it the correct answer.
- ✗
commit check
Why it's wrong here
The `commit check` command validates the candidate configuration for syntax errors, missing parameters, and resource conflicts without activating it. While it catches many errors, it performs no commit and creates no commit entry, so there is no change to roll back. It is a pre-flight validation tool, not a method to implement a change safely—the change never becomes active.
- ✗
rollback 0
Why it's wrong here
The `rollback 0` command restores the candidate configuration to match the last committed configuration, effectively discarding any uncommitted edits made in the current session. Because it only affects the pending candidate and not the active configuration, it cannot protect against problems caused by a committed change. It is used to cancel changes before they are committed, not to recover from a bad commit.
Go deeper
Related to this question
About these practice questions
One of 156 original JN0-106 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This JN0-106 practice question is part of Courseiva's free Juniper Networks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the JN0-106 exam.