PQ (Priority Queuing) ensures low-latency services like voice and video are prioritized.

WFQ (Weighted Fair Queuing) fairly allocates remaining bandwidth to services like FTP.

Option B provides a balanced approach: guarantees for voice/video via PQ, and fairness for FTP via WFQ.

Exact Extract - Huawei HCIE-Datacom QoS Module:

“Voice and video traffic should be handled by PQ to minimize delay and jitter. Non-critical services such as FTP should be placed in WFQ queues to ensure bandwidth fairness.”

In the Huawei SD-WAN solution, LAN-side devices (such as CPEs and aggregation routers) use various routing protocols to connect to Layer 3 networks and exchange routes dynamically. The supported protocols include:

✅ A. IS-IS (Intermediate System to Intermediate System)

A link-state protocol often used in large enterprise networks for fast convergence and scalability.

✅ B. OSPF (Open Shortest Path First)

A widely used dynamic routing protocol for intra-domain (LAN) connectivity.

Commonly used in enterprise networks to connect SD-WAN edge routers to LAN networks.

✅ C. BGP (Border Gateway Protocol)

BGP is primarily used for WAN and internet connectivity, but it can also be used inside large enterprise networks for LAN-side routing.

BGP enables inter-domain routing and policy-based route control.

✅ D. RIP (Routing Information Protocol)

A legacy distance-vector protocol still supported in some networks for basic LAN routing.

Less preferred due to slow convergence and hop-count limitations.

Reference from Huawei HCIE-Datacom Documentation:

Huawei SD-WAN Deployment Guide – LAN-Side Routing Protocols

HCIE-Datacom Training Material – Routing Configuration in SD-WAN

IS-IS (Intermediate System to Intermediate System) protocol has a limit on the size of Link-State PDUs (LSPs).

Why Fragmentation?

LSPs contain routing and topology information.

If the LSP exceeds the maximum size, fragmentation allows the device to store and forward more routes by breaking them into smaller LSPs.

Key Point: IS-IS fragmentation is essential in large-scale networks where routing tables grow beyond the default LSP size limit.

✅ Reference: Huawei HCIE-Datacom Guide - IS-IS Protocol and Route Scaling

Comprehensive and Detailed In-Depth Explanation:

In Huawei Open Programmability System (OPS), the URL structure is used to specify managed objects in a standardized way.

The URL path /ifm/interfaces/interface is used in NETCONF/YANG-based APIs to represent interface-related data on a device.

This path allows users to query, configure, or manage network interfaces through programmatic means.

The IFM (Interface Management) model is commonly used for managing network interfaces, and this URL path correctly follows the convention.

Therefore, the statement is TRUE.

HTTP/2 is a TCP-based protocol, not UDP-based. It runs on top of TCP port 443 (usually via TLS). The protocol enhances performance using multiplexing, header compression, and stream prioritization, but it still relies on TCP, unlike newer protocols like HTTP/3, which uses UDP and QUIC.

Exact Extract - Huawei Application Networking Fundamentals:

“HTTP/2 continues to use TCP as its transport layer, introducing improvements like multiplexing over a single TCP connection. UDP-based HTTP/3 is a separate protocol built on QUIC.”

When VLAN-based MAC address flapping detection is configured, the following actions can be taken:

Alarm sending (generates logs or SNMP traps)

MAC address blocking (blocks specific flapping MAC addresses)

Interface blocking (shuts down or disables the interface temporarily)

Traffic filtering, however, is not an action option directly supported as a response to MAC flapping. Traffic filtering is part of ACL or QoS, not a built-in flapping response.

Exact Extract - Huawei Switching Configuration Guide – MAC Address Management:

“Actions that can be configured upon detection of MAC address flapping include sending alarms, blocking MAC addresses, and blocking interfaces. Traffic filtering is not supported as a direct action.”