Cisco 300-110 Practice Exam Questions & Answers

In Cisco's AP controller preference hierarchy, each AP can be configured with a primary, secondary, and tertiary controller designation. The AP will attempt to join controllers in this exact order: primary first, secondary second, and tertiary third. When no controllers from the preference list are available, the AP may fall back to any reachable controller through standard CAPWAP discovery. In this hospital deployment, the service/development controller must be the controller of last resort --- it should only receive AP associations when all other options are exhausted. Configuring the service/dev controller as the tertiary controller in the APs' preference configuration ensures exactly this behavior: APs will attempt the SSO pair (primary) first, then the third production WLC joined via mobility tunnel (secondary), and only then the service/dev controller (tertiary). This prevents development traffic from disrupting production service, and ensures production APs do not inadvertently join the service environment during partial outages. Configuring it as primary (Option A) or secondary (Option C) would allow APs to join the service controller before exhausting production options. AP failover priority (Option D) governs which APs are processed during controller recovery, not the controller preference order during join. Reference: WLSD Study Guide --- AP Controller Preference Configuration, Primary/Secondary/Tertiary WLC Assignment, Hospital WLAN High Availability Design.

Floor loss calculation is a fundamental skill in multi-floor wireless site survey methodology. The floor attenuation value represents the signal power reduction caused by penetrating through a single floor structure including the floor decking, subfloor, ceiling material, plenum space, and any structural elements. In this measurement scenario, the engineer has two data points: -45 dBm measured at the ground level of the floor containing the access point (the signal level just below the AP's floor) and -50 dBm measured at the ceiling level of the floor below (the signal level just after passing through the floor structure). The floor loss is simply the difference between these two measurements: (-45 dBm) - (-50 dBm) = -45 + 50 = 5 dB. The result is expressed as a positive value (5 dB) representing attenuation --- signal power decreases by 5 dB when passing through the floor. Expressing it as -5 dB (Option B) would incorrectly imply a signal gain. The 95 dB values (Options A and D) result from incorrectly adding rather than subtracting the dBm values --- a common error when working with negative dBm figures. This floor attenuation value (5 dB) would then be entered into Ekahau's floor material properties to improve predictive model accuracy. Reference: WLSD Study Guide --- Multi-Floor Signal Propagation, Floor Attenuation Factor (FAF), Ekahau Floor Loss Measurement Methodology.

VoWLAN handoff quality is fundamentally determined by the AP placement strategy relative to the direction of user movement. When a user is in motion carrying an active voice call, the roaming event must occur before signal quality degrades below the minimum acceptable VoWLAN threshold (typically -67 dBm for voice, with a minimum SNR of 25 dB). This requires the user to encounter increasing signal strength from a neighboring AP before the current AP's signal drops below the threshold. The optimal AP placement follows the principle of overlapping coverage along the predicted path of travel --- APs must be positioned so that as a user moves, they progressively enter the coverage zone of the next AP while still within adequate range of the current one. Floor plan B represents the correct design where APs are positioned along the travel path with sufficient cell overlap (typically 15-20%) to ensure seamless 802.11r fast BSS transitions. Incorrect floor plans place APs perpendicular to travel direction, at path endpoints only, or with insufficient overlap zones --- all of which create roaming dead zones where the handoff occurs too late, causing voice call disruption. Reference: WLSD Study Guide --- VoWLAN AP Placement, Roaming Design for Moving Users, Cell Overlap and Fast Transition Planning.

The design requirements specify a multi-LAG configuration where each LAG connects to a single switch, different VLANs are assigned to different LAGs, the controller must dynamically learn partner LAG capabilities per port, and standby ports provide redundancy upon active port failure. These requirements collectively point to IEEE 802.3ad LACP (Link Aggregation Control Protocol) as the correct protocol. LACP is the industry-standard IEEE protocol that enables dynamic negotiation of LAG membership between endpoints --- the WLC and each Catalyst 9300 switch exchange LACP PDUs (LACPDUs) to discover port capabilities, negotiate bundle membership, and monitor link status. LACP supports active and passive port states where active ports initiate negotiation and passive ports respond, and it provides the standby port mechanism through its hot-standby capability for link redundancy within the bundle. The requirement to 'learn the identity of partners that can support LAG capabilities' is the defining characteristic of LACP's standardized PDU exchange mechanism. PAgP (Option C) is a Cisco proprietary port aggregation protocol that, while functionally similar, is not the IEEE standard and is incompatible with non-Cisco equipment in mixed environments. OSPF (Option B) and BGP (Option D) are Layer 3 routing protocols entirely unrelated to port channel negotiation. Reference: WLSD Study Guide --- Catalyst 9800 LAG Configuration, LACP IEEE 802.3ad, Multi-LAG High Availability Design.

In a wireless network design where anchor redundancy is required for guest access, setting different priorities for the anchor controllers ensures deterministic primary and backup behavior. Cisco anchor priority uses a lower numerical value to indicate higher preference --- Priority 1 is the highest priority (most preferred) anchor, and Priority 3 is lower priority. Setting Anchor A to priority 1 (Option D) makes it the primary anchor controller --- all new guest client sessions will preferentially anchor to Anchor A. Setting Anchor B to priority 3 makes it the standby anchor --- guest clients will only be anchored to Anchor B when Anchor A is unavailable. This creates a clear primary/backup relationship with deterministic failover. Setting both anchors to the same priority (Options A and C) would result in load balancing between the two anchors rather than active/standby behavior. Option B incorrectly reverses the priorities, making Anchor B the primary and Anchor A the backup. Reference: WLSD Study Guide --- Guest Anchor Redundancy Design, Anchor Priority Configuration, DMZ Anchor WLC Architecture.

After creating a new predictive survey project and importing the floor plan, the next mandatory step is to set the scale of the floor plan. Setting the scale is critical because all subsequent measurements --- AP coverage radius, cell overlap calculations, and distance-based attenuation modeling --- depend on the accuracy of the floor plan's physical dimensions. If the scale is incorrect, the predictive model will place APs at incorrect distances relative to each other and produce inaccurate coverage predictions. The scale is typically set by the engineer clicking on two known points on the floor plan and entering the real-world distance between them, calibrating the software's measurement system. Analyzing the network (Option A) and placing APs (Option C) come after the scale is established. Identifying the coverage area (Option B) is often done simultaneously with scale setting or immediately after. Setting the scale first ensures all subsequent work is based on accurate physical dimensions. Reference: WLSD Study Guide --- Ekahau Predictive Survey Workflow, Floor Plan Import and Scale Setting, Pre-Deployment Survey Methodology.

Cisco's WLAN location and asset tracking architecture (based on Cisco Spaces or legacy Cisco MSE/CMX) relies on the ability to receive and measure the RF signal from tagged assets at multiple APs simultaneously. For accurate location determination using triangulation or trilateration algorithms, a minimum of three APs must receive the tag's signal with sufficient RSSI. Monitor mode APs are dedicated to passive RF listening --- they do not transmit client-serving SSIDs and focus their full radio attention on scanning all channels for signal measurement. Placing monitor mode APs specifically on the perimeter of an asset tracking area provides the spatial diversity and boundary detection capability needed to accurately triangulate assets throughout the interior, without requiring any modifications to the existing data/voice serving APs. Adding monitor mode APs at the perimeter as an overlay ensures the existing 2.4 GHz and 5 GHz voice/data design is entirely undisturbed. Adding local mode APs (Option B) would serve clients and compete for channel capacity. Grouping APs closer (Option C) reduces capacity and increases co-channel interference. Increasing transmit power (Option D) worsens hidden node conditions without improving location accuracy. Reference: WLSD Study Guide --- Cisco Location Services, Monitor Mode APs, Asset Tracking and WLAN Overlay Design.