Online Access Free JN0-643 Practice Test

-- Exhibit --
user@switch> show configuration access
radius_server {
10.1.1.252 {
port 1812;
secret "$9$7gdwgGDkTz6oJz69A1INdb"; ## SECRET-DATA
}
profile radius_server {
authentication-order password;
radius {
authentication-server 10.1.1.252;
}
}
user@switch> show configuration protocols dot1x
authenticator {
ge-0/0/17.0 {
supplicant multiple;
}
}
}
user@switch> show configuration vlans
Sales_VLAN {
vlan-id 123;
}
user@switch> show configuration interfaces ge-0/0/17
unit 0 {
family ethernet-switching {
port-mode access;
}
}
-- Exhibit --
Click the Exhibit button.
You are asked to place employees that are in the sales group into their own VLAN called
Sales_VLAN with a VLAN ID of 123 on port ge-0/0/17. The VLAN must be assigned dynamically. After trying an initial configuration, you see that users in the sales group are not assigned to the Sales_VLAN.
Referring to the exhibit, which two configuration statements are needed on the EX Series switch to resolve this problem? (Choose two.)

• A.set interfaces ge-0/0/17.0 family ethernet-switching vlan members Sales_VLAN
• B.set vlans Sales_VLAN interface ge-0/0/17.0
• C.set access profile radius_server authentication-order radius
• D.set protocols dot1x authenticator authentication-profile-name radius_server

-- Exhibit -

-- Exhibit --
Click the Exhibit button.
In the exhibit, Host2 is the only host currently joining group 231.1.1.1, but S1 is still flooding the traffic to all hosts on VLAN 100.
What feature can be configured on S1 to limit the multicast flooding of traffic to only interested hosts on VLAN 100?

• A.IGMP snooping
• B.Multicast VLAN registration
• C.Multicast scoping
• D.IGMP immediate leave

Which two statements are true about MSDP mesh groups? (Choose two.)

• A.SA messages received from a peer not in any mesh group do not flood to all peers.
• B.The MSDP mesh group was originally designed to limit SA flooding.
• C.SA messages received from a peer not in any mesh group perform a peer-RPF check and, if successful, flood to all peers (except the advertising router).
• D.SA messages received from a mesh group member flood these messages to all peers that are not members of this mesh group.

You notice that a number of IGMP leave group messages are passing through a BMA network and are impacting the network's performance.
What would you do to resolve this issue without affecting multicast traffic?

• A.Suppress group-specific queries.
• B.Apply an import policy to control leave group messages.
• C.Suppress generic IGMP queries.
• D.Enable promiscuous-mode in IGMP.

-- Exhibit --
Mar 16 17:48:06.145257 OSPF periodic xmit from 172.14.10.1 to 224.0.0.5 (IFL 69 area
0 .0.0.1)
Mar 16 17:48:12.404986 ospf_trigger_build_telink_lsas : No peer found
Mar 16 17:48:13.013420 ospf_trigger_build_telink_lsas : No peer found
Mar 16 17:48:13.013555 ospf_set_lsdb_statE. Router LSA 192.168.2.1 adv-rtr 192.168.2.1 state QUIET->GEN_PENDING
Mar 16 17:48:13.013661 OSPF trigger router LSA 0x156d0f0 build for area 0.0.0.1 lsa-id
192.168.2.1
Mar 16 17:48:13.017494 ospf_set_lsdb_statE. Router LSA 192.168.2.1 adv-rtr 192.168.2.1 state GEN_PENDING->QUIET
Mar 16 17:48:13.017636 OSPF built router LSA, area 0.0.0.1, link count 2
Mar 16 17:48:13.017954 OSPF sent Hello 172.14.10.1 -> 224.0.0.5 (ge-0/0/1.0 IFL 69 area
0.0.0.1)
Mar 16 17:48:13.018023 Version 2, length 44, ID 192.168.2.1, area 0.0.0.1
Mar 16 17:48:13.018111 mask 255.255.255.0, hello_ivl 10, opts 0x2, prio 128
Mar 16 17:48:13.018162 dead_ivl 40, DR 172.14.10.1, BDR 0.0.0.0
Mar 16 17:48:13.018613 OSPF DR is 192.168.2.1, BDR is 0.0.0.0
Mar 16 17:48:13.018900 OSPF sent Hello 172.14.10.1 -> 224.0.0.5 (ge-0/0/1.0 IFL 69 area
0.0.0.1)
Mar 16 17:48:13.018968 Version 2, length 44, ID 192.168.2.1, area 0.0.0.1
Mar 16 17:48:13.019032 mask 255.255.255.0, hello_ivl 10, opts 0x2, prio 128
Mar 16 17:48:13.019118 dead_ivl 40, DR 172.14.10.1, BDR 0.0.0.0
Mar 16 17:48:13.028426 OSPF DR is 192.168.2.1, BDR is 0.0.0.0
Mar 16 17:48:13.432025 OSPF packet ignoreD. area mismatch (0.0.0.0) from 172.14.10.2 on intf ge-0/0/1.0 area 0.0.0.1
Mar 16 17:48:13.432135 OSPF rcvd Hello 172.14.10.2 -> 224.0.0.5 (ge-0/0/1.0 IFL 69 area
0.0.0.1)
Mar 16 17:48:13.432189 Version 2, length 44, ID 192.168.5.1, area 0.0.0.0
Mar 16 17:48:13.432274 checksum 0x8065, authtype 0
Mar 16 17:48:13.432346 mask 255.255.255.0, hello_ivl 10, opts 0x2, prio 128
Mar 16 17:48:13.432398 dead_ivl 40, DR 172.14.10.2, BDR 0.0.0.0
commit complete
-- Exhibit --
Click the Exhibit button.
Looking at the traceoptions output in the exhibit, why are the OSPF routers stuck in Init state?

• A.There is a network mask mismatch.
• B.No BDR has been elected.
• C.The routers are in different areas.
• D.There is an MTU mismatch.