JN0-106 Junos Configuration Basics Practice Question
An engineer needs to configure a static route on a Juniper device. Which statement is true regarding the configuration process?
⚠ Common exam trap
The trap here is that candidates familiar with Cisco IOS, where 'set' or 'configure terminal' commands take effect immediately, mistakenly assume Junos behaves the same way, overlooking the mandatory commit step.
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
✓
Configuration changes must be committed to become active.
In Junos, configuration changes are made in a candidate configuration and do not take effect until explicitly committed using the 'commit' command. This two-phase model (edit then commit) ensures that changes are validated before activation, preventing partial or incorrect configurations from disrupting network operations. Option B correctly identifies this requirement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The set command activates the change for 10 minutes by default.
Why it's wrong here
A Junos device does not apply a default 10-minute activation window to `set` commands. The `set` command modifies only the candidate configuration, which persists in the configuration database until you explicitly commit it or discard it with `rollback`. No timer automatically promotes candidate changes to active; activation always requires an explicit commit, and if you do not commit, the changes remain inactive indefinitely.
- ✓
Configuration changes must be committed to become active.
Why this is correct
In Junos, the CLI operates on a candidate configuration that is separate from the active, committed configuration. When you enter a `set` command, the change is stored in the candidate but is not yet applied to the router's runtime processes. The `commit` command validates the candidate, installs it as the new active configuration, and applies it immediately without reboot, making commit the mandatory step for any configuration change to take effect.
- ✗
The configuration is immediately active upon entering the set command.
Why it's wrong here
Entering a `set` command does not immediately alter the active configuration; it only writes a provisional change into the candidate configuration. The router continues using the previously committed configuration until a `commit` is issued. This staged model allows you to build and validate a set of changes atomically, preventing partial or inconsistent configurations from being applied to the live network.
- ✗
The commit command requires a reboot to take effect.
Why it's wrong here
The `commit` command activates configuration changes immediately on the running Junos system, and it does not require a reboot. Junos dynamically applies the new configuration to the relevant software processes; for most changes such as routing policies, interfaces, and firewall filters, the effect is instantaneous. A reboot is only needed for a very small set of system-level parameters (if any), and even then the device would not require a full reboot solely because of commit—Separation of candidate and active configuration ensures that commit itself is a hot operation.
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.