[Free] Download New Latest (November) Juniper JN0-694 Actual Tests 11-20

Ensurepass

QUESTION 11

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?

 

A.

BA classification

B.

RED

C.

MF classification

D.

Rewrite rules

 

Answer: D

 

 

QUESTION 12  

 

user@router> show route protocol bgp detail

 

inet.0: 20 destinations, 20 routes (19 active, 0 holddown, 1 hidden)

 

10.222.1.3/32 (1 entry, 1 announced)

 

*BGP Preference: 170/-101

 

Next hop type: Indirect

 

Address: 0x15ec944

 

Next-hop reference count: 3

 

Source: 1.1.1.1

 

Next hop type: Router, Next hop index: 536

 

Next hop: 1.1.1.1 via ge-0/0/1.0, selected

 

Protocol next hop: 1.1.1.1

 

Indirect next hop: 14081d0 262142

 

State:

 

Local AS: 65222 Peer AS: 65221

 

 

 

 

Age: 2:12 MetriC.1 Metric2: 0

 

Task: BGP_65221.1.1.1.1+56417

 

Announcement bits (2): 0-KRT 4-Resolve tree 1

 

AS path: 65221 I

 

Communities: no-advertise

 

Accepted

 

Localpref: 100

 

Router ID.10.222.1.1

 

 

Click the Exhibit button.

 

You are troubleshooting a problem where an EBGP route is not being advertised to your local IBGP peers. You have received a 10.222.1.3/32 route from an EBGP peer as shown in the exhibit, but the route is not being advertised.

 

What is causing the problem?

 

A.

The route shows as a hidden route and cannot be advertised.

B.

The next hop for the route is indirect and prevents the route from being advertised.

C.

The community prevents the route from being advertised.

D.

The local preference value is too high for the route to be advertised.

 

Answer: C

 

 

QUESTION 13

 

 

 

 

 

clip_image002

 

 

Click the Exhibit button.

 

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

2. 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?

 

A.

Enable the advertise-inactive parameter for the EBGP peering.

B.

Enable the as-override parameter for the EBGP peering.

C.

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

D.

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

 

Answer: A

 

 

QUESTION 14

 

 

 

 

 

clip_image004

 

 

Click the Exhibit button.

 

You are asked to configure a multihop EBGP peering to a loopback address of your ISP. The peering does not establish, and the ISP has verified that the settings are correct on their side.

 

Referring to the exhibit, what is causing the problem?

 

A.

The peer-as parameter is misconfigured.

B.

The local-address parameter is misconfigured.

C.

The static route is misconfigured.

D.

The neighbor parameter is misconfigured.

 

Answer: C

 

 

QUESTION 15

You recently deployed two Anycast RPs. Multicast clients in the network are reporting that

 

 

 

 

they are receiving traffic from some, but not all, multicast sources.

 

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

 

A.

Configure MSDP between the Anycast RPs.

B.

Configure rp-set for the Anycast RPs.

C.

Configure multicast BGP between the Anycast RPs.

D.

Configure the network to always use the RPT and not switch over to the SPT.

 

Answer: AB

 

 

QUESTION 16

 

clip_image006

 

 

Click the Exhibit button.

 

Your network has two connections to your ISP. You have been asked to load-balance

 

 

 

 

traffic across both links that connect to your ISP. You have enabled multipath for this peer, but you are still not getting the expected load balancing.

 

Given the information shown in the exhibit, what else must you do?

 

A.

Configure and apply a load-balancing policy.

B.

Change the multipath parameter to multihop.

C.

Create a policy to manually change the next hops.

D.

Enable the keep all parameter.

 

Answer: A

 

 

QUESTION 17

 

clip_image008

 

 

Click the Exhibit button.

 

The exhibit shows a small switched network, some details about the MSTP configuration in the network, and the VLANs that are trunked over each link. When Switch2 reboots, users in VLAN 400 on Switch3 report that they lose connectivity to resources in VLAN 400 on Switch4.

 

 

 

 

What is the cause of this problem?

 

A.

There are mismatched bridge priorities.

B.

There is a mismatched MSTP configuration name.

C.

VLAN 400 is not trunked between Switch1 and Switch3.

D.

VLAN 400 is trunked between Switch3 and Switch4.

 

Answer: C

 

 

QUESTION 18  

 

user@switch>show dot1x interface ge-0/0/1 detail

 

ge-0/0/1.0

 

Role: Authenticator

 

Administrative state: Auto

 

Supplicant mode: Multiple

 

Number of retries: 3

 

Quiet perioD.60 seconds

 

Transmit perioD.30 seconds

 

Mac Radius: Enabled

 

Mac Radius Restrict: Enabled

 

Reauthentication: Disabled

 

Configured Reauthentication interval: 3600 seconds

 

Supplicant timeout: 30 seconds

 

Server timeout: 30 seconds

 

Maximum EAPOL requests: 2

 

Guest VLAN member:

 

Number of connected supplicants: 0

 

 

 

  

 

Click the Exhibit button.

 

You are asked to troubleshoot an access control issue on your EX Series switch. The user connecting through port ge-0/0/1 indicates that their 802.1X supplicant is failing authentication and they are not able to connect to the network.

 

Referring to the exhibit, what is causing the 802.1X supplicant to fail?

 

A.

The supplicant mode is defined as multiple.

B.

The MAC restrict option is configured.

C.

The supplicant timeout value is set too low.

D.

The reauthentication interval is set too high.

 

Answer: B

 

 

QUESTION 19  

 

user@router# run show log bgp-test

 

 

Jun 10 23:50:43.056697 BGP SEND 192.168.133.1+179 -> 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
-> ::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 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 -> ::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) subc
ode 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 -> 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 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 -> 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 -> 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 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 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 -> 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

 

 

Click the Exhibit button.

 

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

 

A.

The peer AS is incorrect.

B.

The peer does not support 4-byte AS values.

C.

The peer has an NLRI mismatch.

D.

The peer has an incorrect IP address.

 

Answer: C

 

 

QUESTION 20  

 

user@switch# show vlans

 

ws {

 

vlan-id 23;

 

interface {

 

ge-0/0/12.0;

 

ge-0/0/6.0;

 

}

 

dot1q-tunneling;

 

no-mac-learning;

 

}

 

 

Click the Exhibit button.

 

 

 

 

Referring to the exhibit, an administrator notices that all traffic is flooded out of all the ports in VLAN ws.

 

What would cause this problem?

 

A.

no-mac-learning is enabled on the interface.

B.

Spanning tree is disabled.

C.

dot1q-tunneling is enabled on the VLAN.

D.

Unicast destinations are flooded out of all ports.

 

Answer: A

 

Free Free VCE & PDF File for Juniper JN0-694 Actual Tests

Instant Access to Free VCE Files: CompTIA | VMware | SAP …
Instant Access to Free PDF Files: CompTIA | VMware | SAP …

 

This entry was posted in JN0-694 Actual Tests (November) and tagged , , , , , , . Bookmark the permalink.