How to Check Uncommitted Configuration in Junos
An engineer needs to check if the device has any pending changes that have not been committed. Which operational command should they run?
Quick Answer
The answer is the operational command `show configuration | compare`. This command is correct because it displays the differences between the candidate configuration—where uncommitted changes are staged—and the active, running configuration, effectively showing any pending uncommitted configuration that has not yet been applied. On the JNCIA-Junos exam, this question tests your understanding of Junos’s commit model, where changes are made to a candidate configuration and must be explicitly committed to become active. A common trap is confusing this with `show configuration`, which only displays the current active configuration without revealing pending changes, or with `commit check`, which validates syntax but does not show differences. To remember this, think of the pipe to `compare` as a “diff” tool: it compares what you have staged against what is live, making it the go-to command for viewing uncommitted changes before committing.
⚠ Common exam trap
Many candidates confuse 'show system commit' (which shows commit history) with showing pending changes, or they think 'show configuration' alone shows uncommitted changes, but without the '| compare' pipe it only shows the active configuration.
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
✓
show configuration | compare
The 'show configuration | compare' command displays the differences between the candidate configuration (changes made but not yet committed) and the active configuration. This allows the engineer to see any pending changes that have not been committed, which is exactly what the question asks.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
show system configuration
Why it's wrong here
Not a valid command.
- ✗
show system rollback
Why it's wrong here
Shows rollback files, not pending changes.
- ✓
show configuration | compare
Why this is correct
Shows uncommitted configuration differences.
- ✗
show system commit
Why it's wrong here
Shows commit history, not pending changes.
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 →
Same concept, more angles
1 more way this is tested on JN0-106
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. An engineer needs to check the last time the configuration was changed. Which command provides this information?
easy- ✓ A.show system commit
- B.show configuration | display set
- C.show system alarms
- D.show system uptime
Why A: The 'show system commit' command displays the commit history, including the date, time, and user for each configuration change. This allows the engineer to see exactly when the last configuration was committed, which is the definitive way to determine the last time the configuration was changed.
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.