Free Practice Questions for Huawei H35-211_V2.5 Exam

On Huawei OLTs, the standard QoS pipeline for upstream packets is: first perform traffic classification (identify flows), then marking (set CoS/DSCP as required), next apply traffic policing (rate-limit and color traffic), followed by congestion avoidance (AQM such as RED/WRED), and finally congestion management (queue scheduling/priority queuing). This ordered sequence ensures correct identification and marking before any rate enforcement, and that packets encounter AQM prior to scheduler-based dequeue.

A rogue ONU that transmits out of schedule or at abnormal optical levels can disrupt upstream time-slotting on the PON, causing collision and interference. This can force other ONUs on the same PON to deregister or flap frequently. Huawei OLTs provide rogue ONU detection/isolation to protect the PON.

PITP (Port Identification Transparent Transmission) is used on access networks to carry a user’s physical access-location to the upper AAA/BRAS. It has two working forms: P-mode (PPPoE+)—injecting location identifiers into PPPoE discovery—and V-mode (Vendor-tag)—carrying vendor/location tags transparently upstream. The purpose is to let the upper server associate user credentials with access location and, by policy, restrict roaming. Options A, B, D, and E correctly describe these behaviors/terms. Option C is inaccurate as written: PITP itself does not “bind the authentication” or inherently “avoid theft/roaming”; it only delivers location info. Preventing credential theft/roaming is achieved by AAA/BRAS policy that uses the PITP-carried location, not by PITP alone.

The ONT details pane in eSight displays access-port attributes (admin/state, type), Ethernet rate/speed/duplex, and PON optical module telemetry such as temperature and Tx/Rx optical power for condition monitoring and troubleshooting.

For ONT zero-touch on eSight/iMaster NCE-Campus, the prerequisite is that the OLT is onboarded and provisioned (communication parameters, northbound credentials, templates) so that discovered ONTs can inherit policies and be auto-activated. During incremental OLT configuration, eSight does push/update the OLT’s configuration (templates, profiles, authentication rules). Saying “do not provision OLT” is therefore false.

In Type C single-attribution protection, two PON ports form a protection pair to one ONU/ODN, but only one path is active at a time.

B — Correct: Protection groups operate in active/standby mode; only one OLT-side PON port forwards user traffic at any moment.

A — Not necessarily correct: A branch fiber break local to one path can trigger switchover, but describing it as “the OLT work port becomes standby” is imprecise; the group performs role inversion based on configured triggers and signaling, not solely by OLT port state wording.

C — Not always: Uplink failure triggers switchover only if the protection group is explicitly configured to track the uplink Ethernet port; it is not an unconditional behavior.

D — Misleading: While service entries for the ONU remain consistent from a user perspective, additional protection-group configuration is required on the OLT; thus it is not “completely identical” to a non-protected setup.

(Reference: HCIP-Access V2.5 – Type C single-homing protection architecture, active/standby forwarding, and optional uplink-tracking triggers.)

A is consistent with Huawei L2 multicast practice: global L2 multicast/IGMP snooping parameters can be set and then take effect for multicast VLANs involved in service provisioning.

B reflects the forwarding/CPU-punt behavior on access line cards: IGMP Reports/Leaves from users are recognized by board logic and processed by the control plane to update multicast state.

C matches default service control on BTV/IPTV access where a default program limit (commonly 8) per user applies unless adjusted by policy/profile.

D is incorrect: when IGMP match mode is disabled, multicast programs are not required to be pre-provisioned as channels; groups can be learned dynamically by IGMP. Preconfiguring channels is needed when match mode is enabled (channel matching enforced).

B is incorrect: NCE deployment options (on-premises, private cloud, public cloud) are determined by service and architecture needs, not by which vendor provides the physical devices.

D is incorrect: Deployment duration varies with hardware platforms, virtualization stacks, and software environments; it is not the same across scenarios.

A and C are correct: NCE exposes NBIs for OSS integration and operates at the analysis/control layer to collect, analyze, and predict issues using big-data/AI capabilities.

IGMP is the host-side membership protocol: the first-hop router (querier) uses IGMP Queries/Reports/Leaves to manage host participation in multicast groups and to ensure forwarding state reflects receiver interest. PIM-DM/PIM-SM build distribution trees between routers, and MSDP shares source information between PIM-SM domains—they are not used by hosts.

In AQM, high-priority queues are given more tolerant (larger) thresholds so they are less likely to be dropped early. Setting a smaller early-drop threshold for high priority would increase their loss probability, which contradicts QoS objectives—thus A is incorrect. Descriptions in B, C, and D align with Huawei’s treatment of congestion avoidance: RED/WRED proactively drops to stabilize queues and can reduce delay variation; tail drop at full buffer can lead to global TCP synchronization.