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-351 Exam - Topic 4 Question 47 Discussion

Actual exam question for Juniper's JN0-351 exam
Question #: 47
Topic #: 4
[All JN0-351 Questions]

You are an operator for a network running 1S-IS. Two routers are failing to form an adjacency. What are two reasons for this problem? (Choose two.)

Show Suggested Answer Hide Answer

Contribute your Thoughts:

0/2000 characters
Reid
2 months ago
Missing family iso config is a big deal, can't overlook that!
upvoted 0 times
...
King
2 months ago
Wait, is it really possible to have no ISO address? That seems odd.
upvoted 0 times
...
Anissa
2 months ago
I think the area ID mismatch is a common culprit too.
upvoted 0 times
...
Janae
3 months ago
I disagree, I’ve seen adjacencies form without that being a problem.
upvoted 0 times
...
Felicidad
3 months ago
Mismatched router IDs can definitely cause issues.
upvoted 0 times
...
Quentin
3 months ago
I think the family iso configuration is important, so D might be a reason as well, but I need to double-check that.
upvoted 0 times
...
Tijuana
3 months ago
I practiced a question like this, and I feel like mismatched router IDs could be a factor, but I can't recall if that's specifically for L2 routers.
upvoted 0 times
...
Major
4 months ago
I'm not entirely sure, but I think if the ISO address isn't configured, that could definitely prevent adjacency. So, B might be right too.
upvoted 0 times
...
Aimee
4 months ago
I remember something about mismatched area IDs causing adjacency issues, so maybe option C is a good choice.
upvoted 0 times
...
Miriam
4 months ago
This seems straightforward. The key is to identify any mismatches in the router ID or area ID between the two routers. That's probably the issue here.
upvoted 0 times
...
Twana
4 months ago
I'm a bit confused on this one. I know it's related to the IS-IS configuration, but I'm not sure which specific settings could be causing the problem.
upvoted 0 times
...
Emily
4 months ago
Alright, I've got this. The mismatched area ID and missing family iso config are the two most likely culprits here.
upvoted 0 times
...
Omer
5 months ago
Okay, let's see. I'm pretty sure it has to do with the ISO address configuration, but I'll double-check the other options just in case.
upvoted 0 times
...
Nana
5 months ago
Hmm, this one seems tricky. I'll need to think through the possible reasons for the adjacency issue carefully.
upvoted 0 times
...

Save Cancel