New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Juniper JN0-105 Exam - Topic 1 Question 6 Discussion

Actual exam question for Juniper's JN0-105 exam
Question #: 6
Topic #: 1
[All JN0-105 Questions]

You are logged in to a Junos OS device with SSH and issued the show protocols | compare command in the configuration, but no output is shown.

Which statement is correct in this scenario?

Show Suggested Answer Hide Answer
Suggested Answer: B

If issuing the 'show | compare' command in configuration mode yields no output, it indicates that there are no changes to the candidate configuration (B). This command is used to compare the current candidate configuration with the active configuration, and a lack of output suggests that the candidate configuration matches the active one, meaning no changes have been made or the changes have already been committed.


Contribute your Thoughts:

0/2000 characters
Marti
3 months ago
Just to clarify, B is the most straightforward explanation here.
upvoted 0 times
...
Helga
3 months ago
Really? I thought A was the case. That’s surprising!
upvoted 0 times
...
Sommer
3 months ago
Wait, C could be a possibility too. What if someone messed up?
upvoted 0 times
...
Jeannetta
4 months ago
I disagree, D makes sense too. You need to commit first!
upvoted 0 times
...
Misty
4 months ago
B is definitely the right answer. No changes means no output.
upvoted 0 times
...
Sharita
4 months ago
I practiced a similar question, and I think you need to commit changes for them to show up, so maybe D is the answer?
upvoted 0 times
...
Nan
4 months ago
I’m not sure, but I feel like if someone deleted the active configuration, we would see an error instead of just no output.
upvoted 0 times
...
Florinda
4 months ago
I think option B sounds right because if there are no changes, then there wouldn't be any output, right?
upvoted 0 times
...
Alita
5 months ago
I remember something about the command showing differences, but I thought it applied to more than just interfaces.
upvoted 0 times
...
Kris
5 months ago
I think the key here is that you have to commit the config before any output will be shown. That makes sense to me, so I'll go with that.
upvoted 0 times
...
Lajuana
5 months ago
Okay, let me think this through. If there are no changes to the candidate config, that would explain why no output is shown. I'll keep that in mind.
upvoted 0 times
...
Kanisha
5 months ago
Hmm, this is a tricky one. I'm not sure if the command only works for interface configs or if there's something else going on here.
upvoted 0 times
...
Matthew
5 months ago
Wait, did someone delete the active config? That could definitely cause this issue. I'll have to consider that as a possibility.
upvoted 0 times
...
Pedro
5 months ago
I've got a good handle on directory inputs, so I feel pretty confident about this one. I'll make sure to select all the correct options.
upvoted 0 times
...
Serita
5 months ago
This seems straightforward. The question is asking for the annotation to use to ensure immediate timeout, and option A clearly specifies a 1-second timeout, which is what we want.
upvoted 0 times
...
Annamaria
2 years ago
I'm not sure, but I think the command only works for interface configuration differences.
upvoted 0 times
...
Salome
2 years ago
I disagree, I believe the answer is D) You must commit the configuration before any output will be shown.
upvoted 0 times
...
Domitila
2 years ago
I think the correct answer is B) There are no changes to the candidate configuration.
upvoted 0 times
...

Save Cancel