- A
show system configuration
Why wrong: Not a valid command.
- B
show system rollback
Why wrong: Shows rollback files, not pending changes.
- C
show configuration | compare
Shows uncommitted configuration differences.
- D
show system commit
Why wrong: Shows commit history, not pending changes.
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.
JNCIA-JUNOS Operational Monitoring and Maintenance Practice Question
This JNCIA-JUNOS practice question tests your understanding of operational monitoring and maintenance. Examine the command output carefully: the correct answer depends on what the output actually shows, not on general recall alone. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
An engineer needs to check if the device has any pending changes that have not been committed. Which operational command should they run?
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
Option C is correct because 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.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
show system commit
Why it's wrong here
Shows commit history, not pending changes.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often 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.
Trap categories for this question
Command / output trap
Not a valid command.
Detailed technical explanation
How to think about this question
Junos uses a two-phase commit model: changes are made to the candidate configuration in the 'candidate' database, and then committed to the 'active' database. The 'show configuration | compare' command leverages the 'compare' pipe to output only the lines that differ between the candidate and active configurations, using diff-like syntax (lines prefixed with '+' for additions and '-' for deletions). This is essential for verifying changes before committing, especially in production environments where an accidental commit could cause network outages.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the JNCIA-JUNOS exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Operational Monitoring and Maintenance — study guide chapter
Learn the concepts, then practise the questions
- →
Operational Monitoring and Maintenance practice questions
Targeted practice on this topic area only
- →
All JNCIA-JUNOS questions
514 questions across all exam domains
- →
Juniper Networks Certified Associate Junos JNCIA-Junos study guide
Full concept coverage aligned to exam objectives
- →
JNCIA-JUNOS practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related JNCIA-JUNOS practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
User Interfaces practice questions
Practise JNCIA-JUNOS questions linked to User Interfaces.
Junos Configuration Basics practice questions
Practise JNCIA-JUNOS questions linked to Junos Configuration Basics.
Operational Monitoring and Maintenance practice questions
Practise JNCIA-JUNOS questions linked to Operational Monitoring and Maintenance.
Routing Fundamentals practice questions
Practise JNCIA-JUNOS questions linked to Routing Fundamentals.
Networking Fundamentals practice questions
Practise JNCIA-JUNOS questions linked to Networking Fundamentals.
Junos OS Fundamentals practice questions
Practise JNCIA-JUNOS questions linked to Junos OS Fundamentals.
JNCIA-JUNOS fundamentals practice questions
Practise JNCIA-JUNOS questions linked to JNCIA-JUNOS fundamentals.
JNCIA-JUNOS scenario practice questions
Practise JNCIA-JUNOS questions linked to JNCIA-JUNOS scenario.
JNCIA-JUNOS troubleshooting practice questions
Practise JNCIA-JUNOS questions linked to JNCIA-JUNOS troubleshooting.
Practice this exam
Start a free JNCIA-JUNOS practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this JNCIA-JUNOS question test?
Operational Monitoring and Maintenance — This question tests Operational Monitoring and Maintenance — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: show configuration | compare — Option C is correct because 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.
What should I do if I get this JNCIA-JUNOS question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more ways this is tested on JNCIA-JUNOS
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.
Last reviewed: Jun 24, 2026
This JNCIA-JUNOS 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 JNCIA-JUNOS exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.