Free Practice Questions for Huawei H12-891_V1.0 Exam

Huawei Open Programmability System (OPS) and Scripting Support

HuaweiOPS (Open Programmability System)enables network automation usingscript-based programmingfordevice management and configuration.

✅Python is the primary language integrated into Huawei OPS.

Python scripts can automate device configurations, monitoring, and troubleshooting.

OPS supports Python libraries for interacting with network APIs and CLI commands.

Used for Huawei CloudCampus, SDN, and Datacom devices.

In MPLS (Multiprotocol Label Switching), Label Switching Routers (LSRs) handle packets based onFECs (Forwarding Equivalence Classes)and their positions in the label-switched path:

Ingress LSR:The entry point for labeled packets; it classifies packets into FECs and assigns the initial label.

Transit LSR:Intermediate routers that swap labels and forward packets along the LSP.

Egress LSR:The last router in the LSP that removes the label and forwards the packet normally.

An LSRcannotbeboth an ingress and a transit router for the same FEC, because an ingress LSR is defined as thestarting pointfor that specific FEC's LSP. If it’s the ingress, it means the labeled pathstarts there, so it can't be in themiddle (transit)of that same path.

Therefore, the statement isFALSE.

Intra-Area-Prefix-LSA (Type 9) is used in OSPFv3 to carry IPv6 prefix information for a router or network and is flooded within the area.

Link-LSA (Type 8) is only sent on the local link and is not flooded throughout the area.

Inter-Area-Prefix-LSA (Type 3) and Inter-Area-Router-LSA (Type 4) are also flooded within an area but originate from ABRs, typically for cross-area route advertisement.

That said, Intra-Area-Prefix-LSA is specifically flooded within an area, matching the context of the question directly.

Exact Extract - Huawei HCIE-Datacom OSPFv3 Module:

“Intra-Area-Prefix-LSAs are flooded within the area and advertise the IPv6 prefixes associated with router and network LSAs.”

✅A. encoding: indicates the character set encoding format. Currently, only UTF-8 encoding is supported.

UTF-8 is the default and only supported character encoding in NETCONF XML.

✅B. /: indicates the end of the current tag.

In XML, closes an element, defining the end of a structure.

✅C.

The

✅D. ?>: indicates the end of an instruction.

Closes theXML declaration.

Reference from Huawei HCIE-Datacom Documentation:

Huawei NETCONF Development Guide – XML Formatting Rules

HCIE-Datacom Training Material – Understanding XML in Network Automation

ForSRv6 (Segment Routing over IPv6)deployment on abearer WAN, the following are essential:

IGP (OSPFv3 or IS-IS): Required for SID advertisement and SRv6 route computation →✅

BGP: Required when deployinginter-domain SRv6or for control plane distribution of VPN/service routes →✅

Not required:

MPLS: SRv6 replaces MPLS labels withIPv6-based SIDs→❌

BGP-LU: Used inMPLS-based inter-AS scenarios,not applicableto SRv6 →❌

Correct answers: B, C

In Huawei iMaster NCE-WAN controller active/standby deployment, to ensure seamless switchover and uninterrupted management and control channel communication, the following IPs must be configured consistently:

A. Southbound public IP addresses — Required for southbound communication from remote WAN devices via public networks.

C. Southbound private IP addresses — Used for devices accessing controllers over private links. Must remain unchanged between controllers.

D. Northbound IP addresses — For API and external system integration, ensuring upper-layer platforms don't need reconfiguration during switchover.

Internal interconnection addresses (B) are used for internal HA communication between controllers and do not need to be identical, hence not selected.

Exact Extract - Huawei HCIE-Datacom iMaster NCE-WAN Deployment Guide:

“To maintain service continuity, configure consistent southbound and northbound IP addresses across active and standby controllers. Internal interconnection addresses differ between nodes.”

NETCONF definesdatastoresto manage device configurations:

running: Active configuration in use

candidate: Staging area for changes before applying

startup: Configuration loaded on reboot

NETCONF operations:

: Applies changes fromcandidate → running→✅

: Deletes a specified datastore (e.g., startup) →✅

: Validates syntax/logic in thecandidate datastore→✅

Statement D is incorrect: never submits config from startup to running— that’s handled automatically at boot time, not through NETCONF commands.

Correct answer: D

When VLAN-based MAC address flapping detection is configured, the following actions can be taken:

Alarm sending (generates logs or SNMP traps)

MAC address blocking (blocks specific flapping MAC addresses)

Interface blocking (shuts down or disables the interface temporarily)

Traffic filtering, however, is not an action option directly supported as a response to MAC flapping. Traffic filtering is part of ACL or QoS, not a built-in flapping response.

Exact Extract - Huawei Switching Configuration Guide – MAC Address Management:

“Actions that can be configured upon detection of MAC address flapping include sending alarms, blocking MAC addresses, and blocking interfaces. Traffic filtering is not supported as a direct action.”