H12-821_V1.0 Huawei HCIP-Datacom-Core Technology V1.0 Free Practice Exam Questions (2026 Updated)

 Additional Port Roles in MSTP

Master Port: Indicates the port on the shortest path to the root bridge in a region.

Regional Edge Port: Identifies a port at the boundary of the MST region.

Backup and edge ports exist in RSTP and are not newly introduced by MSTP.

 HCIP-Datacom-Core Reference

MSTP port roles are elaborated in the MSTP configuration sections​​.

Comprehensive and Detailed Step-by-Step Explanation:

Multi-Channel Protocols:

Multi-channel protocols use separate channels for control and data communication, requiring application-specific packet filtering (ASPF) to track sessions.

Examples:

FTP (A): Uses separate control and data channels.

SIP (B): Uses multiple ports for signaling and media.

H.323 (D): A VoIP protocol using multiple channels.

Single-Channel Protocol:

SMTP (C): A single-channel protocol for email communication, which does not require ASPF.

An IP prefix filter is designed to match both the IP address and its prefix length, making it suitable for filtering routing information rather than data packets. Options A and D are incorrect because IP prefix filters do not work directly on data packets, and they can match both prefix numbers and lengths ​.

Routing Entries in PIM

(S, G) entries: Represent the shortest path tree (SPT) from a specific source (S) to a specific multicast group (G). These entries are created after data packets are transmitted directly from the source to the receivers.

(S, G) entries are used in both PIM-DM and PIM-SM modes.

PIM-DM and PIM-SM Modes

In PIM-DM, multicast traffic is initially flooded throughout the network and pruned where no receivers exist. (S, G) entries represent source-specific paths created after the flooding stage.

In PIM-SM, multicast traffic initially flows through a shared tree, but (S, G) entries are created when the network switches to the SPT for more efficient forwarding.

HCIP-Datacom-Core Reference

The functionality and application of (S, G) routing entries are detailed in multicast and PIM configuration chapters​​.

 IP Prefix List Matching Conditions

An IP prefix list matches based on:

Mask: Specifies the subnet mask length.

Action: Specifies whether to permit or deny.

Index: Orders the rules within the prefix list.

Port numbers are not applicable as matching conditions in an IP prefix list.

 HCIP-Datacom-Core Reference

IP prefix list configurations are detailed in the routing policy and route filtering chapters​​.

Comprehensive and Detailed Step-by-Step Explanation:

1. Overview of BGP:

BGP (Border Gateway Protocol) is an Exterior Gateway Protocol (EGP) designed to exchange routing information between different Autonomous Systems (ASs) on the internet. Unlike traditional distance-vector protocols (like RIP), BGP is considered a path-vector protocol, as it not only determines reachability but also ensures policy-based routing decisions and advanced path selection mechanisms.

2. Analysis of Each Option:

Option A: BGP does not support authentication. Therefore, it cannot ensure network security.

This statement is incorrect.

BGP supports authentication using mechanisms such as TCP MD5 (Message Digest 5) and TCP-AO (Authentication Option). These authentication mechanisms ensure that BGP messages are not tampered with or intercepted during transmission, enhancing network security.

HCIA-Datacom Study Guide, Chapter "BGP Concepts and Features," Authentication Section.

Option B: BGP uses TCP as the transport layer protocol.

This statement is correct.

BGP relies on TCP (Transmission Control Protocol) as its transport layer protocol, specifically on port 179. TCP provides reliable delivery of BGP messages and ensures the session remains established in case of transient network issues.

TCP also handles error recovery and sequencing, making it a suitable choice for BGP, which requires reliable communication between peers.

Comprehensive and Detailed Step-by-Step Explanation:

Portal Authentication:

Portal authentication uses a web-based mechanism where clients are redirected to a login page.

Communication between the access device and Portal server uses HTTP or HTTPS protocols.

Correct Statements:

Option A: HTTP or HTTPS is used for Portal authentication.

Option D: Portal protocol packets are transmitted over TCP for reliable communication.

Incorrect Statements:

Option B: Port 2000 is not the default for processing Portal packets.

Option C: The default destination port for communication with the Portal server is not 50100.

The summary automatic command in BGP is used to enable automatic summarization of routes, particularly for classful networks. However, manual summarization takes precedence over automatic summarization when both are configured. This makes the statement claiming automatic summarization takes precedence false ​.

The MED (Multi-Exit Discriminator) is an optional, non-transitive attribute used to influence the exit path. MED is considered after attributes such as Local-Preference, AS-Path, and Origin during route selection. By default, if a MED value is missing, it is treated as 0 unless the bestroute med-none-as-maximum command is configured to treat it as 4294967295 ​.

 ACL in Routing Policies

ACLs are frequently used in routing policies to match specific routes based on criteria such as source IP, destination IP, and more. This allows ACLs to influence route redistribution, filtering, and forwarding decisions.

 HCIP-Datacom-Core Reference

ACL applications in routing policies are discussed in the routing policy chapters​​.

 DIS and DR Election

The IS-IS Designated Intermediate System (DIS) is responsible for generating and updating pseudonode LSPs on a broadcast network.

Unlike OSPF DR, the IS-IS DIS does not preempt by default. This behavior avoids unnecessary flapping in the network due to frequent DIS re-elections.

 HCIP-Datacom-Core Reference

The characteristics of DIS and DR behavior are explained in IS-IS network operation chapters​​.

Let’s analyze the process step-by-step:

R1 redistributes the direct route 10.1.1.0/24 into OSPF.

This OSPF route reaches R2 and R3.

R2 and R3 are in an environment that uses IS-IS towards R4.

Both R2 and R3 re-advertise this OSPF route into IS-IS toward R4 (bidirectional route redistribution).

On R3, a route-policy named hcip is applied to control ASE (Autonomous System External) route preference.

The ACL matches the route 10.1.1.0/24.

The route-policy sets the preference of this ASE route to 14.

In Huawei VRP, if a route-policy applied via preference ase route-policy matches a route, it modifies the preference value of the redistributed route when it is advertised.

By default:

OSPF ASE routes have a preference of 150.

But in this case, due to the policy applied, the preference is explicitly changed to 14 on R3 before re-advertising to R4.

So, R4 will install the route 10.1.1.0/24 from R3 with preference 14, assuming R2 doesn’t provide a better preference.

Reference from Huawei HCIP-Datacom-Core Technology Study Guide:

“You can control the preference of OSPF ASE routes by using a route-policy and applying it with the command preference ase route-policy. When the policy matches, the specified preference is used instead of the default (150).”

(Chapter: OSPF Advanced Features – Section: Route Control and Inter-AS Route Redistribution)

Comprehensive and Detailed Step-by-Step Explanation:

1. Overview of PBR (Policy-Based Routing):

Policy-Based Routing (PBR) allows you to override traditional routing decisions by defining user-specific policies.

Interface-Based PBR: Applied to packets arriving at a specific interface and affects traffic being forwarded through the device.

Local PBR: Applied to traffic generated by the local router itself (e.g., locally originated packets such as management traffic).

2. Analysis of Each Statement:

Option A: Interface-based PBR takes effect only for forwarded packets.

Correct (True Statement).

Interface-based PBR applies only to packets arriving at a specific interface and being forwarded through the router. It does not affect locally originated traffic.

Option B: Local PBR takes effect only for locally originated packets.

Correct (True Statement).

Local PBR specifically applies to traffic generated by the router itself, such as pings, SNMP requests, or routing protocol updates.

Option C: Interface-based PBR is configured on an interface and takes effect only for incoming packets on the interface.

Correct (True Statement).

Interface-based PBR is applied directly on the interface using commands like policy-based-route. It only affects traffic entering the specified interface.

Option D: Local PBR is configured in the protocol view.

Incorrect (False Statement).

Local PBR is not configured in the protocol view. It is typically configured using the command local-policy in the system view to handle traffic generated by the router.

3. Summary:

Correct Answer: D (Local PBR is NOT configured in the protocol view).

Huawei HCIA-Datacom Study Guide, Chapter "Policy-Based Routing."

Comprehensive and Detailed Step-by-Step Explanation:

DHCP Configuration Issues:

Option C: The DHCP function is disabled by default on Huawei devices. If the administrator forgets to enable it, clients cannot receive IP addresses.

Option D: DHCP uses broadcast messages, which do not traverse routers. If the clients and DHCP server are on different subnets, a DHCP relay agent must be configured.

Other Options:

Option A: Multiple DHCP servers can coexist as long as their IP address pools do not overlap. This is unlikely to cause the problem.

Option B: STP does not affect DHCP operations unless it delays port activation, which is uncommon in this scenario.

1 – Idle

2 – Connect

3 – OpenSent

4 – OpenConfirm

5 – Established

6 – Active

The BGP finite state machine defines how a BGP speaker transitions through various states when establishing and maintaining a BGP session. Below is the role of each state:

Idle (1) – BGP is waiting to start a connection. Initial state of the BGP process.

Connect (2) – BGP initiates a TCP connection to the peer.

OpenSent (3) – TCP connection is established; BGP sends an OPEN message and waits for one from the peer.

OpenConfirm (4) – BGP has received a valid OPEN message and is now expecting a KEEPALIVE.

Established (5) – BGP session is fully established; UPDATE messages can now be exchanged.

Active (6) – If the TCP connection fails in Connect state, BGP transitions to Active and will retry connection.

Reference from Huawei HCIP-Datacom-Core Technology Study Guide:

“BGP goes through the following states in order: Idle → Connect → Active → OpenSent → OpenConfirm → Established. The transition depends on the success or failure of TCP connection setup and BGP message exchanges.”

(Chapter: BGP Principles – Section: BGP State Machine)