Free and Premium Cisco 300-110 Dumps Questions Answers

This WGB (Workgroup Bridge) design scenario requires satisfying multiple simultaneous constraints. EAP-FAST (Flexible Authentication via Secure Tunneling) is the correct authentication protocol because it provides enterprise-grade 802.1X security using protected access credentials (PAC) without requiring a certificate to be installed on each AP or WGB device — directly satisfying the enterprise-grade security without certificates requirement. EAP-TLS (Options B and D) requires client certificates on every authenticating device, which is explicitly excluded. Mobile station mode is required rather than static mode (Options C and D) because mobile station mode enables the WGB to aggressively scan and roam to optimal mesh neighbors dynamically, evaluating neighbor signal quality and switching to better RAPs/MAPs as the truck moves along its path. Static mode fixes the WGB to a specific channel or AP, preventing the aggressive scanning and roaming required for the latency-sensitive application. The dot1q-capable switch connection supports multiple clients in different VLANs via 802.1Q VLAN tagging between the WGB and the truck ' s local network switch. Reference: WLSD Study Guide — Workgroup Bridge Design, EAP-FAST Authentication, Mobile vs. Static WGB Mode, Industrial Wireless Design.

The Cisco Catalyst 9800 IOS XE WLC uses a tag-based configuration architecture. Three primary tag types are used: site tags, policy tags, and RF tags. The site tag associates an AP with its operational context and contains two specific profile references: the AP join profile (defining AP-level parameters such as NTP, syslog, SSH, LED behavior, and CAPWAP timers) and the flex profile (defining FlexConnect-specific parameters including locally switched VLANs, split tunneling, local authentication settings, and VLAN-ACL mappings). The flex profile within the site tag enables the AP to operate in FlexConnect mode with locally configured switching behavior when WLC connectivity is lost. QoS (Option A) policies are applied at the policy tag level within WLAN policies. NAT (Option B) is not a native profile type in the 9800 tag architecture. VLAN (Option D) configurations are defined within the flex profile or policy profile and are not standalone profile types at the tag level. Understanding the three-tag model is essential for designing and troubleshooting 9800-based deployments. Reference: WLSD Study Guide — Catalyst 9800 Configuration Model, Site Tag Architecture, Flex Profile and AP Join Profile.

A pre-site survey questionnaire is used to gather information before the physical survey begins, helping to define design requirements. The two most important information points it should contain are the access point density required and the applications that will run over the wireless network. Access point density (Option C) must be understood early because it depends on the number and types of users in each area, directly influencing the survey approach and AP placement strategy. Applications (Option E) are critical because they define the QoS requirements — a company developing code may run video conferencing, large file transfers, and real-time collaboration tools, each with distinct bandwidth and latency requirements that shape the RF design criteria. The total number of existing APs (Option A) and the current controller model (Option D) are inventory questions, not design requirement inputs. Client device types (Option B) are important but are a subset of the application question — applications drive the specific device capability requirements. Reference: WLSD Study Guide — Pre-Site Survey Requirements Gathering, Customer Questionnaire, Design Requirements Definition.

The eping command is used on Cisco Wireless LAN Controllers to verify that the redundancy peer in a Stateful Switchover (SSO) pair of controllers is up and connected. This command sends ECHO packets (EoIP echo packets) to the peer controller to ensure the data path connectivity is functioning. In an SSO configuration, eping verifies the EoIP tunnel between the active and standby controllers, which is critical for state synchronization and seamless failover. If eping succeeds, it confirms that both the network path and the EoIP data encapsulation between the controllers are functional. The standard ping command (Option B) tests basic IP connectivity but does not validate the EoIP data path used by the SSO redundancy mechanism. The mping command (Option D) tests mobility control path connectivity between mobility group peers, not the SSO redundancy path. The rping command (Option A) is not a standard Cisco WLC command for testing SSO peer connectivity. Reference: WLSD Study Guide — WLC SSO Troubleshooting, eping Command, Redundancy Peer Connectivity Validation.

In a Cisco Catalyst 9800 SSO deployment using Link Aggregation Group (LAG) for network interface redundancy, the SSO pair — WLC1 (active) and WLC2 (standby) — must both have their physical interfaces connected to the network infrastructure as part of the LAG bundle. LAG on the 9800 in an SSO configuration is implemented as a multi-chassis LAG across both the active and standby controllers. This means both WLC1 and WLC2 contribute physical member links to the port channel, and the connected switches must have LACP or PAgP bundle members from both controllers in the same port channel group. When an SSO failover occurs — WLC1 fails and WLC2 takes over as active — the LAG remains operational because WLC2 ' s physical links are already established members of the bundle and continue forwarding traffic without any link renegotiation. If only WLC1 had LAG connectivity and WLC2 had independent links, an SSO failover would cause a LAG topology change requiring re-convergence, introducing downtime. WLC3 is a separate N+1 backup controller joined via a mobility tunnel — not part of the SSO pair and its LAG configuration is independent. Reference: WLSD Study Guide — Catalyst 9800 SSO with LAG, Multi-Chassis Link Aggregation, High Availability Network Redundancy Design.

For a network supporting both data and voice over wireless, two key Cisco design recommendations apply. First, the 5 GHz radio band is recommended for voice over wireless due to its wider channel bandwidths, allowing for higher data rates and better quality of service for latency-sensitive applications. 40 MHz channels in the 5 GHz band provide significantly higher throughput than 20 MHz channels in 2.4 GHz, making Option B correct for the bandwidth reason stated. Second, setting the cell boundary to -67 dBm ensures sufficient signal strength for reliable voice communication at the cell edge, which is the Cisco standard threshold for VoWLAN coverage. Options C and E are partially correct (24 non-overlapping channels is accurate, 15-20% overlap is standard) but B and D are the primary Cisco recommendations that define the design targets for a predictive survey supporting voice. Reference: WLSD Study Guide — VoWLAN Design Requirements, Predictive Survey Design Criteria, 5 GHz Band Selection.

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 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.

VLAN Select is a feature that allows for the dynamic assignment of clients to different VLANs from a pool based on various criteria, such as load balancing or location. In a centralized wireless deployment with N+1 high availability, if clients are receiving IP addresses from a different subnet after failover despite the WLANs being configured with the same dynamic interfaces, the issue is that the second controller ' s WLAN interface mapping resolves to a different VLAN or DHCP scope. VLAN Select ensures that client VLAN assignment is consistent regardless of which controller the client connects to, preventing the subnet change behavior observed during failover. Without VLAN Select, even identically named dynamic interfaces on two WLCs may map to different VLANs if the underlying switch configuration differs. RF Protocol (Option A) controls radio parameters. AP Groups (Option B) control SSID and VLAN assignments per AP cluster. AAA Override (Option D) allows RADIUS servers to assign per-user VLANs, which requires authentication — but these SSIDs use open authentication. Reference: WLSD Study Guide — N+1 High Availability Design, VLAN Select Feature, Consistent Client VLAN Assignment Across Controllers.

Devices that can tolerate at most 100 ms of delay when roaming are voice devices. The 100 ms maximum roaming delay threshold is the Cisco-specified design criterion for VoWLAN implementations — it defines the maximum time a handset can tolerate being disconnected from the wireless network during a roam event before the voice call is degraded or dropped. This threshold drives specific design requirements: 15-20% cell overlap at -67 dBm, fast roaming mechanisms (802.11r, CCKM, or OKC), and AP placement along user movement paths. Location services (Option A) have flexible latency requirements. Data applications (Option B) can tolerate much higher latency — typically several hundred milliseconds. Video (Option C) streaming has buffering mechanisms that allow for higher latency tolerance than real-time voice. Only voice applications have the strict 100 ms roaming delay requirement that directly influences the predictive design criteria. Reference: WLSD Study Guide — VoWLAN Roaming Design, Roaming Delay Requirements, Predictive Survey Criteria.

In a warehouse setting, two elements with a significant negative effect on wireless performance are AP height and absorption. AP height (Option B) is critical because warehouses often have very high ceilings (25-45 feet). When APs with internal (omnidirectional) antennas are mounted too high, the signal propagates primarily in the horizontal plane and the path loss to floor-level worker devices becomes excessive. Additionally, metal shelving between the AP and users further attenuates the already weak signal at high mounting heights. Absorption (Option E) is a major challenge in warehouses because the inventory stored on metal racks, particularly liquid goods, dry goods in cardboard, and dense materials, absorbs RF energy significantly. Metal racking causes both absorption and reflection, creating RF shadows and multipath environments that degrade connection quality. Wireless channels (Option A) are a design parameter, not an environmental impediment. Client authentication (Option C) and authorization (Option D) are network security processes unrelated to RF propagation quality. Reference: WLSD Study Guide — Warehouse Wireless Design, AP Height Considerations, RF Absorption in Industrial Environments.

For APs to be able to fail over between a primary SSO pair in one data center and a standalone WLC in a remote data center connected via WAN with firewalls, two design requirements must be met. First, a mobility tunnel must be created between the wireless controllers (Option A). The mobility tunnel enables the controllers to exchange mobility control messages, peer information, and eventually AP context when failover occurs. Without the mobility tunnel, the remote WLC is not recognized as a valid failover target by the APs through the mobility domain. Second, UDP ports 16666 and 16667 must be open through the firewalls between the controllers (Option D). UDP port 16666 is used for mobility control traffic and UDP port 16667 is used for mobility data traffic — both must be permitted through the firewalls at both data centers for the mobility tunnel to establish and function. HTTPS port 443 (Option B) is used for web management and API communication, not for mobility tunneling. A static RF group leader (Option C) is a RRM configuration unrelated to AP failover capability. Creating a mobility group with the same names (Option E) is a component of the configuration but alone is insufficient without the mobility tunnel and open firewall ports. Reference: WLSD Study Guide — Inter-Site WLC Failover Design, Mobility Tunnel Requirements, Firewall Port Planning for WAN-Separated Controllers.

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.

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.

When eping (EoIP ping) fails between two Cisco Wireless LAN Controllers, it indicates that the data path of the mobility tunnel is blocked. In Cisco AireOS wireless networks, the mobility data path uses IP Protocol 97 (EtherIP — Ethernet-over-IP encapsulation) for tunneling client traffic between the anchor and foreign controllers. This is distinct from the control path, which uses UDP port 16666. When the mobility data path (IP Protocol 97) is blocked by a firewall or ACL between the two controllers ' networks, eping will fail because eping specifically tests the EoIP data encapsulation path. After a power cut, when clients disconnect and attempt to roam between APs on different controllers, the mobility tunnel must be operational for session continuity. If IP Protocol 97 is blocked, the mobility data plane cannot function, causing client disconnections during inter-controller roaming events. The other IP protocols listed (67, 77, 87) are not used for Cisco WLC mobility tunneling. Reference: WLSD Study Guide — Mobility Tunnel Data Path, IP Protocol 97 (EtherIP), eping Command and Troubleshooting.

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.

In Cisco ' s guest anchor WLC deployment model, multiple anchor controllers can be configured in a DMZ to provide redundancy for guest WLAN traffic. The anchor priority value determines which anchor controller is preferred for establishing the guest mobility tunnel from the foreign WLC. Cisco ' s anchor priority system assigns the highest preference to the lowest numerical priority value. Priority 1 is the highest priority, meaning the foreign WLC will prefer Anchor1 when establishing the CAPWAP mobility tunnel for anchoring guest client traffic. Priority 2 would be assigned to Anchor2, and Priority 3 to Anchor3, creating a deterministic failover hierarchy. If Anchor1 becomes unreachable, the foreign controller automatically falls over to Anchor2, then to Anchor3. Priority 0 is not a valid anchor priority value in the Cisco WLC configuration. This design pattern is critical for enterprise guest deployments where DMZ anchor redundancy must be maintained without manual intervention. Reference: WLSD Study Guide — Guest Wireless Architecture, Anchor WLC Configuration, Mobility and DMZ Design.

In an anchored WLAN deployment, client traffic is encapsulated within CAPWAP mobility tunnels between the foreign WLC (where the AP joins) and the anchor WLC (in the DMZ or designated network segment). This tunneling adds encapsulation overhead — CAPWAP/mobility tunnel headers consume a portion of the available MTU on the transport path. When video streaming clients generate large TCP segments, these segments may exceed the effective MTU of the mobility tunnel path, causing IP fragmentation at the WLC or along the path to the anchor. Fragmentation significantly degrades throughput and increases CPU overhead for high-volume video traffic. The correct solution is TCP MSS Clamping — reducing the Maximum Segment Size value advertised in TCP SYN packets so that TCP endpoints negotiate a segment size remaining below the fragmentation threshold. The Cisco 9800 WLC supports TCP MSS adjustment, which intercepts TCP handshake packets and rewrites the MSS option to a value accounting for CAPWAP tunnel overhead. Setting matching MTUs (Option A) does not prevent fragmentation if the effective tunnel MTU is lower than the client segment size. Increasing the MTU (Option B) is often constrained by physical infrastructure. Setting the DF bit (Option D) would cause packets to be dropped rather than fragmented. Reference: WLSD Study Guide — Anchored WLAN Design, CAPWAP Mobility Tunnel MTU, TCP MSS Clamping.

When designing a wireless network to support diverse services — including data, voice, video, and location tracking — across a distributed enterprise with a main office and 10 branch locations, the two primary design factors directly shaping the RF and capacity architecture are the number of wireless devices requiring access and the type of site where the survey will be performed. The device count (Option B) drives AP density, channel reuse planning, capacity modeling, and controller licensing requirements. Each service type — particularly VoWLAN and video — imposes strict per-client throughput and latency constraints that must be multiplied across the concurrent device population. The type of site (Option C) determines the survey approach, attenuation characteristics, coverage requirements, and antenna selection. A warehouse, hospital, or open-plan office each demands a fundamentally different RF design. Options A and D are organizational considerations, not technical RF design inputs. Option E (power sockets) is an installation logistics concern, not a wireless design factor. Reference: WLSD Study Guide — Requirements Gathering, Site Survey Planning, Capacity and Coverage Design Methodology.

To optimize roaming in a wireless network with multiple controllers, it is essential to use the same WLAN name (SSID) across all controllers. When SSIDs differ between controllers, clients perceive them as different networks and must perform a full re-association and re-authentication when roaming between APs managed by different controllers. This causes a roaming disruption equivalent to connecting to an entirely new network. By using identical SSID names on both controllers, clients can seamlessly roam between APs on different controllers within the same mobility group — the controllers exchange client state information via the mobility tunnel, enabling seamless handoff. In the scenario described, ' Copr-NET390595865WLC-1 ' and ' Copr-NET6837l638WLC-2 ' are different SSIDs, meaning clients cannot roam transparently between them. Making both controllers broadcast the same SSID name (and using a mobility group to connect the controllers) resolves this. Reference: WLSD Study Guide — SSID Consistency Across Controllers, Inter-Controller Roaming, Mobility Group Configuration.

Cisco ' s mobility group architecture enables seamless client roaming between WLCs by establishing a trusted peer relationship and shared mobility domain. When two Cisco Catalyst 9800-80 WLCs are placed in the same mobility group, they establish CAPWAP mobility tunnels enabling both Layer 2 and Layer 3 roaming with session continuity including IP address preservation. Within the same mobility group, WLCs exchange client state information, allowing 802.11r Fast BSS Transition, 802.11k neighbor reports, and 802.11v BSS Transition Management to function across controller boundaries. No specific primary or secondary roles are assigned within a mobility group — all members are peers with equal standing for roaming purposes, which is precisely what Option D describes. Option A incorrectly implies a hierarchical structure that does not exist in mobility group peer relationships. Option B separating the WLCs into different groups would break inter-building roaming since clients would experience a full re-authentication cycle. Option C imposing an anchor relationship is appropriate only for guest WLANs. Reference: WLSD Study Guide — Mobility Group Architecture, Inter-Controller Roaming, 802.11r/k/v Fast Roaming Design.

To focus the coverage heat map on the desired coverage threshold, the engineer should use the RSSI slider to set the heat map to the desired cutoff filter. This action adjusts the display to show only the signal levels that meet or exceed the specified RSSI value, effectively filtering out weaker signals and highlighting areas with sufficient coverage. In Ekahau and similar survey tools, the RSSI slider provides a dynamic way to set minimum signal thresholds, allowing the engineer to quickly validate whether coverage meets design targets such as -67 dBm for voice or -70 dBm for data. Changing the color scheme (Option A) only modifies the visual representation without filtering data. The RSSI calibration tool (Option B) adjusts how the tool perceives signal levels, not the display filter. Filtering by AP (Option D) would remove APs from the view, potentially hiding coverage gaps. Reference: WLSD Study Guide — Post-Deployment Survey, Ekahau Heat Map Tools, RSSI Coverage Filtering.

Mobility groups are created by configuring each Wireless LAN Controller (WLC) to use the same mobility domain name (mobility group name) and defining each WLC as a peer in the static mobility members list of every other WLC in the group. This bidirectional configuration establishes the trusted peer relationship and enables WLCs to exchange client information, security credentials, and state data for seamless roaming. The same mobility group name on all WLCs creates a shared identity; the static peer list defines which controllers are trusted mobility partners and provides their management IP addresses and MAC addresses for tunnel establishment. Option A is incorrect because members should run compatible (ideally the same) software versions, not different ones. Option B is incorrect — all WLCs in a mobility group must use the same virtual IP address for proper roaming. Option D is incorrect — in an HA SSO pair, the pair presents as a single logical mobility entity, not as two separate peers. Reference: WLSD Study Guide — Mobility Group Configuration, Peer Configuration Requirements, Mobility Domain Architecture.

For a high-density classroom deployment using 5 GHz with channel bonding in groups of two (40 MHz channels), the correct configuration is to set the channel width for 802.11a (5 GHz) to 40 MHz and set the 24 Mbps data rate to Mandatory. Channel bonding refers to combining two adjacent 20 MHz channels into a single 40 MHz channel, doubling the channel width. Since the requirement specifies 5 GHz operation (where high-density design is appropriate), this must be applied to the 802.11a radio profile, not 802.11b (which operates only on 2.4 GHz). Setting 24 Mbps as Mandatory ensures that APs transmit management frames (beacons, probe responses, and other control frames) only at 24 Mbps — this is how the ' only allow APs to send 802.11 management frames at 24 Mbps ' requirement is implemented. Setting it as Supported (Options B and D) would allow the AP to use lower rates for management frames. Options A and D incorrectly target 802.11b, which does not support 40 MHz channels. Reference: WLSD Study Guide — High-Density WLAN Design, 802.11a Channel Configuration, Data Rate and Channel Width Settings.

Flex+Bridge mode is a specialized AP operating mode that combines two distinct Cisco wireless capabilities: FlexConnect (for local switching of client data traffic and central authentication via the WLC) and Bridge/Mesh mode (enabling wireless backhaul when no wired Ethernet uplink is available). In a branch environment without wired backhaul, a standard FlexConnect AP (Option D) cannot operate because FlexConnect still requires an Ethernet connection for its control plane. Bridge mode alone provides mesh backhaul but does not support the local switching with central authentication model required here. MAP (Option A) is a Mesh Access Point role for wireless backhaul, and RAP (Option C) is a Root Access Point with a wired connection — neither meets the no-wired-backhaul requirement with local switching. Flex+Bridge uniquely satisfies both requirements: the Flex component allows locally switched VLANs to be bridged directly to the access layer without traversing the WAN, while the Bridge component enables the AP to use a wireless mesh link for its backhaul uplink. Central authentication is maintained via the CAPWAP control tunnel over the mesh link. Reference: WLSD Study Guide — FlexConnect Design, Mesh Networking, Flex+Bridge Mode Configuration and Use Cases.

In Ekahau Site Survey ' s multi-floor predictive modeling workflow, alignment points are the critical mechanism that allows the software to understand the precise vertical spatial relationship between floors in a multi-story building. Once floor plans are imported with their scale correctly defined, alignment points must be placed on each floor at the same real-world physical location — such as a stairwell corner, elevator shaft, or structural column — so that Ekahau can accurately calculate vertical signal propagation and inter-floor RF bleed. Without alignment points, the software has no spatial reference to determine which area on Floor 2 is directly above a given point on Floor 1, making floor-to-floor signal bleed calculations geometrically impossible. Drawing coverage areas (Option A) is a post-AP-placement activity. Starting the auto planner (Option B) would attempt to place APs without the required spatial reference. Choosing AP models (Option D) is a subsequent step. Alignment points are a fundamental requirement for any predictive survey involving multi-floor buildings. Reference: WLSD Study Guide — Ekahau Predictive Survey Methodology, Multi-Floor Building Configuration, Signal Propagation Modeling.

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.

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.