300-110 Designing Cisco Wireless Networks Exam Topics and Questions

Wireless Site Survey sets the foundation for everything else on this exam. Get it wrong and every downstream design decision compounds the error. This topic is where candidates discover whether they can translate physical reality into design choices. The exam probes your ability to read a site, interpret RF behaviour in real environments, and match survey methodology to the scenario in front of you.

– Requirements, constraints, and what shapes the design

Before you pick an AP or draw a coverage cell, you need to know what the network has to do and what the building will let you do. Client density drives channel reuse planning and AP placement far more than raw coverage does: a warehouse with a handful of scanners and a hospital ward with hundreds of concurrent voice handsets demand completely different cell sizes and AP counts, even if the floor plans look similar.

Real-time applications such as voice and video set the floor for latency and jitter, which in turn constrains channel width choices and roaming thresholds. Deployment type matters because a location-services deployment demands tighter AP spacing for RSSI accuracy than a pure data deployment does. Security requirements can dictate AP placement near access points to physical spaces, and antenna type drives coverage shape. Knowing which constraint dominates in a given scenario is the skill the exam is testing here.

– RF propagation and material attenuation

Material attenuation is the mechanism that makes or breaks a wireless design. Different construction materials absorb and reflect 2.4 GHz and 5 GHz signals at different rates, and the exam expects you to reason about what happens to signal strength and cell boundaries when RF passes through concrete, glass, drywall, or metal shelving. The practical implication is that two physically identical floor plans in different buildings can require completely different AP placements.

Attenuation also affects your antenna selection. A high-gain directional antenna can punch through a lossy wall, but it narrows the coverage arc and can create dead zones. Omnidirectional antennas spread signal evenly but may not have the gain to overcome heavy attenuation. You need to be able to reason from material to design outcome, not just recall that concrete attenuates more than drywall.

– Survey types and when to use each

The exam distinguishes four survey approaches and expects you to know which one fits which phase of a project. A predictive survey happens before any hardware is installed: you model the environment in a planning tool and produce a heat map based on floor plan dimensions, wall materials, and AP placement assumptions. It is fast and cheap but only as accurate as the inputs.

A pre-deployment survey goes on-site before installation, often using an AP-on-a-stick to measure real propagation. A Layer 1 survey focuses specifically on the RF spectrum: you are looking for non-802.11 interference sources, not coverage. A post-deployment survey validates the live network against design targets. Confusing these phases or mixing up their outputs is a common source of lost marks. The exam also tests your familiarity with tools: Ekahau and Hamina for predictive and active surveys, Chanalyzer and a spectrum analyser for Layer 1 interference hunting. Know what each tool measures and what it cannot tell you.

How Wireless Site Survey is tested

At 25% of the exam, this topic generates a significant share of the items you will face. Expect scenario-driven questions that describe a physical environment, a business requirement, or a specific interference symptom, and ask you to select the appropriate survey type, tool, or design response.

The most common trap is treating survey types as interchangeable. Items reward candidates who can match the phase of the project to the right methodology: a pre-deployment survey does not replace a post-deployment validation, and a spectrum analyser finding does not tell you anything about coverage. A second trap is applying data-network design rules to voice or location deployments. Cell overlap requirements, RSSI thresholds, and AP spacing are all different depending on deployment type, and the exam will present scenarios where the wrong generalisation costs you marks.

Items on planning tools reward knowing what each tool's output represents, not just its name. Candidates who treat Chanalyzer and Ekahau as synonyms for 'wireless software' will find those items unforgiving.

Where the previous topic was about reading the environment, this one is about building the system that lives in it. Wired and Wireless Infrastructure carries the highest weight on the exam, and the breadth is real: physical plant, licensing, radio management, traffic-type design, high-density networks, and mesh bridging all sit here. The cost of a shallow pass through this material shows up across multiple questions, not just one or two.

– Physical and logical infrastructure foundations

Physical infrastructure questions centre on power, cabling, and switch port capacity. PoE budget is the most testable constraint: an AP that requires 802.3at (PoE+) will not operate correctly on an 802.3af port, and a switch with a limited per-port or chassis power budget may force you to rethink AP placement or count. Cabling distance limits and mounting requirements also appear, particularly in outdoor or industrial scenarios where grounding becomes a safety and signal-quality concern.

On the logical side, the exam focuses on WLC and AP licensing tied to the architecture in use. A split-MAC architecture with a centralised WLC has different licensing demands than a distributed or embedded controller model. You need to know which architecture implies which licensing model, because the exam will describe a deployment scenario and ask you to identify the correct infrastructure requirement, not simply recall a definition.

– Radio management and RF design

Radio Resource Management is the mechanism by which a Cisco wireless network adjusts power and channel assignments automatically. The exam expects you to understand RRM well enough to know when it helps and when it needs to be constrained. Cisco Catalyst Center AI-Enhanced RRM extends traditional RRM with machine-learning-driven optimisation, and the exam distinguishes it from classical RRM behaviour.

RF profiles and Radio profiles let you segment RRM behaviour by AP group or physical zone, which matters in mixed-density environments. RxSOP (Receive Start of Packet) is frequently misunderstood: it sets the threshold below which an AP ignores a received signal. Raising RxSOP effectively shrinks the cell, which is useful in high-density designs but can create coverage gaps if set incorrectly. Items on radio management reward knowing the effect of a parameter change on cell size and client behaviour, not just the parameter's name.

– Traffic-type and high-density design

Data, voice, video, and location services each impose different design constraints, and the exam expects you to apply the right set for each. Voice and video require predictable latency, low jitter, and fast roaming, which drives decisions about SSID count, QoS marking, band steering, and call admission control. Location services using Cisco Spaces depend on AP density and placement geometry to achieve the accuracy the business requires.

High-density design compounds these constraints. In a lecture hall or stadium, the dominant problem is co-channel interference and airtime contention, not coverage. The design response involves reducing cell size, using directional antennas, disabling lower data rates, and controlling client association. The exam will present a high-density scenario and reward candidates who reach for interference-management techniques rather than simply adding more APs.

– Wireless bridging and mesh

Mesh and wireless bridging questions test a narrower but specific set of knowledge. You need to know the operating modes available: root AP, mesh AP, and the role each plays in forwarding traffic back to the wired network. Ethernet bridging extends a wired LAN segment over a mesh link, and the exam expects you to know when this is the right tool and what its limitations are.

Workgroup Bridge (WGB) mode allows a wired device to associate to the wireless network through a bridge AP. Roaming behaviour for WGB clients differs from standard client roaming and is a testable detail. Candidates who treat mesh purely as 'wireless APs without cables' miss the forwarding and roaming distinctions that the exam probes.

How Wired and Wireless Infrastructure is tested

At 30%, this is the largest single topic on the exam and the one most likely to determine your result. Items tend to be scenario-based and multi-layered: a question might describe a deployment type, a power constraint, and a client density figure, then ask which design decision follows. Each individual concept is straightforward in isolation; the difficulty is applying several at once.

RRM and RxSOP items are particularly unforgiving because the wrong direction of change (raising versus lowering a threshold) produces opposite outcomes. Items reward candidates who can reason from parameter to RF effect to client impact in sequence. A common mistake is treating RxSOP as a transmit-power control: it is not.

High-density items reward interference-management thinking rather than coverage thinking. Mesh items reward knowing the specific forwarding and roaming rules for each mode. Licensing items reward knowing which architecture drives which requirement. Across all sub-areas, the exam favours candidates who can eliminate plausible-but-wrong options by following the logic of the scenario rather than pattern-matching to a remembered fact.

After designing the physical and logical infrastructure, the next problem is keeping clients connected as they move. Mobility covers how Cisco wireless controllers share client state, hand off sessions, and tunnel traffic across a distributed network. This topic catches candidates who understand static design well but have not worked through what happens the moment a client walks from one AP's cell into another, especially across controller boundaries.

– Mobility groups, roles, and tunnelling

Mobility groups define which controllers can share client context with each other. The exam expects you to design group membership based on the roles controllers play: anchor, foreign, and the traffic paths that result. When a client roams between APs on the same controller, the handoff is local and invisible to the wired network. When the client crosses to a different controller, the mobility tunnel carries the session, and you need to know whether that tunnel is carrying data, control traffic, or both, and what the difference means for the forwarding path.

Anchor controllers deserve particular attention. An anchor holds the client's original IP binding and VLAN assignment even after the client has roamed to a foreign controller. This matters for guest access and for any deployment where consistent IP addressing across roaming events is a business requirement. Items on this area reward candidates who can trace the data path through a multi-controller topology, not just name the roles.

– Client roaming optimisation and Site Tags

Optimising roaming means reducing the time a client spends transitioning between APs to a level the application can tolerate. Voice calls are the hardest constraint: a roaming event that takes too long drops the call. The exam tests the mechanisms available to speed roaming: 802.11r (Fast BSS Transition), 802.11k (neighbour reports), and 802.11v (BSS transition management). Knowing which protocol does which job, and which client types support each, is the level of detail the exam requires.

Site Tags are a Catalyst 9800 construct that groups APs sharing a common policy and RF profile within a site. They affect how mobility behaves locally and how the controller applies configuration to a set of APs. The exam treats Site Tags as a design element: given a topology and a roaming requirement, you need to know how to assign Site Tags to produce the correct behaviour. Candidates who have only seen Site Tags as a configuration step, rather than a design decision, find these items difficult.

How Mobility is tested

Mobility items at 25% tend to be the most topology-dependent questions on the exam. You will be given a diagram or a description of a multi-controller deployment and asked to identify what happens during a specific roaming event, or to select a design that meets a stated roaming performance requirement.

The anchor-foreign distinction is the most frequently tested concept, and the trap is conflating the data path with the control path. Items reward candidates who can describe both paths separately. A second trap is assuming that all fast-roaming protocols are equivalent: 802.11r, 802.11k, and 802.11v each do something distinct, and selecting the wrong one for a voice roaming scenario will cost marks.

Site Tag questions reward design-level thinking. Knowing the CLI to configure a Site Tag is not enough; you need to know the consequence of assigning or not assigning one in a given topology. Candidates who have not worked through multi-controller scenarios end up guessing on these items, which the item design makes expensive.

Mobility handles what happens when clients move. High availability handles what happens when infrastructure fails. At 20%, this topic is the smallest on the exam, but the sub-topics are precise: the exam tests specific HA mechanisms by name and expects you to know the conditions under which each one applies. Candidates who treat HA as a general concept rather than a set of distinct, named features lose marks they could easily have kept.

– Controller redundancy

Link Aggregation Group (LAG) on a controller bonds multiple physical uplinks into a single logical interface, protecting against a single uplink failure. It is a network-availability mechanism, not a controller-redundancy mechanism, and that distinction appears in exam items. Stateful Switchover (SSO) is the controller-level feature: when a primary controller fails, the standby takes over with client sessions intact, avoiding a full re-association storm. The 'stateful' part is the key detail, because a non-stateful failover forces every AP and client to reconnect.

Controller priority determines which unit becomes primary when multiple controllers are eligible. Redundancy relationships, including the anchor role in a guest or roaming topology, interact with priority settings in ways the exam probes. Knowing that an anchor controller failure has different consequences than a foreign controller failure, and how priority and redundancy configuration mitigates each, is the level of depth required.

– AP-level resilience

AP prioritisation controls which APs are served first when a controller restarts and AP join capacity is limited. In a high-density or mixed-criticality deployment, not all APs are equally important, and the exam expects you to know how prioritisation interacts with the join process.

Fall-back configuration assigns each AP a primary, secondary, and tertiary controller. The exam tests the order of preference and what happens when each level is unavailable. This is a straightforward mechanism, but exam items often describe a failure scenario and ask which controller an AP will join, requiring you to follow the preference order correctly under pressure.

Embedded Wireless Controller (EWC) runs the controller function directly on a capable AP, eliminating the external WLC as a single point of failure for small deployments. The exam expects you to know when EWC is the appropriate HA choice and what its operational boundaries are compared to a dedicated controller.

How WLAN High Availability is tested

High availability items are among the most precise on the exam. The sub-topics are narrow and well-defined, which means there is less ambiguity in the items but also less room to reason your way to an answer you have not prepared. Candidates who know the mechanism names but cannot describe their operational effect find these items unforgiving.

SSO items reward knowing what 'stateful' means in practice: client sessions survive the switchover without re-association. Items on LAG reward the ability to distinguish a link-level protection mechanism from a controller-level one. Fall-back items reward correctly following the primary-secondary-tertiary preference order through a described failure sequence.

EWC items tend to focus on deployment suitability: the exam will describe a site and ask whether EWC is the right HA approach, which requires knowing its capacity and feature constraints. A common mistake is treating EWC as a full replacement for a dedicated controller in all scenarios. Candidates who have worked through HA scenarios, rather than simply reading about them, handle the multi-step failure questions most reliably.