Free Download Juniper JN0-694 VCE Test Engine Full Version Now

Juniper Networks Certified Support Professional (JNCSP-ENT): JN0-694 Exam
JN0-694 Questions & Answers
Exam Code: JN0-694
Exam Name: Juniper Networks Certified Support Professional (JNCSP-ENT)
Q & A: 50 Q&As

QUESTION 1
Referring to the exhibit, why are the OSPF routes missing from the routing table for this router?
user@router> show ospf database
Area 0.0.0.1
Type ID Adv Rtr Seq Age Opt Cksum Len
Router 172.24.255.1 172.24.255.1 0x800000d4 182 0x22 0x59f3 36
Router 172.24.255.2 172.24.255.2 0x800000d4 177 0x22 0x57f2 36
Router *172.24.255.4 172.24.255.4 0x800000dc 176 0x22 0x75fa 72
Network 172.24.124.2 172.24.255.2 0x80000007 177 0x22 0x7957 36
Summary 172.24.13.0 172.24.255.1 0x80000004 2370 0x22 0x3f62 28
Summary 172.24.23.0 172.24.255.1 0x80000002 471 0x22 0xdeb9 28
Summary 172.24.255.1 172.24.255.1 0x800000cb 2037 0x22 0x2bbb 28
Summary 172.24.255.2 172.24.255.2 0x800000cc 487 0x22 0x19ca 28
Summary 172.24.255.3 172.24.255.1 0x80000003 140 0x22 0xb2f9 28
OSPF AS SCOPE link state database
Type ID Adv Rtr Seq Age Opt Cksum Len
Extern *1.47.82.0 172.24.255.4 0x80000002 1037 0x22 0x4225 36
Extern *100.0.0.0 172.24.255.4 0x80000001 2643 0x22 0xfc88 36
user@router> show ospf neighbor
Address Interface State ID Pri Dead
172.24.124.2 ge-0/0/1.0 Full 172.24.255.2 128 36
172.24.124.1 ge-0/0/1.0 Full 172.24.255.1 128 30
user@router> show ospf interface ge-0/0/1.0 extensive
Interface State Area DR ID BDR ID Nbrs
ge-0/0/1.0 PtToPt 0.0.0.1 0.0.0.0 0.0.0.0 2
Type: P2MP, Address: 172.24.124.4, Mask: 255.255.255.0, MTU: 1500,
Cost: 1
Adj count: 2
Hello: 10, DeaD. 40, ReXmit: 5, Not Stub
Auth type: None
Protection type: None
Topology default (ID 0) -> Cost: 1
A. mismatching OSPF interface type with the neighbor
B. MTU mismatch with the neighbor
C. incorrect IP address configured on the interface
D. no Type 4 LSAs in the OSPF database
Answer: A

QUESTION 2
You notice that there is a problem with the OSPF adjacency between two routers, R1 and R2.
The relevant system logs from R1 are shown in the exhibit.
What would cause this behavior?
Jun 12 02:56:06 R1 rpd[60735]: RPD_OSPF_NBRDOWN: OSPF neighbor
10.50.10.25 (realm
ospf-v2 fe-0/0/4.0 area 0.0.0.0) state changed from Full to Init due to
1WayRcvd (event reason:
neighbor is in one-way mode)
Jun 12 02:59:36 R1 rpd[60735]: RPD_OSPF_NBRUP: OSPF neighbor
10.50.10.25 (realm ospf-v2 fe-0/0/4.0 area 0.0.0.0) state changed from Init to ExStart due to
2WayRcvd (event reason:
neighbor detected this router)
Jun 12 02:59:36 R1 rpd[60735]: RPD_OSPF_NBRUP: OSPF neighbor
10.50.10.25 (realm ospfv2
fe-0/0/4.0 area 0.0.0.0) state changed from Exchange to Full due to
ExchangeDone (event
reason: DBD exchange of slave completed)
A. R2 was dropping R1’s OSPF hello packets.
B. R1 was dropping R2’s OSPF hello packets.
C. R1’s interface went down and came back up.
D. There is an OSPF hello timer mismatch between the two routers.
Answer: A

QUESTION 3
Referring to the exhibit, you are configuring an OSPF network. All OSPF adjacencies come up
and stay stable. But neither R1 nor R2 has the prefix 200.200.200.200/32 in its routing table.
What is causing this problem?
A. R2 does not have the export policy for prefix 200.200.200.200/32.
B. R1 does not have routes to network 172.10.1.0/24.
C. R2 is BDR on both network 172.10.1.0/24 and 172.20.1.0/24.
D. The router ID of R1 is the same as the router ID of R3.
Answer: D

QUESTION 4
You are troubleshooting an OSPF adjacency problem between R1 and R2.
Referring to the exhibit, what is causing this OSPF adjacency problem?
A. There is a hello interval mismatch.
B. There is a dead interval mismatch.
C. There is an MTU mismatch.
D. There is an LSA refresh timer mismatch.
Answer: C

QUESTION 5
You are trying to establish an OSPF adjacency between R1 and R2, but the adjacency does not
establish.
Referring to the exhibit, what is causing the adjacency to fail?
user@R1> show ospf neighbor
Address Interface State ID Pri Dead
10.222.0.2 ge-0/0/1.0 Init 10.222.1.2 128 32
user@R1> show ospf interface detail
Interface State Area DR ID BDR ID Nbrs
ge-0/0/1.0 DR 0.0.0.0 10.222.1.1 0.0.0.0 1
Type: LAN, Address: 10.222.0.1, Mask: 255.255.255.252, MTU: 1500, Cost:
1
DR addr: 10.222.0.1, Priority: 128
Adj count: 0
Hello: 10, DeaD. 40, ReXmit: 5, Not Stub
Auth type: MD5, Active key ID. 10, Start time: 1970 Jan 1 00:00:00 UTCProtection type: None
Topology default (ID 0) -> Cost: 1
lo0.0 DR 0.0.0.0 10.222.1.1 0.0.0.0 0
Type: LAN, Address: 10.222.1.1, Mask: 255.255.255.255, MTU: 65535,
Cost: 0
DR addr: 10.222.1.1, Priority: 128
Adj count: 0
Hello: 10, DeaD. 40, ReXmit: 5, Not Stub
Auth type: None
Protection type: None
Topology default (ID 0) -> Cost: 0
user@R2> show ospf neighbor
user@R2> show ospf interface detail
Interface State Area DR ID BDR ID Nbrs
ge-0/0/1.0 PtToPt 0.0.0.0 0.0.0.0 0.0.0.0 0
Type: P2P, Address: 10.222.0.2, Mask: 255.255.255.252, MTU: 1500, Cost:
1
Adj count: 0
Hello: 10, DeaD. 40, ReXmit: 5, Not Stub
Auth type: MD5, Active key ID. 10, Start time: 1970 Jan 1 00:00:00 UTC
Protection type: None
Topology default (ID 0) -> Cost: 1
lo0.0 DR 0.0.0.0 10.222.1.2 0.0.0.0 0
Type: LAN, Address: 10.222.1.2, Mask: 255.255.255.255, MTU: 65535,
Cost: 0
DR addr: 10.222.1.2, Priority: 128
Adj count: 0
Hello: 10, DeaD. 40, ReXmit: 5, Not Stub
Auth type: None
Protection
A. The MD5 key ID values are mismatched between R1 and R2.
B. R1 has both family inet and family iso configured on the link toward R2.
C. The IP subnet mask is mismatched between R1 and R2.
D. The interface type is mismatched between R1 and R2.
Answer: D

…go to http://www.lead2pass.com/jn0-694.html to download the full version Q&As.