Refer to the exhibit.

You are a wireless specialist and have been called to inspect an existing wireless network that offers voice services. High channel utilization on 2.4 GHz has been reported. How can you solve this problem?

• A. Deselect DTPC, to avoid high channel utilization.
• B. Enable at least five mandatory data rates.
• C. Disable data rates 1, 2, 5.5, 6, and 9 Mb/s; set 11 Mb/s as mandatory; and leave the other higher data rates as supported.
• D. Enable lower data rates 1 and 2, to avoid sticky clients.
• E. Disable higher data rates 36, 48, and 54 Mb/s, which increase channel utilization.

In a bridge-to-bridge setup, the network administrator wants to allow only the root bridge the ability to associate to the non-root bridge. To achieve this goal, the administrator decides to implement a MAC filter. If 0017.dfa6.cdf0 is the MAC address of the root AP (ROOT_AP) and 0017.dfa6.ae13 is the MAC address of the non-root AP (NONROOT_AP), which command set will achieve this goal?

• A. ROOT_AP# configure terminal ROOT_AP(config)# access-list 700 permit 0017.dfa6.cdf0 ROOT_AP(config)# interface Dot11Radio0 ROOT_AP(config-if)# dot11 association mac-list 700
• B. ROOT_AP# configure terminal ROOT_AP(config)# access-list 700 permit 0017.dfa6.cdf0 ROOT_AP(config)# dot11 association mac-list 700
• C. NON-ROOT_AP# configure terminal NON-ROOT_AP(config)# access-list 700 permit 0017.dfa6.cdf0 NON-ROOT_AP(config)# dot11 association mac-list 700
• D. NON-ROOT_AP# configure terminal NON-ROOT_AP(config)# access-list 700 permit 0017.dfa6.ae13 NON-ROOT_AP(config)# dot11 association mac-list 700
• E. NON-ROOT_AP# configure terminal NON-ROOT_AP(config)# access-list 700 permit 0017.dfa6.cdf0 NON-ROOT_AP(config)# dot11 ssid bridge NON-ROOT_AP(config-ssid)# dot11 association mac-list 700

Refer to the exhibit.

A Cisco Wireless IP Phone is unable to seamlessly roam on 2.4 GHz. There are interruptions of several seconds on each roaming. No problems are reported on 5 GHz. A full site survey for voice has been completed on both bands.
Which Cisco WLC feature does this issue involve?

• A. client band select
• B. Aironet information element
• C. coverage-hole detection
• D. client load balancing

To manage the wireless network separately, an IT administrator created several virtual domains on the Cisco WCS. APs and WLCs were assigned to these virtual domains. However, when the IT staff logs into the Cisco WCS, they are assigned to the default root domain. The Cisco WCS login request is authenticated by an external RADIUS server. What needs to be configured next to solve this problem?

• A. The IT administrator needs to add local user accounts in the Cisco WCS.
• B. The IT administrator needs to add the correct attribute in the RADIUS server to assign the administrator to the proper virtual domain.
• C. Users need to manually select the proper virtual domain after logging into the root domain.
• D. The IT administrator needs to configure the user group settings to map users to the proper virtual domain.
• E. The administrator needs to change to TACACS+ authentication because the virtual domain cannot be assigned via RADIUS authentication.

Refer to the exhibit.

You are testing coverage-hole detection in your lab. You are using the default Cisco WLC coverage-hole detection configuration that is shown. You have 14 test clients, all associated to the same AP. You move three of the clients far away from the AP so that they have an RSSI of -85 dBm or lower for 1 minute. To your surprise, you see precoverage-hole alarms, but no coverage-hole alarm is triggered.
Which two scenarios explain this issue? (Choose two.)

• A. The failed clients must be at an RSSI of -80 dBm or lower for at least 90 seconds.
• B. The failed clients must be at an RSSI of -81 dBm or lower for at least 90 seconds.
• C. The number of failed clients is less than 25 percent of the total number of clients that are associated to the AP.
• D. This Cisco WLC is not an RF group leader and so cannot make a coverage-hole decision.
• E. Coverage-hole alarms are generated based on the number and percentage of failed packets from the client, rather than on thresholds.