300-110 Designing Cisco Wireless Networks (300-110 WLSD) v1.2 Questions and Answers

This question requires a straightforward PoE power budget calculation. The IEEE 802.3at standard (PoE+) delivers a maximum of 30W at the Power Sourcing Equipment (PSE/switch port). Cisco 9100 Series access points such as the C9120, C9130, and C9136 are designed to operate with full functionality using PoE+ at 30W per AP. The total PoE power requirement for 12 APs is calculated as: 12 APs × 30W per AP = 360W. This figure represents the total power draw that the Cisco 3800 Series PoE+ switch must be capable of supplying across the connected AP ports simultaneously. The Cisco Catalyst 3800 Series switches offer a total PoE power budget that must be validated against this 360W requirement during the design phase. Note that some Cisco 9100 APs support higher power modes through IEEE 802.3bt (PoE++), which can provide up to 90W — but the question specifies PoE+ (802.3at) for the switch infrastructure, making 30W × 12 = 360W the correct answer. Option D (720W) would correspond to 24 APs at 30W each. Option B (1080W) would represent 36 APs. Option C (184.8W) corresponds to a non-standard per-AP power value. Reference: WLSD Study Guide — PoE Power Budget Planning, Cisco 9100 Series AP Power Requirements, Wired Infrastructure Design for Wireless Deployments.

Receive Start of Packet (RxSOP) is a Cisco proprietary mechanism that defines the minimum received signal threshold at which an access point will acknowledge an 802.11 frame and begin processing it. In a high-density lecture hall environment with 16 APs and directional antennas on a constrained channel plan, rogue APs operating on the same or adjacent channels contribute directly to elevated channel utilization by causing unnecessary medium contention, virtual carrier sensing via NAV, and clear channel assessment deferral. By raising the RxSOP threshold on the legitimate APs, the engineer creates a higher signal floor requirement — only signals above the configured RxSOP level are processed. Signals from distant rogue APs, arriving below this threshold, are silently discarded rather than processed, preventing them from consuming airtime through CCA deferral and NAV mechanisms. Band select (Option A) encourages dual-band clients to move to 5 GHz but does not address rogue interference. 802.11w (Option B) is a management frame protection standard, not an interference mitigation tool. DFS detection (Option D) is for radar avoidance on UNII-2 channels, not rogue AP mitigation. Reference: WLSD Study Guide — High-Density WLAN Design, RxSOP Configuration, Channel Utilization Management.

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.

Raising the minimum data rate to 24 Mbps reduces the effective coverage range of each AP because clients at the cell edge operating at low data rates are effectively excluded from the cell. This shrinks cell size, reducing channel overlap between neighboring APs on the same channel. Using directional antennas limits the coverage area of some APs by focusing RF energy in specific directions rather than radiating omnidirectionally, which directly reduces the lateral overlap between adjacent APs. Increasing AP transmit power (Option B) would worsen overlap, not reduce it. Allowing UNII-2e channels (Option C) provides more channel options but does not reduce the physical cell overlap — it only provides more channels to avoid co-channel interference. Power saving mode (Option E) is a client-side power management feature unrelated to AP cell sizing during a survey. Reference: WLSD Study Guide — Channel Overlap Mitigation, Data Rate Configuration, Directional Antenna Use Cases.

This question requires straightforward wireless capacity engineering calculation. The total throughput requirement is 100 users × 1 Mbps per user = 100 Mbps aggregate. Each channel in the design can support 20 Mbps of usable throughput — this is the per-cell, per-channel allocation defined in the design parameters, representing usable throughput prior to RF overhead as stated in the question. The number of channels required is therefore: total required throughput divided by throughput per channel = 100 Mbps ÷ 20 Mbps per channel = 5 channels. In practice, each channel corresponds to a non-overlapping frequency assignment in the 5 GHz band. With 5 channels and 20 Mbps per channel, the design provides exactly 100 Mbps of aggregate capacity for 100 concurrent users at 1 Mbps each. This calculation methodology is foundational to Cisco ' s high-density WLAN design approach, where the number of spatial streams, channel allocations, and AP placement are all derived from the per-user throughput requirement multiplied by the concurrent user population. Reference: WLSD Study Guide — High-Density WLAN Capacity Planning, Per-User Throughput Calculation, Channel Planning and Spatial Reuse.

The Cisco Aironet 4800 Series Access Point is a tri-radio, high-performance access point designed for high-density environments. It draws significantly more power than older dual-radio APs and requires IEEE 802.3bt (also known as PoE++), which provides up to 90W per port at the Power Sourcing Equipment. IEEE 802.3af (Type 1 PoE) delivers only 15.4W and 802.3at (Type 2 PoE+) provides up to 30W — both are insufficient for full functionality of the 4800 series, which has a dedicated third scanning radio that requires the additional power budget provided by 802.3bt. IEEE 802.3ac is a standard related to VLAN tagging and is entirely unrelated to Power over Ethernet. Engineers designing wired infrastructure for Cisco 4800 deployments must ensure switches support 802.3bt Type 3 or Type 4 to guarantee full AP functionality across all three radios simultaneously. Reference: WLSD Study Guide — Wired Infrastructure Design, PoE Standards and Power Budget Planning, Cisco 4800 Series AP Specifications.

The hidden node problem is a classic RF design flaw that emerges when APs transmit at excessive power levels relative to the attenuation characteristics of the environment. In a brick-walled building, AP signals penetrate walls with significant attenuation. When an AP transmits at maximum power, its signal propagates far beyond the intended cell boundary and reaches client devices that may be physically near other APs but unable to detect the original transmitting AP due to wall attenuation between them. These clients can hear the distant AP ' s signal but cannot hear each other — making them hidden from one another. This leads to simultaneous transmissions, frame collisions at the AP receiver, and dramatic throughput degradation. The 802.11 CSMA/CA mechanism depends on all stations being able to sense the medium before transmitting; hidden nodes defeat this mechanism entirely. The WLSD curriculum consistently identifies excessive AP transmit power in high-attenuation environments as a primary cause of hidden node conditions. The solution is to reduce AP transmit power so that cell sizes remain appropriate for the physical environment. Reference: WLSD Study Guide — RF Design Fundamentals, Hidden Node Problem, Transmit Power and Cell Size Optimization.

When Cisco WLCs are configured to use multicast for mobility group communications, all WLCs participating in the same mobility group must be configured with an identical multicast group IP address. The mobility multicast mode allows a WLC to send a single multicast frame received simultaneously by all other WLCs in the group, rather than sending individual unicast copies to each peer. For this to function correctly, every WLC in the group must join the same IP multicast group address, and the underlying network infrastructure must be configured to support IP multicast routing or IGMP snooping for that specific group address. If any WLC is configured with a different multicast IP address, it will join a different multicast group and will not receive mobility messages from the other WLCs, effectively isolating it from the group ' s communication plane. Service port IP addresses (Option A) are unique per controller. Interface IDs (Option B) are locally significant identifiers. Management IP addresses (Option C) are unique per WLC and identify each peer in unicast configurations. Reference: WLSD Study Guide — Mobility Group Configuration, Multicast Mobility Messaging, WLC Peer Communication.

When configuring high availability on a Cisco access point, the AP can be configured with a maximum of three controllers: a primary controller, a secondary controller, and a tertiary controller. This three-tier hierarchy defines the failover order — the AP first attempts to join its primary controller, then the secondary if the primary is unavailable, and finally the tertiary if both the primary and secondary are unreachable. After exhausting all three configured options, the AP enters a discovery process to find any available controller. This three-controller configuration (primary, secondary, tertiary) allows network engineers to implement N+1 redundancy where critical APs can be directed to specific backup controllers in a deliberate sequence. Limiting the configuration to only 2 controllers (as stated in Option B which would be incorrect) would reduce redundancy options for environments with geographically distributed controllers requiring specific failover paths. Reference: WLSD Study Guide — AP High Availability Configuration, Primary/Secondary/Tertiary Controller Assignment, AP Failover Design.

When designing a wireless network for any environment, including a historic building with ornate wall coverings and aesthetic constraints, RF coverage must always be considered first when placing access points. RF coverage is the fundamental requirement — without adequate signal strength throughout the space, no other design objective can be met. The engineer must first determine AP locations that provide the required signal strength and coverage to all areas before addressing aesthetics, overlap calculations, or interference mitigation. In a historic building specifically, the ornate wall coverings and dense construction materials may cause unexpected signal attenuation, making it even more important to model RF coverage before committing to AP positions. Once RF coverage requirements are established, aesthetic concerns (Option A) can guide the choice of AP form factor, enclosures, or cabling routes. Cell overlap (Option C) is derived from coverage calculations. RF interference (Option D) analysis follows after RF coverage baseline is established. Reference: WLSD Study Guide — Site Survey Methodology, AP Placement Priority, Special Environment Wireless Design.

In the Cisco Catalyst 9800 IOS XE WLC configuration framework, the site tag serves as the primary organizational and functional grouping element for FlexConnect APs at a given physical location. The site tag defines the FlexConnect site — a logical boundary within which APs can perform local switching and local inter-AP roaming without requiring CAPWAP tunnel traversal to the WLC for every client handoff. Within a FlexConnect site defined by the site tag, APs can exchange client roaming context information directly with each other (peer-to-peer), enabling fast Layer 2 roaming for clients moving between APs that share the same site tag — effectively defining the roaming domain for FlexConnect APs at that site. The site tag also references the flex profile (which defines VLAN mappings, local auth settings, and split tunneling parameters) and the AP join profile. Switch port configuration (Option A) is performed on the infrastructure switches, not through the WLC site tag. IP address assignment (Option B) is a DHCP function. Firewall policies (Option C) are applied through ACLs and policy tags, not site tags. Reference: WLSD Study Guide — Catalyst 9800 Tag Architecture, FlexConnect Site Tag Role, Local Roaming in FlexConnect Deployments.

Link Aggregation Group (LAG) is the correct design approach for a single Cisco 9800-40 WLC that requires high availability between the WLC and the core switch in the event of a cable failure. LAG combines multiple physical ports on the WLC into a single logical channel, providing both redundancy (traffic automatically redistributes across remaining links when one fails) and load balancing (traffic is distributed across all active links). Importantly, LAG operates transparently to AP management — APs see a single logical uplink regardless of which physical port their traffic traverses. With a single WLC, Multi-LAG (Option B) is not applicable — Multi-LAG is a feature of the Catalyst 9800 that allows multiple separate LAG bundles for different network connections, typically used with SSO pairs. LACP (Option C) is the protocol used to negotiate LAG member links — it is the mechanism within LAG, not an independent design approach. PAgP (Option D) is a Cisco proprietary alternative to LACP for port aggregation but the question asks for the design approach, which is LAG. Reference: WLSD Study Guide — Catalyst 9800 LAG Design, Port Redundancy and Load Balancing, Single-Controller High Availability.

In a mixed deployment where a Cisco Catalyst 9800 IOS XE WLC operating in SSO is required to establish a mobility peer relationship with a legacy AireOS WLC, the critical configuration requirement is that the 9800 SSO pair presents a single, consistent mobility MAC address to all peer WLCs. When the 9800 is in SSO mode, the active and standby controllers function as a single logical entity, but AireOS WLCs identify mobility peers by MAC address. If the MAC address changes during an SSO switchover, the AireOS peer will detect the change and tear down the mobility tunnel, disrupting inter-controller client roaming. The command ' wireless mobility mac-address < MAC > ' configures a static, persistent mobility MAC address on the 9800 SSO pair that remains constant regardless of which physical unit is active. This ensures the AireOS WLC always identifies the 9800 pair by the same MAC address, maintaining the mobility tunnel and enabling seamless client roaming. Option A configures the HA interface for SSO synchronization but not for AireOS mobility interoperability. Option B sets a default gateway. Option D enables management gateway failover, unrelated to mobility peer identification. Reference: WLSD Study Guide — IOS XE WLC SSO Configuration, AireOS to 9800 Migration, Mobility Peer MAC Address Management.

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.

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.

RF Profiles are a Cisco WLC configuration construct that allows administrators to define a customized set of Radio Resource Management (RRM) parameters and apply them to a subset of APs operating in a specific environment or coverage zone. Within a university high-density deployment — where a lecture hall, outdoor quad, cafeteria, and library may each require fundamentally different RF settings — RF Profiles enable differentiation without globally modifying all RRM parameters. An RF Profile can define custom values for: minimum mandatory data rates, maximum transmit power, minimum transmit power, channel width (20/40/80 MHz), RxSOP thresholds, client load balancing parameters, and coverage hole detection sensitivity. This allows the engineer to apply aggressive interference mitigation settings to high-density assembly areas while maintaining full-coverage settings for perimeter zones. AP Groups (Option A) assign WLANs and interface mappings to subsets of APs but do not directly control RF parameters. RF Groups (Option B) are automatically formed by RRM and represent a cluster of APs coordinating channel and power assignment. AP Profiles (Option C) define AP behavior parameters such as NTP and SSH settings, not RF optimization parameters. Reference: WLSD Study Guide — RF Profile Configuration, High-Density WLAN Design, RRM Parameter Customization.

The issue described indicates that there are more critical priority access points than the backup Cisco WLC can accommodate with its available AP licenses. The backup WLC has only 10 licenses available, but 7 APs are set to critical failover priority and 5 to high failover priority — a total of 12 APs attempting to join. Even though critical priority APs are processed before high priority APs, the backup WLC can only accept 10 APs total (its license limit). Since there are 7 critical priority APs and only 10 total licenses, all 7 critical APs will fail over successfully — but if the scenario involves additional critical APs beyond the license limit, the excess will not be able to join. The oversubscription of the critical priority AP count relative to available backup WLC capacity is the root cause. AP failover priority being disabled (Option D) would mean all APs have equal priority, not that critical APs fail to join. ' network ap-priority set to enable ' (Option B) enables the priority processing globally, which would be required for the feature to work at all. Reference: WLSD Study Guide — AP Failover Priority, N+1 Redundancy License Planning, WLC License Capacity Management.

When using Metageek Chanalyzer in conjunction with a Cisco CleanAir-capable AP for Layer 1 spectrum analysis, the AP must be configured in SE-Connect mode (Spectrum Expert Connect). SE-Connect mode enables the AP ' s CleanAir radio to operate as a dedicated spectrum analyzer, feeding raw spectrum data to the connected Chanalyzer software for visualization and analysis. In this mode, the AP does not serve any Wi-Fi clients and instead focuses all radio resources on spectrum scanning. Metageek Chanalyzer uses the SE-Connect mode specifically to receive the CleanAir ASIC ' s spectrum analysis data. Local mode (Option A) serves clients normally, only providing periodic CleanAir reports. Sniffer mode (Option B) captures 802.11 frames for protocol analysis and does not provide raw spectrum data to Chanalyzer. Monitor mode (Option C) performs WIDS scanning and RRM measurements but does not support the direct Chanalyzer integration. SE-Connect is the specific mode that enables external spectrum analysis software to use the CleanAir ASIC ' s spectrum data in real time. Reference: WLSD Study Guide — Cisco CleanAir Technology, AP Operating Modes, SE-Connect Mode for Spectrum Analysis.

This community bank design scenario requires precise alignment of EWC deployment scale, AAA integration, and traffic routing decisions with the stated constraints. With four APs per campus and a goal of local traffic handling, converting a single C9120 to EWC mode is optimal — converting two APs to EWC (Options B and C) on a four-AP campus wastes 50% of campus AP infrastructure for controller functions rather than client service. The single EWC AP serves as the active local controller for the remaining three client-serving APs. The HQ WLC set as N+1 backup ensures that if the branch EWC fails, the remaining APs fall back to the centralized controller. For the guest WLAN, local web authentication on the guest VLAN provides the locally routed guest access requirement without requiring WAN connectivity to HQ. For the employee WLAN, adding the HQ ISE AAA server to the EWC ' s RADIUS configuration enables 802.1x PEAP authentication to traverse the WAN to ISE at the time of client association. Once authenticated, traffic is locally switched — satisfying both the central authentication and local traffic routing requirements simultaneously. Option D ' s use of guest anchor for the employee WLAN is architecturally incorrect and would route traffic through HQ rather than locally. Reference: WLSD Study Guide — EWC Design, N+1 Redundancy, AAA Integration for Branch WLANs, Local Web Authentication.

In outdoor wireless deployments, foliage — particularly dense trees — represents the most significant and variable RF obstruction that engineers must account for during site survey and design. Trees are problematic for multiple compounding reasons: the high water content of living tissue causes signal absorption consistent with the principle that water is an effective absorber of 2.4 GHz and 5 GHz RF energy; the irregular branching structure causes multi-path scattering; and foliage density changes seasonally, meaning signal propagation characteristics measured during winter may differ substantially from summer readings when leaves are fully developed. A fully leafed deciduous tree can attenuate a 5 GHz signal by 6–15 dB depending on density and depth. Wind (Option A) causes only momentary mechanical movement of foliage and is not an obstruction itself. Rain (Option B) causes some absorption at higher frequencies but its effect at 2.4 GHz and 5 GHz in typical conditions is marginal compared to foliage. Poles (Option D) are thin structures with minimal RF impact. Outdoor surveys for university campuses must specifically account for tree locations, canopy density, and seasonal variation. Reference: WLSD Study Guide — Outdoor Wireless Design, Environmental RF Attenuation Factors, Outdoor Site Survey Considerations.

IEEE 802.11v BSS Transition Management is the standard that enables the network (via the AP) to actively provide roaming recommendations and suggestions to associated clients. When enabled on a SSID, the AP can send BSS Transition Management Request frames to clients, informing them of preferred target APs ranked by signal quality, load, and channel conditions. Critically, BSS Transition Management is a voluntary mechanism — clients that support 802.11v can act on the AP ' s recommendation, while clients that do not support 802.11v simply ignore the BSS Transition Request frames and continue operating normally. This selective applicability directly satisfies the requirement that non-VoWLAN clients must not be impacted. 802.11k (Option A) enables clients to build neighbor lists through measurement reports — this is a client-initiated process, not an AP-to-client recommendation. CCKM (Option B) is a Cisco proprietary fast roaming mechanism for legacy clients, unrelated to roaming guidance. 802.11r (Option D) accelerates the re-association handshake during roaming but does not provide proactive roaming recommendations. Reference: WLSD Study Guide — VoWLAN Design, 802.11v BSS Transition Management, Roaming Optimization Protocols.

The Cisco Catalyst 9300-48HX is a high-density PoE switch specifically designed for Cisco Catalyst 9100 Series AP deployments. The 48HX variant features 48 Multi-Gigabit PoE ports with IEEE 802.3bt (PoE++) support, providing up to 90W per port. The Cisco 9166 Access Point is a Wi-Fi 6E AP that requires IEEE 802.3bt (PoE++) power to achieve full radio functionality — enabling all three radios including the 6 GHz radio. In a two-switch stack of 48HX units, the total PoE budget is designed and rated to support full-port utilization with Cisco 9100 series APs simultaneously. The design intent is to connect APs to all ports on all switches — maximizing the deployment density and ensuring every AP runs with full functionality. Connecting to only half the ports on one switch (Option B), half of each switch (Option C), or all ports on only one switch (Option D) would underutilize the infrastructure and fail to achieve the full deployment density that the switch stack was architected to deliver. The AP naming scheme requiring sequential area numbering requires all APs to be connected and fully operational across the entire stack. Reference: WLSD Study Guide — Catalyst 9300 PoE Infrastructure, 9166 AP Power Requirements, High-Density Wired Infrastructure Design.

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.

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.

A predictive survey (also called a virtual or model-based survey) is the appropriate and only feasible methodology for a facility that does not yet physically exist in its complete form. Since the warehouse has only its foundation and perimeter walls, it is impossible to conduct any form of physical (active or passive) survey of the complete environment. A predictive survey uses architectural floor plans imported into a tool such as Ekahau Site Survey, where the engineer defines attenuation areas representing planned materials and structures: concrete block walls, steel shelving racks, metallic surfaces, and other warehouse-specific obstructions. The software models RF propagation through these defined attenuation values, enabling accurate AP placement planning, antenna selection, and channel planning without physical access to the complete facility. The output is a validated bill of materials with AP counts, models, and associated infrastructure requirements. Passive surveys (Options A and C) require physical APs transmitting RF signals to collect measurement data — impossible in an incomplete building. A hybrid approach mixing passive survey with predictive modeling introduces measurement errors from the incomplete physical state. Reference: WLSD Study Guide — Survey Types, Predictive Survey Methodology, Pre-Deployment Planning for New Construction.