H12-891_V1.0 Practice Questions

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.  

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

✅

B.  

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 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.  

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

VXLAN networks suffer from ARP flooding because ARP requests are broadcasted across all VTEPs in a Layer 2 domain. To reduce ARP flooding, the following mechanisms can be enabled:

✅

A.  

Allows the local VTEP to respond to ARP requests without forwarding them across the VXLAN network.

The VTEP caches MAC-IP mappings and replies directly to ARP requests, reducing unnecessary flooding.

✅

B.  

Converts ARP broadcast packets into unicast or multicast packets to minimize network-wide flooding.

✅

C.  

Collects and stores MAC-IP bindings of endpoints, which can be used by proxy ARP to reduce flooding.

Incorrect Answer:

❌

D.  

Port isolation prevents communication between devices within the same VLAN but does not help reduce ARP flooding between VTEPs.

Reference from Huawei HCIE-Datacom Documentation:

Huawei VXLAN Configuration Guide – ARP Optimization Techniques

HCIE-Datacom Training Material – Reducing ARP Broadcasts in VXLAN Networks

The Differentiated Services (DiffServ) model for Quality of Service (QoS) enables traffic management based on predefined priorities. This involves classifying, policing, queuing, and scheduling traffic to ensure efficient network resource utilization.

Breakdown of Each QoS Processing Step:

✅ Step 1: Traffic Classification and Marking

Purpose: Identifies and marks packets based on QoS attributes such as DSCP (Differentiated Services Code Point) or 802.1p priority bits.

Function: Assigns a QoS label to packets for further processing.

Example: Packets carrying voice traffic (EF - Expedited Forwarding) are marked for high-priority treatment.

✅ Step 2: Traffic Policing (CAR - Committed Access Rate)

Purpose: Enforces bandwidth limits on specific traffic flows to prevent excessive usage.

Function: Drops or re-marks packets exceeding the assigned bandwidth threshold.

Example: If a video stream exceeds 10 Mbps, excess packets may be dropped or re-marked.

✅ Step 3: Congestion Management (Queuing and Scheduling)

Purpose: Manages traffic flow through queues based on assigned QoS levels.

Function: Places packets in appropriate priority queues (e.g., Strict Priority, Weighted Fair Queuing - WFQ, CBWFQ).

Example: Voice packets are assigned to high-priority queues for low-latency forwarding.

✅ Step 4: Congestion Avoidance

Purpose: Prevents network buffer overflows and excessive packet drops.

Function: Uses mechanisms like WRED (Weighted Random Early Detection) to drop lower-priority packets before congestion occurs.

Example: If a queue reaches 80% capacity, WRED may drop low-priority packets to maintain QoS.

✅ Step 5: Traffic Shaping

Purpose: Smooths out traffic bursts to maintain a consistent transmission rate.

Function: Buffers and delays packets to prevent excessive packet drops.

Example: If outgoing traffic exceeds 50 Mbps, shaping ensures it does not exceed this limit while maintaining steady flow.

In firewall hot standby (HRP - Hot Standby Routing Protocol) mode, certain data can be synchronized between the active and standby firewalls to ensure uninterrupted service.

The following data is backed up:

✅ Server mapping table: Contains information about NAT mappings and other session mappings.

✅ AAA user table (excluding the default user admin): Ensures that authenticated users do not need to re-authenticate in case of failover.

✅ Session table: Ensures that existing connections remain active when switching to the standby firewall.

❌ Dynamic MAC address table is NOT backed up because it is dynamically learned and not relevant to firewall session synchronization.

✅ Reference: Huawei HCIE-Datacom Guide - Firewall HRP Synchronization