All About JN0-694 practice test Dec 2016

Our Juniper Juniper exam questions as well as answers are revised as well as verified for many times prior to publishing. All the professionals spare zero efforts for you to provide the buyers with greatest and most up-to-date Juniper JN0-694 training materials. A great number of people get got the admired Juniper certificate. Thus we have total confidence in offer your wonderful success after employing our Juniper JN0-694 exam questions as well as answers. Limited accessibility to our free updated Juniper JN0-694 exam goods within 120 days. Youd much better keep visiting Pass4sure site to download your recently upgraded Juniper JN0-694 study resources. Seek the Juniper JN0-694 study guide for help, or perhaps email us. Your problems will be solved timely.

2016 Dec JN0-694 actual exam

Q1. -- Exhibit– 

-- Exhibit --

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:


Q2. -- Exhibit --user@R1> show bgp neighbor 172.10.3.201 Peer: 172.10.3.201+54714 AS 64512 Local: 172.10.3.202+179 AS 64513 Type: External State: Established Flags: Last State: OpenConfirm Last Event: RecvKeepAlive Last Error: None Export: [ export ] Options: Local Address: 172.10.3.202 Holdtime: 90 Preference: 170 Local AS: 64513 Local System AS: 0 Number of flaps: 0 Peer ID.10.247.194.254 Local ID.10.247.24.6 Active Holdtime: 90 Keepalive Interval: 30 Peer index: 0 BFD.disabled, down Local Interface: ge-0/0/0.500 NLRI for restart configured on peer: inet-unicast NLRI advertised by peer: inet-unicast NLRI for this session: inet-unicast Peer supports Refresh capability (2) Restart time configured on the peer: 120 Stale routes from peer are kept for: 300 Restart time requested by this peer: 120 NLRI that peer supports restart for: inet-unicast NLRI that restart is negotiated for: inet-unicast NLRI of received end-of-rib markers: inet-unicast NLRI of all end-of-rib markers sent: inet-unicast Peer supports 4 byte AS extension (peer-as 64512) Peer does not support Addpath Table inet.0 Bit: 30000 RIB State: BGP restart is complete RIB State: VPN restart is complete Send state: in sync Active prefixes: 7 Received prefixes: 7 Accepted prefixes: 7 Suppressed due to damping: 0 Advertised prefixes: 30 Last traffic (seconds): Received 5 Sent 18 Checked 8 Input messages: Total 40 Updates 3 Refreshes 0 Octets 877 Output messages: Total 55 Updates 13 Refreshes 0 Octets 1764 Output Queue[2]: 0 -- Exhibit --Click the Exhibit button. 

A customer reports that BGP graceful restart is not working on R1. After a Routing Engine failover, R1 did not set the restart state bit in its Open message. The customer provides the BGP neighbor output shown in the exhibit. 

Referring the exhibit, what is causing this problem? 

A. BGP graceful restart is not enabled on R1. 

B. BGP graceful restart is not enabled on the peer device. 

C. The restart duration time is not configured on R1. 

D. The restart duration time is not configured on the peer device. 

Answer:


Q3. An end user on interface ge-0/0/1.0 is trying to receive a multicast stream for 232.0.0.1 sourced from but is not receiving it. You use the show igmp group command and do not see this group in the list. You enable traceoptions for IGMP and find the following IGMPv3 report from the end user's host: 

Jun 10 13:11:03.577641 RCV IGMP V3 Report len 16 from 192.168.1.13 intf ge-0/0/1.0 

Jun 10 13:11:03.577984 Records 1 

Jun 10 13:11:03.578027 Group 232.0.0.1, type IS_EX, aux_len 0, sources 0 

Which configuration change is required to allow the group to be added in the router? 

A. set routing-options multicast ssm-groups 232.0.0.1/32 

B. set routing-options multicast asm-override-ssm 

C. set protocols igmp interface ge-0/0/1.0 promiscuous-mode 

D. set protocols igmp interface ge-0/0/1.0 group-limit 2 

Answer:


Q4. -- Exhibit --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 UTC Protection 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 type: None Topology default (ID 0) -> Cost: 0 -- Exhibit --

Click the Exhibit button. 

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? 

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:


Q5. -- Exhibit --

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 ospf-v2 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) 

-- Exhibit --

Click the Exhibit button. 

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? 

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:


Refresh JN0-694 free question:

Q6. -- Exhibit --policy-options { 

policy-statement accept-static { 

from protocol static; 

then accept; 

-- Exhibit --

Click the Exhibit button. 

The policy shown in the exhibit is deployed on a router and used as the only BGP export policy. The router is sending only one BGP route to its peers. However, when you run the CLI command test policy accept-static 0.0.0.0/0, the policy matches thousands of routes. 

Which statement explains this discrepancy? 

A. All policies have an implicit then accept final term. 

B. The default policy for BGP is to reject all routes. 

C. The default policy for the test policy command is to accept all routes. 

D. The test policy command always shows all routes, regardless of whether they match the policy, when you use the 0.0.0.0/0 argument. 

Answer:


Q7. Two neighboring routers are able to form an OSPF adjacency, but are not able to establish an IBGP neighborship. 

What are two reasons for the IBGP neighborship problem? (Choose two.) 

A. One of the devices has a misconfigured BGP peer address. 

B. One or both of the connected interfaces are missing the family iso statement. 

C. OSPF has a lower route preference than BGP. 

D. A firewall filter on one of the interfaces is blocking TCP traffic. 

Answer: B,C 


Q8. -- Exhibit --{master:0}[edit ethernet-switching-options secure-access-port] 

user@switch# show 

interface ge-0/0/1.0 { 

static-ip 172.27.0.2 vlan v11 mac 00:0c:29:b5:89:7c; 

no-dhcp-trusted; 

vlan v11 { 

arp-inspection; 

interface ge-0/0/2.0 { 

dhcp-trusted; 

user@switch> show log messages | match arp 

Feb 8 14:31:45 switch eswd[1280]: ESWD_DAI_FAILED.3 ARP_REQUEST received, interface ge-0/0/1.0[index 73], vlan v11[index 5], sender ip/mac 172.27.0.2/00:0c:29:b5:89:7d, receiver ip/mac 172.27.0.1/00:00:00:00:00:00 

Feb 8 14:34:05 switch eswd[1280]: ESWD_DAI_FAILED.3 ARP_REQUEST received, interface ge-0/0/1.0[index 73], vlan v11[index 5], sender ip/mac 172.27.0.2/00:0c:29:b5:89:7d, receiver ip/mac 172.27.0.1/00:00:00:00:00:00 

Feb 8 14:36:05 switch eswd[1280]: ESWD_DAI_FAILED.3 ARP_REQUEST received, interface ge-0/0/1.0[index 73], vlan v11[index 5], sender ip/mac 172.27.0.2/00:0c:29:b5:89:7d, receiver ip/mac 172.27.0.1/00:00:00:00:00:00 

-- Exhibit --

Click the Exhibit button. 

You have been asked to troubleshoot a problem where a user is not able to send traffic through your switch. While troubleshooting, you see the log messages shown in the exhibit. 

What is causing the problem? 

A. The eswd process has been corrupted. 

B. The receiver MAC in the packets is undefined. 

C. The defined MAC address is misconfigured. 

D. The static IP address is misconfigured. 

Answer:


Q9. You use static routes for connectivity to the ISP. Your ISP recently switched to using different links for multicast and unicast traffic. Following the change, users in your company were unable to receive multicast traffic through the ISP. 

What must you configure on your router to reestablish multicast connectivity to your ISP? 

A. Add a static default route to the ISP in the inet.2 routing table. 

B. Add the default-rpf-interface parameter under the [edit routing-options multicast] hierarchy. 

C. Add the upstream-interface parameter under the [edit protocols pim] hierarchy. 

D. Disable PIM on the interface used for unicast traffic. 

Answer:


Q10. -- Exhibit– 

-- Exhibit --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:



see more JN0-694 dumps