Cisco 300-110 Exam Questions

Metal doors cause the most signal attenuation among common building materials due to the fundamental electromagnetic properties of metal. Metal is highly reflective and absorptive of radio frequency signals --- it creates what is effectively a Faraday cage effect around any room or space it encloses. In wireless design attenuation modeling tools such as Ekahau, metal is assigned the highest attenuation value among standard building materials, typically 30+ dB per surface. Cinder block walls (Option A) are dense and provide significant attenuation (10-15 dB) but are not as RF-impenetrable as solid metal. Glass walls (Option C) and office windows (Option D) have relatively low attenuation values (2-4 dB) due to the minimal RF-absorbing properties of glass. When engineers model attenuation materials in predictive survey tools, metal doors and metal-containing structures consistently produce the highest per-surface attenuation values, making them the primary barrier obstacles to plan around. Reference: WLSD Study Guide --- RF Signal Attenuation, Building Material Attenuation Values, Predictive Survey Material Modeling.

Cisco 3800 Series APs support IEEE 802.11ac Wave 2, which can deliver throughput exceeding 1 Gbps. Fast Ethernet switches are limited to 100 Mbps per port, creating a severe bottleneck. The two actions that provide maximum support are replacing with mGig switches (Option A) and replacing with gigabit switches with 10G uplinks (Option B). mGig (Multi-Gigabit Ethernet) switches support 2.5G and 5G speeds over existing CAT 6A cabling, allowing the full throughput of 802.11ac Wave 2 APs to be utilized without replacing the existing cable plant. Gigabit switches with 10G uplinks ensure that the access layer can support 1 Gbps per AP port while providing sufficient uplink capacity. Since the existing cabling is already CAT 6A, which supports 10 Gbps over short distances and 5 Gbps over 100 meters, there is no need to replace the wiring (Option D eliminates). The 100-meter distance limitation (Option C) already applies to standard Ethernet and is met by CAT 6A --- this is not an action but a constraint check. Option E (55 meters) is only relevant for specific 5GBASE-T configurations and doesn't maximize support compared to A and B. Reference: WLSD Study Guide --- mGig Infrastructure, 802.11ac Wave 2 Infrastructure Design, Switch Upgrade Planning.

Cisco WLC AP Failover Priority governs the order in which APs are processed when a WLC recovers and APs begin re-associating. The priority levels are: Critical, High, Medium, and Low. During recovery situations, the WLC will accept and process AP join requests in order of priority --- Critical priority APs are processed first, before all other priority levels. In a deployment where the WLC is located in a remote data center connected via WAN, the join process for all APs is slower due to WAN latency and potential bandwidth constraints. Under these conditions, assigning Critical priority to executive office APs ensures they are at the front of the processing queue and restore service before lower-priority APs. The executive office designation implies business-critical operations requiring the fastest possible wireless restoration --- a requirement that directly maps to the Critical priority level. High priority (Option A) would position the executive APs second in the queue behind any Critical priority APs. Medium (Option B) and Low (Option C) would place them further down the processing order. Reference: WLSD Study Guide --- AP Failover Priority Configuration, N+1 and SSO Redundancy Design, WAN-Linked Controller Deployments.

To test whether mobility control packets can reach between WLC peers in a mobility group (used to validate the anchor controller DMZ setup), two steps are required. First, the mping (mobility ping) command (Option A) is the Cisco WLC CLI tool specifically designed to test mobility control path connectivity between WLC peers. Running mping on both WLCs verifies that mobility control messages (UDP port 16666) can be exchanged bidirectionally. Second, UDP port 16666 must be open between the WLCs (Option C) --- mping uses this port, and if it is blocked by a firewall (which is common when the anchor is in a DMZ), the mobility control path cannot be established. These two steps together --- sending mping packets and confirming the firewall permits UDP 16666 --- validate mobility control plane connectivity. The eping (EoIP ping) command (Option B) tests the data path tunnel, not the control path. IP Protocol 97 (Option D) is for the data plane in legacy mobility mode. Tracert (Option E) traces routing paths but does not validate mobility protocol connectivity. Reference: WLSD Study Guide --- Mobility Group Troubleshooting, mping Command, UDP 16666 Firewall Requirements.

This design scenario requires careful interpretation of the SSO pair function and AP priority semantics. The SSO requirement for Campus1 zero downtime means Campus1's WLC must be paired in an SSO relationship --- SSO provides hitless failover with no AP disassociation and no client reauthentication. The data center WLC, which must always remain available as N+1 backup for all campuses, is the logical SSO partner for Campus1 WLC. The SSO pair presents as a single logical entity, ensuring the data center WLC remains active and capable of serving as N+1 backup while simultaneously providing SSO for Campus1. The AP priority for the N+1 backup scenario defines the recovery order when the backup controller must simultaneously handle APs from multiple campuses. In Cisco WLC AP failover priority, priority 1 is Critical (highest). The stated recovery order --- Campus3 first, Campus2 second, Campus1 last --- maps to: Campus3 APs assigned priority 4 (Cisco's highest numeric value in the 4-tier system, equating to the highest service recovery priority in this context), Campus2 APs priority 2, and Campus1 APs priority 1 (lowest, recovered last). Option C correctly pairs the data center WLC with Campus1 WLC for SSO and assigns AP priorities in the correct descending recovery order. Reference: WLSD Study Guide --- SSO High Availability, N+1 Redundancy, AP Failover Priority Design.