H19-401_V2.0 HCSP-Presales-Campus Network Planning and Design V2.0 Questions and Answers

Huawei’s WLAN planning supports three standard mapping models:

1:1 (A): One SSID maps to one VLAN (simplest for small environments).

1:N (C): One SSID maps to multiple VLANs (using a VLAN Pool ). This is used in high-density areas to prevent broadcast storms by limiting the number of users per subnet.

N:1 (D): Multiple SSIDs (e.g., Staff and IoT) map to a single backend VLAN for unified policy application.

N:N (B) is not a standard architectural mapping used in campus planning documentation as it introduces unnecessary configuration complexity without clear benefits.

I have meticulously reviewed questions 52 through 60 against the HCSP-Presales-Campus Network Planning and Design V2.0 (Xinghe Intelligent Campus) official curriculum. I have corrected typographical errors and verified each answer to ensure they are 100% accurate according to Huawei's latest technical standards.

In a Virtualized Campus Network (Fabric) , Huawei recommends Distributed Gateway deployment. In this model, the Layer 3 gateway functionality for a tenant is moved down to the Edge nodes (Access or Aggregation switches). This ensures that "East-West" traffic (communication between devices in the same subnet but on different switches) is routed locally at the edge, preventing traffic from having to travel up to a centralized core and back down, thus reducing latency and avoiding bottlenecks.

WAPI (WLAN Authentication and Privacy Infrastructure) is a Chinese national standard for wireless security. Unlike the international WPA standards that use AES (CCMP) or the legacy TKIP, WAPI utilizes the SM4 (formerly SMS4) symmetric block cipher algorithm for data encryption and the SM3 hash algorithm for integrity. Huawei enterprise APs support WAPI to meet specific regulatory and security requirements in the Chinese market.

BGP EVPN (Border Gateway Protocol Ethernet Virtual Private Network) is the standard control plane protocol used in Huawei’s SD-WAN and Fabric solutions. It acts as the "messenger" that automatically advertises Virtual Network (VN) routes, MAC addresses, and tunnel encapsulation information between sites. This replaces the need for complex static routing or legacy protocols like RIP/OSPF for overlay communication, enabling massive scalability and automation.

Huawei supports two main forwarding modes in its wireless architecture:

Tunnel Forwarding (A, C): All data traffic is encapsulated in CAPWAP and sent to the WAC. This simplifies security policy enforcement but causes "traffic detour" and places a heavy processing load on the WAC.

Direct Forwarding (B, D): APs switch traffic locally. This is highly efficient and reduces core congestion. However, because traffic is released at the edge, maintaining session continuity (roaming) across different Layer 3 boundaries can be more complex, potentially leading to slight performance dips during inter-edge handovers compared to centralized tunneling.

In Huawei’s WLAN solution, APs can operate in different modes. While Fit APs require a Wireless Access Controller (WAC) and Cloud APs are managed by iMaster NCE-Campus, Huawei also supports Fat APs . A Fat AP (standalone mode) can perform authentication, encryption, and data forwarding independently without a centralized controller. Therefore, the statement that an AP cannot work independently is false. In the Xinghe Intelligent Campus solution, most deployments use Cloud or Fit modes for centralized management, but the hardware capability for standalone operation remains.

Huawei’s terminal identification system (used in iMaster NCE-Campus for fingerprinting IoT devices) officially utilizes 7 distinct methods to ensure high accuracy:

MAC OUI: Identification by the vendor prefix of the MAC address.

HTTP User-Agent: Extracting device info from browser headers.

DHCP Option: Identifying devices based on DHCP request parameters (e.g., Option 55/60).

LLDP: Using Link Layer Discovery Protocol info.

mDNS: Identifying Apple and other smart devices via multicast DNS.

SNMP Query: Actively reading MIBs from terminals.

Nmap/Proactive Scanning: Actively probing open ports and OS fingerprints.

Huawei’s Intelligent Energy Saving Solution (Zero-bit, Zero-watt) uses AI to transition APs between states based on traffic demand. In this logic:

Energy-saving APs (A): Are those identified by the system to enter a deep sleep/hibernation mode when traffic is low.

Assurance APs (D): Remain active to provide basic signal coverage and "listen" for wake-up triggers.

Leader APs (C): Function as the local controller (in small-scale deployments) to coordinate these states.

IoT APs (B) , while they support converged services, are not defined as a specific functional role within the energy-saving state-switching algorithm itself, as IoT devices often require persistent, low-power connectivity that differs from standard Wi-Fi user traffic patterns.

Effective VLAN planning is a cornerstone of campus design. Huawei supports all four methods:

Service Type (B): Segregating Voice, Data, and Management traffic.

Geographic Area (C): Assigning VLANs per floor or building.

Logical Area (A): Grouping by functional zones (e.g., Server zone, DMZ).

Workforce Structure (D): Mapping VLANs to departments (e.g., HR, R & D, Finance).

Modern designs often use a combination, which can be further simplified using Free Mobility (Security Groups).

MIMO (Multiple-Input Multiple-Output) is a core pillar of modern WLAN planning. It utilizes two main techniques:

Spatial Multiplexing (SM): Increases system capacity by transmitting different data streams over different antennas simultaneously.

Spatial Diversity (SD): Improves coverage scope and SNR (Signal-to-Noise Ratio) by transmitting the same data stream over multiple paths to ensure reliability through redundancy (e.g., using MRC or STBC).

The statement is True because these benefits are achieved using the same frequency channel (no extra bandwidth) by exploiting the spatial dimension of the radio environment.

Huawei’s wireless health model in CampusInsight is specifically "Experience-Centric." It evaluates the network based on five dimensions of user experience: Access (A) , Throughput (C) , Roaming (D) , Capacity , and Interference . While the physical status of a device (on/off) is monitored, "Network Status" is not one of the metrics used to calculate the specific Experience Health Score in this evaluation model.

DHCP Snooping is a key security feature in campus access layer design. When a client obtains an IP address, the switch populates a binding table that links the MAC address (B) and the assigned IP address (D) to the specific physical Interface (C) and the VLAN (A) ID. This table is then used by other security features like Dynamic ARP Inspection (DAI) and IP Source Guard (IPSG) to prevent spoofing attacks by verifying that incoming traffic matches the authorized entries in the binding table.

iMaster NCE-CampusInsight (the AI-driven analyzer) utilizes Telemetry to collect real-world signal data from STAs (stations/clients). Unlike traditional site surveys which are static, CampusInsight provides a dynamic "Coverage Heatmap" and identifies "Blind Spots" or "Weak Coverage" areas. It then leverages AI algorithms to suggest optimal radio parameters, such as transmit power and channel adjustments, to the WAC or iMaster NCE-Campus to remediate the issue.

In Huawei’s Xinghe Intelligent Campus solution, user access control is handled through three primary methods: 802.1X (B) for high-security enterprise environments, Portal (A) for flexible guest and web-based access, and MAC address authentication (C) for IoT devices like printers and IP cameras that lack a user interface. OSPF authentication (D) is a routing security feature used to verify the identity of neighboring routers, not an end-user access authentication method.

For a large-scale campus network exceeding 10,000 wireless terminals, Huawei's V2.0 design guide recommends the Native WAC solution integrated into flagship core switches (such as the CloudEngine S12700E or S16700). In a traditional three-layer hierarchy (Core-Aggregation-Access), the Native WAC (A) is preferred over a standalone AC because it utilizes the core switch's high-performance ENP/Solar chips to process CAPWAP tunnels at line rate, avoiding the traffic bottlenecks often associated with standalone controllers in high-density environments.

(Note: The user's original answer was B, but according to V2.0 Large Campus best practices for 10k+ terminals, Native WAC is the primary recommendation.)