JN0-106 User Interfaces Practice Question
Which TWO statements are true about the 'commit confirmed' command? (Choose two.)
⚠ Common exam trap
A common mix-up: candidates confuse 'commit confirmed' with 'commit at' (scheduling) or assuming the timeout is restricted to 5-minute increments, when in fact it accepts any integer minute value.
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
✓
The default timeout is 10 minutes.
Option B is correct because the 'commit confirmed' command in Junos OS uses a default rollback timeout of 10 minutes, during which the configuration is active but not yet permanent. Option E is correct because the commit only becomes permanent if the administrator issues a confirming 'commit' command within that timeout window; otherwise, the device automatically rolls back to the previous configuration. Option A is incorrect because scheduling a commit for a future time is done with the 'commit at' command, not 'commit confirmed'. Option C is incorrect because 'commit confirmed' does not save the configuration to a file before applying; it applies the candidate configuration with an automatic rollback timer. Option D is incorrect because the timeout can be set to any value from 1 to 65,535 minutes using the 'commit confirmed <minutes>' syntax, not only in multiples of 5 minutes.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
It is used to schedule a commit at a future time.
Why it's wrong here
This option confuses 'commit confirmed' with 'commit at', which is a separate Junos feature for scheduling configuration activation at a specific future time. A confirmed commit takes effect immediately upon execution, but it starts a rollback timer; if the commit is not confirmed within the timeout window, the system automatically reverts. No future scheduling is involved—the change is active right away.
- ✓
The default timeout is 10 minutes.
Why this is correct
When you issue 'commit confirmed' without explicitly specifying a timeout, Junos applies a default of 10 minutes. This means the new configuration remains active for exactly 10 minutes, and if no confirmation is received before the timer expires, the system automatically restores the previous configuration. You can override this default by appending a numeric value to the command, such as 'commit confirmed 5'.
- ✗
It saves the configuration to a file before applying.
Why it's wrong here
A confirmed commit does not create or save a separate configuration file; it simply marks the current configuration as active and preserves the previous configuration as a rollback point in memory. This rollback point is maintained by the Junos commit process and is used only if the confirm timer expires. No file-based backup is produced, and the standard candidate/config database behavior remains unchanged.
- ✗
The timeout can be set only in multiples of 5 minutes.
Why it's wrong here
The timeout for a confirmed commit is not restricted to multiples of 5; it accepts any integer minute value from 1 through 65535. For example, 'commit confirmed 3' is a perfectly valid command that sets a three-minute confirmation window. Junos does not impose rounding or force values to a five-minute granularity, so this statement is factually incorrect.
- ✓
It requires a confirmation within the specified time to make the commit permanent.
Why this is correct
The entire purpose of a confirmed commit is to require a second action before the configuration becomes permanent. If you do not issue the appropriate confirmation within the configured time, Junos automatically rolls back to the last stable configuration, protecting against accidental lockout. A confirmation can be performed with 'commit confirm' or by simply issuing another regular commit, which cancels the rollback timer.
Go deeper
Related to this question
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.