最新なJuniper JN0-694問題集（52題）、真実試験の問題を全部にカバー！

質問 1：
-- Exhibit --
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
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 -> ::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 -> 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 -> 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
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 -> 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?
A. The peer does not support 4-byte AS values.
B. The peer has an incorrect IP address.
C. The peer has an NLRI mismatch.
D. The peer AS is incorrect.
正解：C

質問 2：
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. MF classification
B. RED
C. Rewrite rules
D. BA classification
正解：C

質問 3：
-- Exhibit --
protocols {
bgp {
group isps {
type external;
peer-as 13090194;
multipath multiple-as;
neighbor ;
neighbor ;
}
}
}
-- Exhibit --
Click the Exhibit button.
The exhibit shows the complete BGP configuration for a router. The network operator reports that both peering sessions are up, but the router is not conducting per-flow load balancing over the connections to these two peers.
What are two causes for this behavior? (Choose two.)
A. The router has different IGP metrics to these BGP peers.
B. The forwarding-table export policy is not configured to cause per-flow load balancing.
C. The BGP peers are not sending identical advertisements over the two sessions.
D. The multiple-as parameter causes BGP to only choose multiple paths to different ASs, rather than multiple paths to the same AS.
正解：B,C

質問 4：
The exhibit shows part of the configuration for a router. You receive a complaint that the router is not correctly reclassifying all traffic to the best-effort forwarding class when the amount of IPv4 traffic exceeds 10 Mbps.

You have isolated the problem to traffic with the IP precedence bits set to the binary value
101.
Which configuration is causing this behavior?
A. the filter firewall filter's term 1
B. the policer1 policer
C. the filter firewall filter's term 2
D. the ip_classifier_1 classifier
正解：A

質問 5：
-- Exhibit -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
user@router> show route protocol ospf table inet.0
inet.0: 11133 destinations, 11135 routes (11133 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
224.0.0.5/32 *[OSPF/10] 1w0d 00:01:14, metric 1 MultiRecv -- Exhibit -
Click the Exhibit button.
Referring to the exhibit, why are the OSPF routes missing from the routing table for this router?
A. mismatching OSPF interface type with the neighbor
B. incorrect IP address configured on the interface
C. no Type 4 LSAs in the OSPF database
D. MTU mismatch with the neighbor
正解：A