A Juniper documentation is usually a pro documentation system. There are a few quantities of Juniper in lots of professions. A Juniper business provides greatest on-line Juniper exercise program regarding Juniper Accredited with which you can noticeably raise ones That career. The Juniper JN0-694 Accredited exhibits powerful knowledge of the foundation competencies of the supplied job job, which is often used from a student or perhaps basic level.
2021 Sep JN0-694 free practice questions
Q11. -- 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. Configure a static ARP entry for address 70.1.1.1.
B. Change the instance type on VR-1 to forwarding.
C. Create a RIB group to import the direct route 70.1.1.0/24 to both the default instance and the VR-1 instance.
D. Configure an import policy to import the route 200.200.200.200/32 to the VR-1 instance.
Answer: C
Q12. -- Exhibit --user@router# show class-of-service
classifiers {
inet-precedence ipp-test {
import default;
forwarding-class best-effort {
loss-priority low code-points be;
}
forwarding-class expedited-forwarding {
loss-priority low code-points af21;
}
forwarding-class assured-forwarding {
loss-priority low code-points af11;
}
forwarding-class network-control {
loss-priority low code-points nc1;
}
}
}
interfaces {
ge-* {
scheduler-map map-test;
unit * {
classifiers {
inet-precedence ipp-test;
}
rewrite-rules {
inet-precedence ipp-rw-test;
inet-precedence default;
}
}
}
}
...
rewrite-rules {
inet-precedence ipp-rw-test {
forwarding-class best-effort {
loss-priority low code-point be;
loss-priority high code-point af21;
}
forwarding-class expedited-forwarding {
loss-priority high code-point af21;
loss-priority low code-point be;
}
forwarding-class assured-forwarding {
loss-priority low code-point af11;
loss-priority high code-point af11;
}
forwarding-class network-control {
loss-priority low code-point nc1;
loss-priority high code-point nc1;
}
}
}
user@router> show class-of-service
...
Code point type: inet-precedence
Alias Bit pattern
af11 001
af21 010
af31 011 af41 100 be 000 cs6 110 cs7 111 ef 101 nc1 110 nc2 111 -- Exhibit --
Click the Exhibit button.
Traffic with the IP precedence value af21 ingresses the router and should be rewritten with the same value as it egresses; however, this traffic is rewritten to a different value.
Referring to the exhibit, what is the source of this problem?
A. The BA classifier is assigning the traffic to the best-effort queue with a high loss priority.
B. The BA classifier is assigning the traffic to the best-effort queue with a low loss priority.
C. The BA classifier is assigning the traffic to the expedited forwarding queue with a high loss priority.
D. The BA classifier is assigning the traffic to the expedited forwarding queue with a low loss priority.
Answer: D
Q13. 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: A
Q14. 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: A,B
Q15. -- 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: D
Latest JN0-694 download:
Q16. -- Exhibit --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
-- Exhibit --
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
Q17. -- Exhibit --user@R1> show class-of-service interface ge-0/0/0 Physical interface: ge-0/0/0, Index: 134 Queues supporteD.8, Queues in use: 4 Scheduler map: , Index: 2 Congestion-notification: Disabled
Logical interface: ge-0/0/0.0, Index: 69 Object Name Type Index Classifier ipprec-compatibility ip 13 -- Exhibit --
Click the Exhibit button.
You are sending traffic to the ge-0/0/0 interface on R1 with the expedited forwarding (101) IP precedence bits. However, the counters on the router show that it is not processing any traffic in the expedited forwarding queue.
Referring to the exhibit, what is causing the problem?
A. The classifier does not contain a mapping for this precedence value.
B. The classifier is assigning the traffic a high loss priority.
C. The classifier is assigning the traffic to the best-effort forwarding class.
D. The classifier is dropping the traffic.
Answer: C
Q18. -- 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: C
Q19. -- Exhibit --user@switch# show vlans
ws {
vlan-id 23;
interface {
ge-0/0/12.0;
ge-0/0/6.0;
}
dot1q-tunneling;
no-mac-learning;
}
-- Exhibit --
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
Q20. -- 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: A