Online Access Free JN0-694 Practice Test

-- 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 multiple-as parameter causes BGP to only choose multiple paths to different ASs, rather than multiple paths to the same AS.
• 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 router has different IGP metrics to these BGP peers.

You are implementing Q-in-Q tunneling on an EX Series switch. You want the tunnel to
support all C-VLANs; however, only some VLANs are able to send traffic across the tunnel. Switch-1 has the following configuration:
[edit vlans]
user@Switch-1# show
v100 {
vlan-id 100;
interface {
ge-0/0/0.10;
ge-0/0/1.20;
}
dot1q-tunneling {
customer-vlans [ ];
}
}
What would solve this problem?

• A.Add family ethernet-switching to the tunnel-side interface on Switch-1.
• B.Remove the customer-vlans statement.
• C.Implement RSTP.
• D.Q-in-Q tunneling will not work in this scenario; use a Layer 2 VPN instead.

You add a multicast source to a network. The source's DR sends register messages to the
RP However, multicast clients are not able to receive traffic from the source. What are two causes of this problem? (Choose two.)

• A.The RP did not receive a PIM join message for the group specified.
• B.The designated router must send a null register message to the RP.
• C.A reject policy is configured on the RP.
• D.A reject policy is configured on the designated router.

-- 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 has an incorrect IP address.
• B.The peer has an NLRI mismatch.
• C.The peer does not support 4-byte AS values.
• D.The peer AS is incorrect.

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.Disable PIM on the interface used for unicast traffic.
• B.Add a static default route to the ISP in the inet.2 routing table.
• C.Add the upstream-interface parameter under the [edit protocols pim] hierarchy.
• D.Add the default-rpf-interface parameter under the [edit routing-options multicast] hierarchy.