Free Huawei H35-211_V2.5 Practice Exam with Questions & Answers | Set: 2

IPTV over FTTH relies on multicast control; therefore the essential U2000 template is the IGMP template, which defines IGMP behaviors, program authorization binding, and multicast parameters used by the OLT/ONT. MGC applies to voice (VoIP), and SNMP pertains to NMS communication rather than IPTV service logic; value-added templates are not mandatory for basic IPTV.

In GPON, DBA (Dynamic Bandwidth Allocation) operates in the upstream direction. The OLT grants upstream transmission opportunities to ONTs by assigning T-CONT bandwidth (Fixed/Assured/Non-Assured/Best-Effort) within upstream frames. The downstream direction is a continuous broadcast stream from the OLT at the fixed GPON line rate; user traffic is multiplexed without DBA. Hence, DBA is upstream-only; downstream traffic is not DBA-scheduled.

In GPON Type C dual-attribution protection, the ONU has dual PON connections to two OLT PON ports (or two OLTs). When the protection group is configured to track the OLT’s uplink Ethernet port, a Down state on that uplink is an OLT-side trigger. The OLT initiates the protection action (forces the working/standby role swap via PON protection signaling).

A — Correct behavior: After the OLT triggers protection, the ONU’s working PON interface becomes standby, and the protect interface becomes working.

B — Correct behavior: The OLT monitors and updates the ONU uplink status as part of the protection group state machine.

C — Correct behavior: After inversion, services egress the ONU via the protect PON port toward the OLT, i.e., traffic follows the configured protect path.

D — Incorrect (answer): In this scenario the trigger is the OLT’s uplink Ethernet status, not an ONU-detected failure. Therefore the ONU does not detect the fault nor initiate the switchover; the OLT does.

(Reference: HCIP-Access V2.5 – GPON protection mechanisms; Huawei OLT protection group behavior, Type C dual-homing with uplink-tracking.)

Huawei multicast guidance stresses IGMP version compatibility: devices running an earlier version must interoperate only with hosts using the same or earlier version, otherwise v3 messages may not be processed. In Huawei’s multicast feature guidance for access devices (OLT side vs. user side), the behavior documented is that when the device is operating in IGMPv2, IGMPv3 Report messages from terminals are not processed—interoperation is restored only after the terminal/device side is downgraded to v2 (often driven by periodic queries that induce hosts to respond in v2). This maps operationally to dropping unsolicited IGMPv3 Reports when the OLT is fixed to v2. Huawei also recommends ensuring the device runs an IGMP version the same as or later than member hosts to avoid such loss. Therefore, with OLT fixed at v2, an incoming v3 Join is discarded.

In H.248, the MGC controls the MG by creating a Context (also called an empty connection) and then adding terminations to build point-to-point, multipoint, or conference topologies. During call setup the MGC typically creates an empty context first, then binds terminations as media is negotiated.

A is incorrect: contexts and terminations can be modified during the session.

B is incorrect as written (the association/context is released, not “used”).

C is incorrect: an MG limited to point-to-point cannot host three or more endpoints in one context.

SNMPv2c uses a community-string model (clear-text “read”/“write” strings) and provides no authentication integrity or encryption. Only SNMPv3 adds auth/privacy (AuthNoPriv/AuthPriv) with hashing and encryption. Therefore, stating that SNMPv2c can encrypt user passwords is false.

With ONT Zero-Touch Provisioning (ZTP) enabled on eSight, newly discovered ONTs can be automatically identified and provisioned by pushing service templates from eSight. This removes the need for advance (preset) service configuration on the OLT during incremental onboarding; the OLT simply accepts the provisioning delivered by eSight.

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.

On Huawei VRP, Advanced IPv4 ACLs (which can match source IP, destination IP, and L4 port numbers) use the 3000–3999 numbering range.

2000–2999 = Basic IPv4 ACL (matches source IP only).

3000–3999 = Advanced IPv4 ACL (matches source/destination IP, protocol, ports).

4000–4999 = Layer 2 (MAC) ACL.

5000–5999 = User-defined/other ranges, not the standard advanced IPv4 range.

Therefore, to match IPs and ports, select 3000–3999.

Huawei access security recommends limiting MAC learn counts per port/VLAN, and using anti-MAC-spoofing bindings: either automatic (dynamic) bindings generated by the system or manual static MAC bindings to the service/port. Simply replacing a terminal is not a network-side mitigation method and is not listed as a protection measure.