EVPN (Ethernet VPN) is a control plane technology used with VXLAN to provide Layer 2 and Layer 3

services in data center networks, including Huawei’s implementations. EVPN routes are categorized

into types, with Type 5 routes (IP Prefix routes) serving a specific purpose:

Type 5 Routes: These routes advertise IP prefixes and are used for inter-subnet routing, allowing

communication between different VXLAN Virtual Network Identifiers (VNIs) or between VXLAN

networks and external networks. They carry a Layer 3 VNI and IP prefix information, enabling routers

or gateways to perform Layer 3 forwarding.

Usage Scope: Type 5 routes are not limited to hosts on a VXLAN network accessing external

networks. They are also used by network devices (e.g., gateways, routers) within the EVPN domain

to facilitate routing between subnets, including intra-VXLAN communication. For example, a

centralized gateway or distributed gateway can use Type 5 routes to route traffic within the data

center or to external networks, not just host-initiated access.

The statement is FALSE (B) because Type 5 routes are not exclusively for hosts on a VXLAN network to

access external networks; they support broader Layer 3 routing functions across the EVPN domain.

Reference: Huawei HCIP-Data Center Network Training – EVPN Routing; CloudFabric EVPN

Configuration Guide.

A hypervisor is a software layer that creates and manages virtual machines (VMs) by abstracting

physical resources from the underlying hardware. The question specifies that the hypervisor

virtualizes "memory" and "input/output (I/O) resources," and the task is to provide the missing

resource acronym in uppercase letters. In virtualization contexts, including Huawei’s FusionCompute

or OpenStack with KVM, the primary physical resources virtualized by a hypervisor are:

CPU: The central processing unit (CPU) is virtualized to allocate processing power to VMs, enabling

multi-tenancy and workload isolation.

Memory: Virtualized to provide RAM allocation to VMs, abstracted via memory management units

(MMUs).

I/O Resources: Input/output resources (e.g., NICs, disks) are virtualized to allow VMs to

communicate and store data, often through virtual NICs (vNICs) or virtual disks.

The question lists "memory" and "I/O resources" explicitly, implying the missing resource is CPU, as it

completes the standard triad of virtualized resources in hypervisor design. Thus, the answer is CPU.

Reference: Huawei HCIP-Data Center Network Training – Virtualization Fundamentals;

FusionCompute Architecture Guide.

In Huawei’s CloudFabric Solution, the iMaster NCE-Fabric SDN controller cluster separates network

planes based on carried services to ensure scalability and security. Let’s evaluate each option:

A. BGP microservice plane: This is not a standard plane in Huawei’s SDN architecture. BGP is used in

the underlay/overlay but not defined as a separate microservice plane for the controller. FALSE.

B. Southbound service plane: This is true. The southbound plane carries configuration and control

data to network devices (e.g., via NETCONF, BGP-EVPN), a critical service plane in SDN. TRUE.

C. Northbound management plane: This is true. The northbound plane provides APIs for

management applications and orchestration (e.g., OpenStack integration), handling service requests.

TRUE.

D. Internal communication plane: This is true. This plane facilitates communication between

controller cluster nodes for synchronization and high availability. TRUE.

Thus, B (Southbound service plane), C (Northbound management plane), and D (Internal

communication plane) are the network planes divided based on carried services.

Reference: Huawei CloudFabric Data Center Network Solution – SDN Architecture; HCIP-Data Center

Network Training – Controller Planes.

Traditional data center networks (DCNs) often suffer from single points of failure, limited scalability,

and traffic bottlenecks. Both M-LAG and stacking address these issues, but their suitability for 24/7

service continuity differs.

M-LAG Benefits: M-LAG (Multi-Chassis Link Aggregation) on Huawei CE switches allows two devices

to act as a single logical switch, providing active-active forwarding, high availability, and rapid

failover (e.g., via peer-link synchronization). It supports non-stop service during device failures,

making it ideal for 24/7 continuity.

Stacking Benefits: Stacking combines multiple switches into a single logical unit, sharing a control

plane. While it improves scalability and simplifies management, a stack master failure can disrupt

the entire stack unless redundancy is perfectly configured, potentially affecting service continuity.

Comparison: M-LAG’s decentralized design and real-time synchronization offer better fault isolation

and recovery compared to stacking, where a master switch failure impacts the stack. Huawei

documentation highlights M-LAG’s superiority for high-availability scenarios like 24/7 operations.

The statement is TRUE (A) because M-LAG is indeed a better choice than stacking for ensuring 24/7

service continuity due to its robust failover and redundancy features.

Reference: Huawei CloudEngine Series Switch Configuration Guide – M-LAG vs. Stacking; HCIP-Data

Center Network Training – High Availability Solutions.

Huawei’s CloudFabric intelligent O&M solution, leveraging iMaster NCE-Fabric and FabricInsight,

uses the "1-3-5" principle (detect within 1 minute, locate within 3 minutes, rectify within 5 minutes)

to handle faults. This approach analyzes faults across multiple dimensions. Let’s evaluate each

option:

A . Device: This is supported. The solution monitors device-level metrics (e.g., CPU, memory) to

detect and locate faults. SUPPORTED.

B . Protocol: This is supported. Protocol issues (e.g., OSPF conflicts, BGP errors) are analyzed for fault

detection and resolution. SUPPORTED.

C . Service: This is supported. Service-level faults (e.g., tenant connectivity, VPC issues) are tracked

and addressed. SUPPORTED.

D . Application: This is not supported. The "1-3-5" troubleshooting focuses on network infrastructure

(devices, protocols, services, configurations), not application-layer issues, which are outside its

scope. NOT SUPPORTED.

E . Configuration: This is supported. Configuration errors (e.g., mismatched VNIs) are detected and

rectified as part of the process. SUPPORTED.

Thus, D (Application) is not a dimension supported by the "1-3-5" troubleshooting function.

Reference: Huawei CloudFabric Data Center Network Solution – Intelligent O&M; HCIP-Data Center

Network Training – Troubleshooting Dimensions.