JN0-106 User Interfaces Practice Question
An engineer wants to apply a candidate configuration and automatically revert to the previous configuration after 10 minutes if the commit is not confirmed. Which command should be used?
⚠ Common exam trap
Test-takers frequently confuse the `commit confirmed` timer with the `commit at` scheduling feature, which sets an absolute time for a commit rather than a countdown for automatic rollback.
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 10
The `commit confirmed 10` command commits the candidate configuration and starts a 10-minute timer. If the commit is not explicitly confirmed with another `commit` command within that time, Junos automatically reverts to the previous configuration. This is the correct method for a timed automatic rollback after a commit.
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 confirmed 10
Why this is correct
The `commit confirmed 10` command commits the active candidate configuration immediately and starts a 10-minute rollback timer. If you do not issue a confirming commit (such as `commit confirm` or `commit`) before the timer expires, Junos automatically reverts to the previous configuration. This protects against remote device lockout by ensuring that an unconfirmed commit is undone, making it the correct way to apply a candidate config with an automatic safety rollback.
- ✗
commit at 10
Why it's wrong here
The `commit at 10` command schedules the candidate configuration to be committed at a specific time, not as a rollback safeguard. In Junos, `commit at` expects a time value (e.g., `commit at 14:00`), so `10` would be treated as a time-of-day or an invalid input, and it does not create any automatic rollback behavior. This option neither applies the configuration immediately nor provides the auto-revert safety net that `commit confirmed` offers.
- ✗
set system commit timer 10
Why it's wrong here
The `set system commit timer 10` command does not exist in Junos configuration. Junos does not have a global commit timer knob; the only way to set a rollback timeout is through the `commit confirmed <minutes>` command at the configuration mode prompt. Any attempt to use this command would result in a syntax error, so it cannot fulfill the engineer's requirement.
- ✗
commit check
Why it's wrong here
The `commit check` command validates the candidate configuration for syntax and consistency errors without activating it. It is essentially a dry-run that reports problems, but the configuration remains uncommitted, meaning the active configuration is unchanged. Since it does not apply the candidate config and does not set any rollback timer, it is unsuitable for the engineer's need to apply and automatically revert if necessary.
About these practice questions
This JN0-106 question is part of Courseiva's 326-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.