[Free] 2018(Jan) EnsurePass Testinsides Juniper JN0-694 Dumps with VCE and PDF 11-20

Ensurepass.com : Ensure you pass the IT Exams
2018 Jan Juniper Official New Released JN0-694
100% Free Download! 100% Pass Guaranteed!
http://www.EnsurePass.com/JN0-694.html

Enterprise Routing and Switching Support, Professional (JNCSP- ENT)

Question No: 11

You want to receive routes from a remote EBGP peer as shown in the exhibit. The remote site has the same AS number as your own. You have successfully established the EBGP peering, but are not receiving any routes.

Which BGP group configuration parameter will enable you to receive routes from the remote EBGP peer?

Ensurepass 2018 PDF and VCE

  1. advertise-inactive

  2. multipath

  3. as-override

  4. remove-private

Answer: C

Question No: 12

You have configured OSPF between two routers and the adjacency is not coming up. You confirm that the physical link between them is up and then run the commands shown in the exhibit on both routers.

Which two configuration mistakes apply? (Choose two.)

Ensurepass 2018 PDF and VCE

  1. The hello timer is mismatched.

  2. The subnet is mismatched.

  3. The DR ID is mismatched.

  4. The area ID is mismatched.

Answer: A,D

Question No: 13

– Exhibit –

Ensurepass 2018 PDF and VCE

– Exhibit –

Click the Exhibit button.

You are asked to assist with a problem with a new EBGP peering between Site 1 and Site

  1. Referring to the exhibit, Site 1 is not receiving the 100.100.0.0/16 routes from Site 2. Which action will resolve the problem?

    1. Enable the advertise-inactive parameter for the EBGP peering.

    2. Enable the as-override parameter for the EBGP peering.

    3. Create an export policy to export the IBGP routes over the EBGP peering.

    4. Create a next-hop-self policy and apply it as an export policy to the EBGP peering.

Answer: A

Question No: 14

– Exhibit –

policy-statement test_route_filter {

term 1 { from {

route-filter 192.168.0.0/16 longer; route-filter 192.168.1.0/24 longer { metric 5;

accept;

}

route-filter 192.168.0.0/8 orlonger accept;

}

then { metric 10; accept;

}

}

term 2 { then { metric 20; accept;

}

}

}

– Exhibit –

Click the Exhibit button.

Given test route 192.168.1.0/24 and the configuration shown in the exhibit, what is the expected result?

  1. accepted with metric of 5

  2. accepted with metric of 10

  3. accepted with metric of 20

  4. rejected

Answer: C

Question No: 15

Your Junos device is dropping certain traffic flows, while allowing other traffic flows to pass through the device unaffected.

Which CoS component is causing this problem?

  1. BA classification

  2. RED

  3. MF classification

  4. Rewrite rules

Answer: D

Question No: 16

You observe that a router is using an unusually high amount of CPU cycles. You determine that continuous SPF calculations in OSPF are being performed.

What are two reasons for this problem? (Choose two.)

  1. The wrong authentication keys between the OSPF neighbors are used.

  2. The interface MTU is mismatched between the OSPF neighbors.

  3. There are duplicate router IDs within the OSPF area.

  4. An OSPF adjacency is flapping.

Answer: C,D

Question No: 17

– Exhibit –

user@router# run show log bgp-test

Jun 10 23:50:43.056697 BGP SEND 192.168.133.1 179 -gt; 192.168.133.0 64925

Jun 10 23:50:43.056739 BGP SEND message type 3 (Notification) length 23

Jun 10 23:50:43.056760 BGP SEND Notification code 2 (Open Message Error) subcode 7 (unsupported capability)

Jun 10 23:50:43.056781 BGP SEND Data (2 bytes): 00 04

Jun 10 23:50:52.215104 advertising receiving-speaker only capabilty to neighbor

::192.168.133.0 (External AS 300)

Jun 10 23:50:52.215173 bgp_senD. sending 59 bytes to ::192.168.133.0 (External AS 300)

Jun 10 23:50:52.215200

Jun 10 23:50:52.215200 BGP SEND ::192.168.133.1 179 -gt; ::192.168.133.0 57107

Jun 10 23:50:52.215233 BGP SEND message type 1 (Open) length 59

Jun 10 23:50:52.215256 BGP SEND version 4 as 23456 holdtime 90 id 10.200.1.1 parmlen

30

Jun 10 23:50:52.215276 BGP SEND MP capability AFI=2, SAFI=1

Jun 10 23:50:52.215294 BGP SEND Refresh capability, code=128 Jun 10 23:50:52.215312 BGP SEND Refresh capability, code=2

Jun 10 23:50:52.215332 BGP SEND Restart capability, code=64, time=120, flags=

Jun 10 23:50:52.215353 BGP SEND 4 Byte AS-Path capability (65), as_num 2123456789

Jun 10 23:50:52.216018

Jun 10 23:50:52.216018 BGP RECV ::192.168.133.0 57107 -gt; ::192.168.133.1 179

Jun 10 23:50:52.216058 BGP RECV message type 3 (Notification) length 21

Jun 10 23:50:52.216079 BGP RECV Notification code 2 (Open Message Error) subcode 2 (bad peer AS number)

Jun 10 23:51:15.058112 advertising receiving-speaker only capabilty to neighbor 192.168.133.0 (External AS 300)

Jun 10 23:51:15.058192 bgp_senD. sending 59 bytes to 192.168.133.0 (External AS 300)

Jun 10 23:51:15.058217

Jun 10 23:51:15.058217 BGP SEND 192.168.133.1 50083 -gt; 192.168.133.0 179

Jun 10 23:51:15.058250 BGP SEND message type 1 (Open) length 59

Jun 10 23:51:15.058273 BGP SEND version 4 as 65001 holdtime 90 id 10.200.1.1 parmlen

30

Jun 10 23:51:15.058294 BGP SEND MP capability AFI=1, SAFI=128

Jun 10 23:51:15.058312 BGP SEND Refresh capability, code=128 Jun 10 23:51:15.058331 BGP SEND Refresh capability, code=2

Jun 10 23:51:15.058386 BGP SEND Restart capability, code=64, time=120, flags= Jun 10 23:51:15.058416 BGP SEND 4 Byte AS-Path capability (65), as_num 65001

Jun 10 23:51:15.058651 bgp_pp_recv:3140: NOTIFICATION sent to 192.168.133.0

(External AS 300): code 6 (Cease) subcode 7 (Connection collision resolution), Reason: dropping 192.168.133.0 (External AS 300), connection collision prefers 192.168.133.0 53170 (proto)

Jun 10 23:51:15.058680 bgp_senD. sending 21 bytes to 192.168.133.0 (External AS 300)

Jun 10 23:51:15.058702

Jun 10 23:51:15.058702 BGP SEND 192.168.133.1 50083 -gt; 192.168.133.0 179

Jun 10 23:51:15.058735 BGP SEND message type 3 (Notification) length 21

Jun 10 23:51:15.058755 BGP SEND Notification code 6 (Cease) subcode 7 (Connection collision resolution)

Jun 10 23:51:15.059557 advertising receiving-speaker only capabilty to neighbor 192.168.133.0 (External AS 300)

Jun 10 23:51:15.059594 bgp_senD. sending 59 bytes to 192.168.133.0 (External AS 300)

Jun 10 23:51:15.059617

Jun 10 23:51:15.059617 BGP SEND 192.168.133.1 179 -gt; 192.168.133.0 53170

Jun 10 23:51:15.059649 BGP SEND message type 1 (Open) length 59

Jun 10 23:51:15.059671 BGP SEND version 4 as 65001 holdtime 90 id 10.200.1.1 parmlen

30

Jun 10 23:51:15.059691 BGP SEND MP capability AFI=1, SAFI=128

Jun 10 23:51:15.059709 BGP SEND Refresh capability, code=128 Jun 10 23:51:15.059727 BGP SEND Refresh capability, code=2

Jun 10 23:51:15.059747 BGP SEND Restart capability, code=64, time=120, flags= Jun 10 23:51:15.059768 BGP SEND 4 Byte AS-Path capability (65), as_num 65001

Jun 10 23:51:15.060383 bgp_process_caps: mismatch NLRI with 192.168.133.0 (External

AS 300): peer: (1) us: (4)

Jun 10 23:51:15.060445 bgp_process_caps:2578: NOTIFICATION sent to 192.168.133.0 (External AS 300): code 2 (Open Message Error) subcode 7 (unsupported capability) value 4

Jun 10 23:51:15.060470 bgp_senD. sending 23 bytes to 192.168.133.0 (External AS 300)

Jun 10 23:51:15.060492

Jun 10 23:51:15.060492 BGP SEND 192.168.133.1 179 -gt; 192.168.133.0 53170

Jun 10 23:51:15.060556 BGP SEND message type 3 (Notification) length 23

Jun 10 23:51:15.060578 BGP SEND Notification code 2 (Open Message Error) subcode 7 (unsupported capability)

Jun 10 23:51:15.060600 BGP SEND Data (2 bytes): 00 04

– Exhibit –

Click the Exhibit button.

Referring to the exhibit, what is causing the IPv4 BGP peering to stay in an active state?

  1. The peer AS is incorrect.

  2. The peer does not support 4-byte AS values.

  3. The peer has an NLRI mismatch.

  4. The peer has an incorrect IP address.

Answer: C

Question No: 18

You are implementing Q-in-Q tunneling on an EX Series switch. You want the tunnel to support all C-VLANs; however, only some VLANs are able to send traffic across the tunnel. Switch-1 has the following configuration:

[edit vlans] user@Switch-1# show v100 {

vlan-id 100; interface { ge-0/0/0.10; ge-0/0/1.20;

}

dot1q-tunneling { customer-vlans [ ];

}

}

What would solve this problem?

  1. Add family ethernet-switching to the tunnel-side interface on Switch-1.

  2. Implement RSTP.

  3. Q-in-Q tunneling will not work in this scenario; use a Layer 2 VPN instead.

  4. Remove the customer-vlans statement.

Answer: C

Question No: 19

Referring to the exhibit, an administrator notices that the VLAN interface is not coming up. What would cause this problem? Click the Exhibit to see a larger version.

Ensurepass 2018 PDF and VCE

  1. All member interfaces are down.

  2. The unit number for the VLAN is misconfigured.

  3. The subnet mask is incorrect.

  4. All member interfaces are in access mode

Answer: A

Question No: 20

Referring to the exhibit, an administrator has configured dot1q-tunneling on the VLAN, but LLDP is not being tunneled.

Ensurepass 2018 PDF and VCE

What is causing the problem?

  1. LLDP needs to be enabled as a protocol to tunnel.

  2. LLDP can only be processed one hop away.

  3. LLDP needs to be disabled on the tunneling device.

  4. LLDP tunneling only works on trunked interfaces.

Answer: A

100% Ensurepass Free Download!
Download Free Demo:JN0-694 Demo PDF
100% Ensurepass Free Guaranteed!
JN0-694 Dumps

EnsurePass ExamCollection Testking
Lowest Price Guarantee Yes No No
Up-to-Dated Yes No No
Real Questions Yes No No
Explanation Yes No No
PDF VCE Yes No No
Free VCE Simulator Yes No No
Instant Download Yes No No