Juniper JN0-694 問題集

質問 1：
-- 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 the peer device.
B. BGP graceful restart is not enabled on R1.
C. The restart duration time is not configured on the peer device.
D. The restart duration time is not configured on R1.
正解：B

質問 2：
-- Exhibit -

-- Exhibit --
Click the Exhibit button.
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 dead interval mismatch.
B. There is an MTU mismatch.
C. There is an LSA refresh timer mismatch.
D. There is a hello interval mismatch.
正解：B

質問 3：
Referring to the exhibit, the prefix 3.3.3.3/32 is not in R1 's routing table. Which two configuration changes on R2 would resolve the problem? (Choose two.)


A. Option A
B. Option C
C. Option D
D. Option B
正解：B,D

質問 4：
-- Exhibit - -- Exhibit -

Click the Exhibit button.
On R1, the interface fe-0/0/1 is assigned to the default routing instance and fe-0/0/2 is assigned to a virtual router instance named VR-1.
Referring to the exhibit, the static route 200.200.200.200/32 is missing from the routing table of the default routing instance.
What should you do on R1 to resolve this problem?
A. Create a RIB group to import the direct route 70.1.1.0/24 to both the default instance and the VR-1 instance.
B. Configure an import policy to import the route 200.200.200.200/32 to the VR-1 instance.
C. Configure a static ARP entry for address 70.1.1.1.
D. Change the instance type on VR-1 to forwarding.
正解：A

質問 5：
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.)
A. An OSPF adjacency is flapping.
B. The interface MTU is mismatched between the OSPF neighbors.
C. The wrong authentication keys between the OSPF neighbors are used.
D. There are duplicate router IDs within the OSPF area.
正解：A,D