Mobility

Question 1

The use of mobility groups is only beneficial when a deployment comprises of overlapping coverage established by two or more APs that are connected to different WLCs? True/False

Answer 1

True

Question 2

The anchor controller can also be statically configured per WLAN and thus is not always the first controller the client connects to. This functionality is called auto-anchor mobility and can improve load balancing and security. This feature is used a lot with guest networks, where the anchor controller is a controller located in the DMZ? True/False

Answer 2

True

Question 3

In every roaming scenario, mobility messages are exchanged between controllers in the same mobility group or mobility domain? True/False

Answer 3

True

Question 4

Mobile announce is sent when a client first associates with a controller? True/False

Answer 4

True

Question 5

If the client was previously associated with another controller in the mobility group, that controller sends a Mobile Handoff to the new controller.? True/False

Answer 5

True

Question 6

When roaming between different mobility domains, the client must set up a new association, DHCP exchange and authentication? True/False

Answer 6

True

Question 7

A mobility domain can provide seamless roaming for up to 3 mobility groups that contain the max amount of WLCs (24). A mobility domain can thus contain up to 72 WLCs (3 * 24)? True/False

Answer 7

True

Question 8

Mobility groups enable you to limit roaming between different floors, buildings, or campuses in the same enterprise by assigning different mobility group names to different controllers within the same wireless network? True/False

Answer 8

True

Question 9

802.11k allows 11k capable clients to request a neighbor list containing information about known neighbor APs that are candidates for roaming. This list includes the APs’ channels.? True/False

Answer 9

True

Question 10

The use of the 802.11k neighbor list can limit the need for active and passive scanning? True/False

Answer 10

True

Question 11

Ethernet-over-IP (EoIP) tunnels, which uses UDP port 16666 for tunnel control traffic and IP protocol 97 for used data traffic? True/False

Answer 11

True

Question 12

Catalyst 9800 WLCs use encrypted CAPWAP tunnels? True/False

Answer 12

True

Question 13

Mobility messages cannot be exchanged between Catalyst 9800 and AireOS platforms, unless AireOS controller is running version 8.8.111 or later? True/False

Answer 13

True

Question 14

When using mobility features with a firewall, the following ports should be open UDP 16666 for tunnel control traffic and IP protocol 97 for user data traffic? True/False

Answer 14

True

Question 15

Cping is to test mobility of data traffic using CAPWAP? True/False

Answer 15

True

Question 16

Eping is to test mobility data over EoIP? True/False

Answer 16

True

Question 17

Mping is to test mobility control message over UDP port 16666? True/False

Answer 17

True