JN0-106 Junos Configuration Basics Practice Question
When configuring a new Juniper router, an engineer needs to ensure that configuration changes are not automatically committed after a certain time if not explicitly confirmed. Which configuration parameter controls this?
⚠ Common exam trap
A common mix-up: candidates confuse 'commit confirmed' with 'commit at' or 'commit synchronize', thinking any time-based or dual-RE feature provides automatic rollback, but only 'commit confirmed' enforces a confirmation window to prevent permanent unverified changes.
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 is used to apply a configuration change that will automatically roll back to the previous configuration if not explicitly confirmed within a specified time period (default 10 minutes). This ensures that changes are not permanently applied unless the engineer verifies them, preventing accidental lockout or misconfiguration.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
commit check
Why it's wrong here
The 'commit check' command validates the candidate configuration by parsing syntax and verifying the statement hierarchy without activating the configuration. It acts as a pre-flight test that reports errors but leaves the running configuration untouched, so it cannot provide the automatic rollback safety required when applying changes to a new router.
- ✗
commit at
Why it's wrong here
The 'commit at' command schedules the candidate configuration to be committed at a specific time in the future, making it useful for planned maintenance windows. It does not, however, require confirmation after the commit nor does it automatically revert the changes if the network becomes unreachable, so it does not offer the fail-safe that 'commit confirmed' provides.
- ✗
commit synchronize
Why it's wrong here
The 'commit synchronize' command is used only in multi-chassis systems, such as a chassis cluster or a multi-chassis routing configuration, where the commit must be applied to both members simultaneously. On a single standalone router it is not applicable, and it does not provide any mechanism for confirmation-based rollback, making it irrelevant as a safety measure for a new router.
- ✓
commit confirmed
Why this is correct
The 'commit confirmed' command makes the candidate configuration active and then automatically rolls back to the previous configuration if the engineer does not issue a confirming commit within the default timeout interval (10 minutes, configurable). This is essential when configuring a new router remotely, because it ensures that a mistaken change that severs the management session will be undone automatically, letting the engineer regain access.
Go deeper
Related to this question
About these practice questions
One of 326 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.