H12-841_V1.5 Exam Dumps : HCIP-Datacom-Campus Network Planning and Deployment V1.5

iMaster NCE-Campus supports multiple deployment modes to meet the needs of different enterprise customers, including on-premise deployment, MSP-owned cloud deployment, and Huawei public cloud deployment. The choice of deployment mode mainly depends on whether the customer wants to invest in infrastructure, manage the platform independently, or use a fully hosted service.

In this scenario, the supermarket chain explicitlydoes not want to purchase physical servers or software, which means an on-premise deployment is not suitable. On-premise mode requires customers to prepare hardware resources, install software, and maintain the system themselves. Similarly, an MSP-owned cloud deployment typically involves a managed service provider hosting the platform, which may still require contractual dependency on a third party and is not the most straightforward option for enterprises seeking minimal investment and simplified operations.

According to HCIP Datacom Campus Network documentation, theHuawei public cloud deploymentis recommended for customers who want acloud-based, subscription-oriented solution. In this mode, iMaster NCE-Campus is hosted and operated on Huawei Cloud. Customers only need to register and subscribe to the service, without purchasing servers, storage, or management software. Huawei is responsible for system maintenance, upgrades, security, and high availability.

This deployment model is especially suitable forretail chains and multi-branch enterprises, such as supermarkets, because it enables centralized management of geographically distributed branch networks with low initial investment and fast rollout.

Therefore, the recommended deployment mode in this case isHuawei public cloud, making optionCthe correct answer.

In a VXLAN BGP EVPN architecture,EVPN Type 5 routes, also known asIP Prefix routes, are used to advertiseLayer 3 reachability informationbetween VXLAN segments. These routes are essential for implementing inter-VNI communication and external network connectivity through distributed or centralized gateways.

According to HCIP Datacom Campus Network documentation, a Type 5 route carriesIP prefix information, including theIP prefix and its prefix length, allowing VTEPs to learn network-level routing information rather than host-level details. TheRoute Distinguisher (RD)is also included to ensure uniqueness of routes across different VPN instances, which is critical in multi-tenant environments. Additionally, thegateway IP addressis carried to identify the next-hop gateway responsible for forwarding traffic toward the advertised prefix.

Unlike EVPN Type 2 routes, which advertiseMAC address and optional host IP address information, Type 5 routes donotcarry MAC addresses. Type 5 routes operate purely at the Layer 3 level and are independent of Layer 2 forwarding. Their purpose is to exchange subnet-level routing information rather than endpoint-level details.

MAC addresses are only relevant for Layer 2 forwarding and ARP/ND suppression, which are functions of EVPN Type 2 routes. Including MAC information in Type 5 routes would be unnecessary and inefficient for Layer 3 routing purposes.

Therefore, the field that isnot carriedin a BGP EVPN Type 5 route is theMAC Address, making optionCthe correct answer.

Comprehensive and Detailed 200 to 250 words of Explanation From HCIP Datacom Campus Network documents knowledge without any URL or Links:

In anasymmetric IRB (Integrated Routing and Bridging)VXLAN forwarding model, Layer 2 forwarding and Layer 3 routing occur ondifferent VTEPs. When PC1 sends traffic to PC2, the packet is first forwarded to thelocal gateway (VBDIF interface)on VTEP1 for Layer 3 routing.

After routing is performed, VTEP1 encapsulates the packet into a VXLAN packet and forwards it to VTEP2. Importantly, theoriginal data frame inside the VXLAN packethas already been rewritten after routing. The destination MAC address in the original Ethernet frame is no longer the MAC address of PC2, but theMAC address of the next-hop gateway on the remote VTEP.

In the figure, this next-hop MAC address isMAC C, which belongs to the VBDIF interface on VTEP2. MAC D (PC2’s MAC address) is only used after the packet is decapsulated and forwarded locally by VTEP2.

According to HCIP Datacom Campus Network VXLAN forwarding behavior, the correct destination MAC address of the original data frame sent from VTEP1 to VTEP2 isMAC C, making optionCcorrect.