H19-402_V1.0 HCSP-Presales – Data Center Network Planning and Design V1.0 Questions and Answers

In Huawei data center network design, particularly in large-scale CloudFabric architectures, Points of Delivery (PoDs) are a fundamental concept used to enable modular scalability, simplified management, and efficient resource pooling. A PoD typically consists of a group of servers, access switches (Leaf), and sometimes aggregation resources that function as a repeatable building block within the data center.

By dividing a data center into multiple PoDs, operators can achieve horizontal scalability , where additional capacity is added by deploying new PoDs without impacting existing services. This aligns with Huawei’s spine-leaf architecture, where each PoD connects to a common spine layer, ensuring consistent performance and low latency.

PoDs also improve fault isolation and operational efficiency , as issues can be contained within a specific module. From a management perspective, this structure simplifies provisioning, monitoring, and automation through platforms like iMaster NCE-Fabric.

Therefore, the statement is TRUE , as PoD-based design is a widely adopted best practice in Huawei data center planning and modern cloud infrastructures.

In Huawei M-LAG design, the peer-link is a critical connection between two M-LAG member devices used for synchronization of control information (such as MAC address tables, ARP entries, and state information) and for forwarding certain types of traffic like broadcast, multicast, and unknown unicast (BUM) traffic when necessary.

However, to prevent traffic loops and duplication , Huawei enforces strict isolation between peer-link interfaces and dual-homed M-LAG member interfaces . Specifically, this relationship is bidirectionally isolated , meaning traffic received from a dual-homed interface is not forwarded to the peer-link and then back to another dual-homed interface, and vice versa.

This bidirectional isolation ensures:

Loop prevention without relying on STP

Avoidance of duplicate packet forwarding

Efficient traffic handling in active-active scenarios

BUM traffic is only forwarded over the peer-link under controlled conditions, not blindly between all interfaces. Huawei CloudFabric best practices emphasize this isolation to maintain stable and predictable forwarding behavior in M-LAG deployments.

Therefore, the correct answer is C (Bidirectionally isolated) .

Huawei data center design guidelines emphasize end-to-end reliability across all layers of the physical network, including uplinks, devices, interconnections, and server access. All the listed options reflect valid reliability principles.

Option A is correct because ECMP (Equal-Cost Multi-Path) is a fundamental mechanism in spine-leaf architectures, ensuring load balancing and fast convergence when links fail. Option B highlights modular switch reliability , where inter-card connections prevent single-card failures from impacting connectivity.

Option C describes the DAD (Dual-Active Detection) mechanism in M-LAG scenarios. When a peer-link failure occurs, DAD ensures that only one device remains active, preventing split-brain conditions and maintaining network stability.

Option D addresses server-side reliability , where dual-homing with NIC teaming (active-active or active-standby) ensures uninterrupted service in case of link or device failure.

Together, these principles form Huawei’s comprehensive approach to building highly reliable and resilient data center networks.

According to Huawei’s CloudFabric intelligent O & M description, the health model is built as a multi-dimensional evaluation system that assesses the network from five dimensions: device, network, protocol, overlay, and service . This means every option listed in the question is part of the CloudFabric health model. Huawei explains that this model integrates telemetry-assisted data such as configuration data, forwarding entry data, logs, and KPI performance information, allowing the platform to detect faults and risks in real time across these five layers.

In practical Huawei CloudFabric operations, the device layer focuses on node health, hardware state, and resource status; the network layer checks connectivity and path quality; the protocol layer verifies control-plane protocols and convergence behavior; the overlay layer evaluates virtualized forwarding networks such as VXLAN fabrics; and the service layer measures the actual service experience and traffic exchange status. Huawei explicitly presents these five as the full health-evaluation scope of CloudFabric intelligent O & M, so the correct response is all five options

In Huawei CloudFabric intelligent O & M (Operations and Maintenance), multiple southbound data collection protocols are supported to enable comprehensive monitoring, analysis, and fault diagnosis. Commonly supported protocols include Telemetry, SNMP, NetStream, and ERSPAN .

Telemetry is the primary modern mechanism, providing real-time streaming data with high accuracy and low latency. SNMP is used for traditional device monitoring and alarm collection. NetStream (Huawei’s implementation of NetFlow) is used for traffic analysis, while ERSPAN enables remote traffic mirroring for deep packet inspection and troubleshooting.

However, Qx is not a standard or supported southbound protocol in Huawei CloudFabric O & M architecture. It is not referenced in Huawei documentation as a mechanism for data collection or monitoring.

Therefore, option B is correct because it identifies the protocol that is not supported , while all other options are valid and commonly used in Huawei intelligent O & M solutions.

Huawei CloudFabric supports multiple data center interconnection (DCI) solutions to meet different scalability and geographic deployment requirements.

Multi-PoD (A) is supported and is used within a single data center to divide it into multiple Pods for modular expansion. It enables large-scale resource pooling while maintaining consistent architecture and simplified management.

Multi-Site (C) is a key CloudFabric capability, allowing multiple geographically distributed data centers to interconnect. This supports disaster recovery (DR), geo-redundancy, and workload migration , often implemented using EVPN/VXLAN across sites.

Multi-DC (D) is a broader concept encompassing interconnection between multiple data centers, including active-active and active-standby designs. Huawei supports this through DCI solutions integrated with CloudFabric , ensuring seamless service continuity.

Multi-VPC (B) is not a standard Huawei CloudFabric multi-DC interconnection model; it is more commonly associated with public cloud networking concepts rather than Huawei’s data center fabric architecture.

Therefore, the correct answers are A, C, and D , which represent the supported multi-data-center interconnection solutions in Huawei CloudFabric.

Huawei data center solutions emphasize the transition toward all-flash data centers as a key enabler of enterprise digital transformation. Traditional HDD-based storage systems cannot meet the performance requirements of modern applications such as AI, big data analytics, cloud computing, and real-time services .

SSD (Solid-State Drive) technology provides significant advantages over HDDs, including:

Ultra-low latency (microseconds vs milliseconds)

High IOPS (Input/Output Operations Per Second)

Better reliability and durability (no mechanical parts)

Lower power consumption and higher density

As a result, SSDs have become the mainstream storage medium in modern data centers, especially in Huawei’s all-flash storage solutions (e.g., OceanStor Dorado) .

All-flash data centers enable:

Faster application response times

Improved user experience

Efficient support for AI and distributed workloads

Simplified storage architecture

Huawei promotes integrating all-flash storage with intelligent lossless networks (RoCE-based) to achieve end-to-end high-performance infrastructure.

Therefore, the statement is TRUE .

In Huawei VXLAN architecture, different gateway types serve distinct roles in tenant communication. The Layer 2 VXLAN gateway is specifically responsible for providing tenant access to the VXLAN network and enabling intra-subnet communication .

A Layer 2 VXLAN gateway (D) connects traditional Layer 2 networks (such as VLAN-based access networks) to the VXLAN overlay. It allows tenant devices or servers to access the VXLAN fabric while maintaining Layer 2 forwarding within the same subnet (same BD/VNI). This means hosts in the same subnet can communicate directly without requiring Layer 3 routing.

In contrast, Layer 3 VXLAN gateways (B) and centralized VXLAN gateways (C) are used for inter-subnet communication , enabling routing between different VXLAN segments. The default VXLAN gateway (A) typically refers to the default gateway IP configured for hosts, which is implemented via Layer 3 gateway functionality.

Huawei CloudFabric design clearly separates Layer 2 access (tenant onboarding and intra-subnet forwarding) from Layer 3 gateway functions (inter-subnet routing) .

Therefore, the correct answer is D (Layer 2 VXLAN gateway) .

In Huawei CloudFabric and cloud platform architectures (such as those integrated with ManageOne and OpenStack ), the concept of a tenant is used to logically isolate resources such as network, compute, and storage . It is correct that one department can be treated as a tenant , and an enterprise can have multiple tenants representing different departments or business units.

However, the statement is false because it incorrectly claims that the entire enterprise data center can be managed by one tenant administrator . In Huawei’s design:

Each tenant has its own administrator , responsible only for that tenant’s resources.

A higher-level role, such as a cloud administrator or system administrator , manages the entire data center infrastructure across all tenants.

This separation ensures:

Multi-tenancy isolation

Security and access control

Clear responsibility boundaries

Huawei emphasizes role-based access control (RBAC) , where tenant admins cannot manage resources belonging to other tenants or the entire infrastructure.

Therefore, the correct answer is FALSE .

According to Huawei data center network design guidelines, the selection of an underlay routing protocol depends on the scale and complexity of the network. For small to medium-sized data centers , particularly when the number of ToR (Top of Rack) switches is less than 100 , OSPF (Open Shortest Path First) is the recommended routing protocol.

OSPF is a mature and widely deployed link-state protocol that offers fast convergence, simple configuration, and strong interoperability. It is well-suited for smaller-scale spine-leaf networks where operational simplicity is a priority. Huawei recommends OSPF in such scenarios because it provides sufficient scalability and performance without the added complexity of protocols like BGP.

For larger-scale data centers (typically more than 100 ToR switches), Huawei suggests using IS-IS or BGP to improve scalability and simplify large-scale route management. RIP is not suitable due to its limitations in scalability and convergence speed.

Therefore, for networks with fewer than 100 ToR switches, OSPF is the optimal and recommended choice .

In Huawei CloudFabric architecture, a PoD (Point of Delivery) or site is defined as an independent network fault domain under the management of the SDN controller (such as iMaster NCE-Fabric). This design is fundamental for large-scale data center deployments, ensuring clear fault isolation, simplified management, and scalable expansion.

Each PoD typically consists of one or more spine-leaf fabric architectures , which provide high-bandwidth, low-latency, and horizontally scalable connectivity. Within a PoD, all devices operate under a unified control and policy framework delivered by the controller. If a failure occurs within a PoD, it is contained and does not affect other PoDs, thereby improving overall network reliability.

Huawei recommends this modular design approach to support multi-data center deployments, disaster recovery, and service expansion. Multiple PoDs can be interconnected to form a larger cloud fabric, while still maintaining independent fault domains.

Therefore, the statement accurately reflects Huawei CloudFabric design principles and is TRUE.

In IPv6, the concept of broadcast addresses does not exist , which is a fundamental difference from IPv4. Instead of broadcast, IPv6 uses multicast and anycast to achieve similar communication functions more efficiently. Therefore, statement B is false , as there is no such thing as an IPv6 broadcast address with all bits set to 1.

Statement A is correct: Unique Local Addresses (ULA) are intended for internal communication within a site or organization and are not routable on the public Internet, similar to IPv4 private addresses.

Statement C is also correct: Global Unicast Addresses in IPv6 are globally routable and function similarly to public IPv4 addresses, enabling end-to-end communication across networks.

Statement D is correct as well: Link-local addresses (FE80::/10) are automatically configured and used only for communication within the same local link (e.g., for neighbor discovery and routing protocols).

Huawei data center designs emphasize IPv6’s efficiency and scalability, particularly its elimination of broadcast traffic, which improves network performance and reduces unnecessary load.

Huawei M-LAG 2.0 is designed to provide ultra-fast convergence and high availability in modern data center networks. One of its key enhancements over traditional M-LAG implementations is the ability to achieve fast fault detection and rapid switchover , minimizing service interruption.

In the event of a single point of failure (such as link or device failure), M-LAG 2.0 leverages mechanisms like BFD (Bidirectional Forwarding Detection) and optimized peer-link synchronization to quickly detect failures and redirect traffic. The switchover time is typically around 5 milliseconds , ensuring near hitless failover for critical services.

This ultra-fast convergence is particularly important for applications such as AI workloads, financial systems, and real-time services , where even small delays can impact performance.

Compared to traditional technologies (which may take tens or hundreds of milliseconds), Huawei M-LAG 2.0 significantly improves network reliability, service continuity, and user experience .

Therefore, the correct answer is C (5 ms) .

Huawei iMaster NCE-Fabric ZTP (Zero Touch Provisioning) is designed to enable automated, fast, and error-free deployment of data center network devices, significantly reducing manual configuration efforts.

All listed options are valid characteristics:

Plug-and-play (A): Devices can automatically obtain configurations once powered on and connected to the network, requiring minimal manual intervention.

Visualized device onboarding (B): The controller provides a graphical interface to monitor onboarding progress, topology, and device status, improving deployment visibility.

Link verification (C): ZTP includes automatic cabling and link detection/verification , ensuring correct physical connections before service provisioning.

Batch device onboarding (D): Multiple devices can be onboarded simultaneously, enabling large-scale data center deployment with high efficiency.

Huawei emphasizes ZTP as a key capability in CloudFabric for:

Rapid service rollout

Reduced human error

Standardized deployment

Simplified O & M

This aligns with Huawei’s goal of achieving fully automated and intelligent data center network provisioning .

Therefore, the correct answers are A, B, C, and D .

Huawei data center design documents clearly state that overlay networks (typically based on VXLAN EVPN) are highly versatile and support multiple application scenarios across modern and traditional environments.

In private cloud scenarios , overlay networks enable resource pooling and seamless data center interconnection, allowing flexible workload migration and multi-tenant isolation. For traditional IDC hosting services , overlays provide improved scalability and tenant isolation compared to VLAN-based designs, making them suitable for legacy-to-cloud evolution.

In public cloud environments (IaaS/PaaS/SaaS) , overlay networks are essential for large-scale multi-tenancy, enabling logical network segmentation, automation, and elastic service provisioning. Similarly, in NFV cloud scenarios , overlays integrate with SDN and NFV architectures to support virtualized network functions, service chaining, and dynamic service deployment.

Huawei CloudFabric emphasizes that overlay technology is not limited to a single use case but is a foundational technology across all modern data center architectures. Therefore, all listed options are valid application scenarios.