H19-404_V1.0 HCSE-Presales-Campus Network Planning and Design V1.0 Questions and Answers

The capabilities introduced with Wi-Fi 7 are 4096-QAM and channel bandwidth of up to 320 MHz. Wi-Fi 7, based on IEEE 802.11be Extremely High Throughput, doubles the maximum channel width available under Wi-Fi 6 and Wi-Fi 6E from 160 MHz to 320 MHz where sufficient regulatory spectrum is available. It also introduces 4096-QAM, encoding 12 bits per modulation symbol compared with 10 bits for Wi-Fi 6’s 1024-QAM. This can increase peak spectral efficiency when the signal-to-noise ratio is sufficiently high.

The other options were available before Wi-Fi 7. Support for up to eight spatial streams existed in earlier IEEE 802.11 generations, and MU-MIMO was already supported before Wi-Fi 7, with major uplink and downlink enhancements delivered by Wi-Fi 6. The 6 GHz band was commercially introduced through Wi-Fi 6E. Huawei’s material specifically describes Wi-Fi 6E as extending Wi-Fi 6 into the 6 GHz spectrum. Wi-Fi 7 continues using 6 GHz but did not introduce it. Therefore, only A and C are correct.

==================

All four options represent objectives of a next-generation advanced industrial network. IP-based connections establish a standardized communications foundation, allowing production systems, controllers, sensors, machines, and management platforms to communicate through scalable Ethernet and IP technologies instead of isolated proprietary field networks.

Networked devices extend connectivity across operational technology assets so that equipment status, production data, and control information can be shared across production lines, plants, data centers, and cloud platforms. Network intelligence introduces automated provisioning, telemetry, analytics, fault prediction, policy optimization, and closed-loop operations. These capabilities reduce manual configuration and improve production availability.

Network-security integration is equally essential because greater openness and interconnection increase the potential attack surface. Security must therefore be integrated into access control, segmentation, device identification, encrypted communication, anomaly detection, and policy enforcement rather than added as an isolated external system. Huawei’s broader CloudCampus architecture similarly emphasizes automated provisioning, intelligent O & M, secure interconnection, integrated wired and wireless management, and open network capabilities. The four objectives collectively create an open, connected, intelligent, and secure industrial communications architecture.

==================

All four statements correctly describe the trade-offs between direct and tunnel forwarding. With direct forwarding, an AP sends service traffic directly to the upstream network rather than encapsulating it in a CAPWAP data tunnel to the WAC. This eliminates unnecessary detours, avoids creating a WAC bandwidth bottleneck, reduces WAC load, and generally provides higher forwarding efficiency.

However, on a fabric network, Layer 3 roaming across different edge nodes may require the original edge or another designated device to remain the home agent. The resulting forwarding path and state synchronization can slightly affect roaming performance, making direct forwarding less suitable for extremely roaming-sensitive deployments. Huawei’s material explains that after Layer 3 roaming in direct-forwarding mode, traffic may continue to be forwarded through the home agent.

Tunnel forwarding sends AP service traffic through CAPWAP tunnels to the WAC. This simplifies centralized policy enforcement, security control, and traffic management. Its disadvantage is that all wireless traffic may detour through the WAC, increasing forwarding pressure and potentially creating a performance bottleneck.

==================

GRE is a multiprotocol encapsulation mechanism and can carry all the listed packet types. It inserts a GRE header around the original payload and then places the resulting GRE packet inside a delivery-protocol packet. Because the GRE header contains a Protocol Type field identifying the encapsulated payload, GRE is not restricted to ordinary IPv4 unicast traffic.

IPv6 packets can be transported as GRE payloads when supported by the tunnel endpoints. IP unicast traffic is the most common use case. GRE can also carry IP multicast and broadcast packets, which is one of its major advantages over basic IPsec tunnel selectors that traditionally focus on IP unicast traffic. This enables routing protocols, multicast applications, discovery traffic, and other non-unicast services to operate across a logical point-to-point tunnel.

RFC 2784 defines GRE as a general mechanism for encapsulating an arbitrary network-layer protocol over another network-layer protocol. It also defines the Protocol Type field used to identify the carried payload. Huawei uses GRE as an SD-WAN overlay data-channel option and can additionally secure it using IPsec when confidentiality and integrity are required.

==================

Huawei SD-WAN provides all four technologies. Per-flow load balancing distributes separate application flows among multiple links that have the same priority and satisfy the required SLA. Per-packet load balancing can transmit packets from one flow across multiple eligible links, improving aggregate bandwidth utilization for large file transfers, backups, and replication.

Multi-fed and selective receiving duplicates critical traffic across different links. The receiving device selects valid packets, removes duplicates, and preserves packet order. Packet loss or failure on one path therefore does not interrupt the service, enabling zero-millisecond link switchover in applicable deployments.

A-FEC dynamically generates redundant packets and adjusts the redundancy ratio according to measured packet loss. The receiving device reconstructs lost packets, reducing video freezing and voice-quality deterioration. Huawei describes both adaptive FEC and multi-fed selective receiving as WAN-optimization mechanisms for key traffic.

Intelligent traffic steering selects links according to application identity, quality, bandwidth, priority, and load. Therefore, A, B, C, and D are all correct.

==================

For the R024C10 software release specified in the question, the AR6700V-L cannot be deployed on Google Cloud Platform. The supported environments represented by this release and question are Amazon Web Services, Oracle Cloud, and Microsoft Azure.

Public-cloud support for a virtual CPE is release-specific. A virtual router requires more than generic virtual-machine compatibility. Huawei must provide or validate the appropriate cloud image, virtual network-interface drivers, deployment template, bootstrap mechanism, licensing integration, resource specifications, and controller-registration process for each cloud platform. Therefore, support for one KVM- or VMware-based environment does not automatically mean that every public-cloud provider is supported.

A cloud-hosted virtual CPE enables branches to establish overlay connectivity directly with cloud workloads and allows the controller to provide unified management and policy orchestration for physical and virtual edge devices. Huawei describes this model as deploying a virtual SD-WAN router on a public cloud to implement branch-to-cloud interconnection and unified policy orchestration. Under the R024C10 compatibility matrix tested by this question, GCP is excluded. Therefore, option B is correct.

==================

The statement is true as a WLAN design recommendation. Inter-WAC roaming is supported, but it introduces more control-plane interaction and forwarding complexity than intra-WAC roaming. The Home WAC and Foreign WAC must belong to the same mobility group, synchronize station and AP information, and establish an inter-WAC CAPWAP tunnel for control information and, in some scenarios, service forwarding.

Additional synchronization, tunnel processing, route handling, and failure dependencies can increase roaming delay and complicate troubleshooting. This is especially relevant for delay-sensitive applications such as voice, video, automated guided vehicles, and real-time production systems. A better design places APs between which users frequently move under the same WAC wherever controller capacity and physical topology permit.

Avoiding inter-WAC roaming does not mean disabling the function entirely. Large campuses may require multiple WACs for scale, redundancy, or geographic distribution. Mobility groups should still be configured for unavoidable cross-controller movement. However, buildings, floors, and continuous roaming areas should be assigned carefully so that normal roaming remains intra-WAC. Therefore, the recommendation in the statement is correct, and the answer is True.

==================

The statement is true. iMaster NCE-Campus supports multiple on-premises deployment combinations rather than being restricted exclusively to Huawei-branded physical servers and Huawei virtualization platforms. The training material explicitly lists physical-server deployment using SUSE Linux and a third-party server, as well as virtual-machine deployment using VMware.

The platform can also be deployed using Huawei server and virtualization combinations, including Huawei 2288X servers, EulerOS, FusionCompute, and TaiShan-based environments. The availability of several combinations enables customers to select an architecture consistent with their existing data-center standards, procurement strategy, virtualization environment, and operational requirements.

Huawei nevertheless identifies a recommended platform combination in the training material. A recommendation does not mean that the other listed combinations are unsupported; it identifies the preferred configuration for standardized deployment and support. The material displays third-party server plus SUSE Linux and VMware-based virtual-machine deployment as valid alternatives while recommending Huawei 2288X V5 plus EulerOS.

The deployment must still satisfy the specified CPU, memory, storage, network-interface, software-version, and compatibility requirements. Therefore, the statement is True.

==================

The statement is true. AI-based energy-saving systems analyze historical traffic and usage patterns to predict periods of low network demand. Ordinary AP radios or access devices can then enter an energy-saving state when their capacity is not required, while surrounding devices maintain sufficient coverage and service availability.

IoT APs, however, may host continuously operating IoT cards, sensors, electronic shelf-label services, Bluetooth location functions, RFID services, healthcare devices, or asset-tracking terminals. Placing such an AP into an energy-saving or hibernation state could interrupt more than ordinary Wi-Fi connectivity. It could also disable an IoT module’s power supply, management channel, data backhaul, or persistent sensing function. Huawei’s Wi-Fi and IoT convergence architecture uses APs as shared locations, power sources, and communication channels for IoT services.

Huawei also applies intelligent technologies to analyze AP load trends and perform predictive network optimization. The safer default is therefore to exclude IoT APs from automatic energy-saving actions unless the administrator confirms that their attached IoT services tolerate interruption. Accordingly, the answer is True.

==================

The statement is false. In Parallel Redundancy Protocol, LAN A and LAN B must remain two separate, failure-independent networks. A PRP RedBox connects a singly attached node or conventional network to both parallel LANs and behaves toward the PRP network like a doubly attached node. It duplicates outgoing frames and transmits one copy through each PRP port. For incoming traffic, it accepts the first valid copy and discards the later duplicate before forwarding the frame through its interlink port.

The RedBox must not operate as a normal bridge that directly forwards frames from its LAN A port to its LAN B port. Doing so would connect the two redundant LANs, potentially creating loops, duplicate propagation, broadcast amplification, and a common failure path. That would defeat the fundamental PRP requirement that failure or disruption in one LAN must not affect the other.

The original video contains the typing error “PPR RedBox”; the correct term is PRP RedBox , meaning Parallel Redundancy Protocol Redundancy Box. PRP topology requires two separate networks with no direct links between them, while the RedBox provides controlled redundant attachment for non-PRP devices.

==================

SM4 is the supported SM-series cryptographic algorithm intended by this question. SM4 is a standardized symmetric block cipher that uses a 128-bit block size and a 128-bit key. It is suitable for high-volume data encryption because symmetric cryptography can process service traffic efficiently compared with public-key algorithms.

Within an SD-WAN or IPsec context, the bulk traffic carried through secure data channels requires a symmetric encryption algorithm. SM4 can therefore be used as the encryption component of an approved cryptographic suite where compliance with Chinese commercial cryptography requirements is necessary.

SM2 is an asymmetric public-key cryptographic suite used for functions such as digital signatures, key exchange, and public-key encryption. It is not the bulk data-encryption algorithm requested in this item. SM1 is a restricted proprietary algorithm whose implementation details are not publicly standardized in the same manner, while SM5 is not the supported option represented by the Huawei course question.

Huawei’s SD-WAN architecture uses IPsec to protect site-to-site services and supports secure GRE-over-IPsec data channels between edge devices. In the SM-series selection presented here, the correct supported traffic-encryption algorithm is SM4.

==================

The Network Management System is not an element of the IFIT measurement model. An IFIT measurement definition identifies the traffic to be measured, the locations where measurement actions occur, and the direction in which the flow is evaluated. The measurement flow specifies the target packets, usually through flow-identification fields. Measurement points define where packets are marked, counted, timestamped, or reported, such as ingress, transit, and egress nodes. Measurement direction distinguishes forward and reverse monitoring so that packet loss, delay, and path behavior can be analyzed correctly for each direction.

An NMS or controller remains operationally important because it creates measurement tasks, distributes configurations, receives telemetry data, correlates the results, and presents fault-location information. However, it is the management and analysis system surrounding the measurement model, not one of the model’s constituent measurement parameters.

Huawei positions IFIT as a high-precision telemetry mechanism used to delimit and locate application-quality faults. The training material highlights IFIT’s capability to locate faults rapidly and detect packet loss with extremely high reliability. Therefore, the component that is not part of the measurement model is the NMS.

==================

Option C is false. Traditional QoS can classify traffic and provide differentiated treatment for service categories such as voice, video, and ordinary data. It normally performs classification, marking, policing, shaping, congestion avoidance, and queue scheduling on an interface. This provides service-level differentiation but does not deliver sufficiently refined simultaneous management across multiple users and multiple applications.

Huawei’s material explicitly states that traditional QoS schedules traffic based on port bandwidth and can differentiate traffic according to service levels, but it is difficult to distinguish traffic by user. It also states that traditional QoS cannot manage and schedule traffic from multiple services and multiple users simultaneously.

HQoS addresses this limitation through hierarchical, multi-level queues. For example, a parent level can allocate bandwidth to departments, VPNs, sites, or users, while child queues prioritize applications such as voice, video, email, and best-effort traffic. Huawei describes HQoS as hierarchical scheduling that differentiates both services and users. Therefore, statements A, B, and D are correct, while statement C incorrectly attributes an HQoS capability to traditional QoS.

==================

Authentication points should generally be placed on access devices close to the terminals. For wireless users, the AP or WLAN access device is the natural admission point because it directly controls the station’s wireless association and service access. For wired users, the access switch directly connects the endpoint and can enforce 802.1X, MAC-address authentication, VLAN authorization, ACLs, and security-group policies.

Huawei recommends access devices as authentication points for employees and specifically recommends access switches as authentication points for wired dumb terminals using MAC-address authentication. Deploying enforcement close to endpoints prevents unauthenticated or unauthorized traffic from traversing deeper into the campus network. It also improves fault isolation, policy granularity, and scalability because admission processing is distributed across access devices.

Option A is incorrect. A centralized authentication point can simplify configuration and policy management, but it does not inherently provide higher performance. It can create concentrated processing pressure, enlarge the Layer 2 scope, and allow unauthenticated traffic to travel farther before being evaluated. Therefore, the recommended principles are represented by B, C, and D.

==================

AR routers support registration query center–based deployment, email-based deployment, and DHCP Option 148–based deployment. In registration query center deployment, the router obtains basic network connectivity, resolves or contacts Huawei’s registration service, retrieves the address and port of iMaster NCE, and then initiates registration. Huawei identifies AR routers, firewalls, switches, and APs as applicable devices for this method.

Email-based deployment is a major SD-WAN ZTP method for AR routers operating as CPEs. An administrator creates the site and ZTP configuration on iMaster NCE and sends a deployment URL to the onsite engineer. After the URL is opened and the parameters are written to the router, the device connects to the WAN and automatically registers with the controller.

DHCP Option 148 can provide the controller’s southbound IP address and port number to an IPv4 AR router, enabling automatic registration. Barcode scanning through the CloudCampus APP is specifically presented as an AP onboarding method, not an AR-router deployment method. Therefore, A, C, and D are correct.