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

The scenario describes a mismatch in OSPF network types between two connected routers: one set to Point-to-Point (P2P) and the other set to Point-to-Multipoint (P2MP). While aligning Hello intervals may seem sufficient for establishing an OSPF neighbor relationship, the fundamental mismatch in network types introduces issues.

OSPF Network Types

P2P: Assumes a direct connection with a single neighbor, uses faster convergence and simpler LSDB synchronization.

P2MP: Supports multiple neighbors on a single interface, requiring different handling for DR/BDR roles and LSDB updates.

Impact of Network Type Mismatch

If Hello intervals are aligned, adjacency establishment might occur. However, mismatched network types affect neighbor role assignment and LSDB synchronization.

P2P expects a direct link and would handle updates differently than P2MP, which assumes multiple neighbors. This leads to inconsistencies in route calculation and forwarding.

HCIP-Datacom-Core Reference

OSPF Basics and Configuration​clearly outlines the criticality of consistent network type configuration for stable OSPF operation.

Lab examples in the HCIP Datacom Lab Guide​further demonstrate the consequences of such mismatches, including unstable neighbor states and incomplete LSDB synchronization.

Hence, the statement that neighbor relationships and LSDB synchronization remain unaffected is incorrect. Proper OSPF operation requires matching network types in addition to aligned Hello intervals.

The silent-interface command disables the sending of OSPF packets, including Hello packets, on the specified interface, which prevents the establishment of OSPF neighbor relationships. However, the interface can still advertise directly connected routes through other interfaces, making Option C incorrect ​.

 During WLAN roaming, the STA sends a Reassociation Request frame to the foreign AP to maintain connectivity. Association frames are used during initial connections, not roaming.

 APs with which a STA is associated before and after roaming can work on different channels, as roaming often occurs across channels in environments like multi-SSID or multi-channel setups.

Options C and D are false, as they contradict standard WLAN roaming procedures ​.

Comprehensive and Detailed Step-by-Step Explanation:

1. Understanding the Prefix List Configuration:

The command ip ip-prefix test index 10 permit 10.0.0.0 8 less-equal 32 defines the following:

The prefix base is 10.0.0.0 with a mask length of 8 bits.

The less-equal 32 condition allows routes with mask lengths ranging from 8 to 32 bits to match.

2. Analysis of Each Route:

Option A: 10.1.1.1/32

Correct.

The prefix 10.1.1.1/32 falls within the 10.0.0.0/8 network range and has a mask length of 32 bits, which satisfies the less-equal 32 condition.

Option B: 10.1.1.0/6

Incorrect.

The prefix 10.1.1.0/6 has a mask length of 6 bits, which is shorter than the base prefix length of 8. It does not satisfy the condition.

Option C: 10.1.1.0/24

Correct.

The prefix 10.1.1.0/24 falls within the 10.0.0.0/8 network range and has a mask length of 24 bits, which satisfies the less-equal 32 condition.

Option D: 10.0.0.0/16

Correct.

The prefix 10.0.0.0/16 falls within the 10.0.0.0/8 network range and has a mask length of 16 bits, which satisfies the less-equal 32 condition.

3. Summary:

The prefixes that match the configuration are 10.1.1.1/32, 10.1.1.0/24, and 10.0.0.0/16.

Huawei HCIA-Datacom Study Guide, Chapter "IP Prefix Lists."

Huawei Configuration Examples for ACL and Prefix Lists.

In asynchronous mode, the local device sends BFD control packets at predefined intervals, and the remote device monitors the receipt of these packets to detect connectivity issues. This is one of the two operating modes in BFD, the other being demand mode ​.

Comprehensive and Detailed in-depth Step-by-Step Explanation:

BGP confederations are used to reduce the complexity of IBGP full-mesh connections within a large AS by dividing the AS into multiple sub-ASs (called "member ASs") while still appearing as a single AS to external ASs. Below is an analysis of each option:

A. The ASs outside a confederation still consider the confederation as one AS:

This is true. Externally, the entire confederation is seen as a single AS, identified by the main AS number.

B. After a confederation is configured, the original IBGP attributes can be retained:

This is true. The configuration of a confederation does not affect the IBGP attributes exchanged between routers.

C. After a confederation is configured, the original AS number is used as the confederation ID of each router:

This is true. The main AS number is used as the Confederation Identifier for all member ASs in the confederation.

D. A confederation divides an AS into several sub-ASs, and EBGP full-mesh connections are established in each sub-AS:

This is false. Within each sub-AS of a confederation, IBGP connections are still used (not EBGP). Confederations are designed to reduce the number of IBGP full-mesh connections required within a large AS by creating smaller, manageable sub-ASs.

Therefore, the correct answer is D.

The Forwarding Information Base (FIB) is derived from the router's routing table and contains the exact forwarding entries used to route packets. It directly guides packet forwarding decisions by matching incoming packets with the correct output interface or next-hop address ​.

A is false – The default value of Local_Pref is 100, not 0.

B is false – Local_Pref is not advertised to EBGP peers, it is only sent to IBGP peers.

C is correct – The Local_Pref value stays constant unless modified by a route-policy or filter.

D is correct – Higher Local_Pref values indicate preferred paths, so BGP prefers the path with the highest Local_Pref among multiple options.

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

“Local_Pref is used to select the best outbound path for traffic leaving the AS. It is only shared among IBGP peers and defaults to 100. The higher the value, the more preferred the route.”

(Chapter: BGP Path Attributes – Section: Local Preference)

Comprehensive and Detailed Step-by-Step Explanation:

OSPF Route Preference Hierarchy:

OSPF uses the following preference order for route types when the prefix is the same:

Intra-area routes (D): Routes within the same OSPF area have the highest priority.

Inter-area routes (B): Routes between different OSPF areas are preferred after intra-area routes.

Type 1 external routes (A): External routes redistributed into OSPF, considering the internal OSPF cost to the ASBR.

Type 2 external routes (C): External routes redistributed into OSPF, ignoring the internal OSPF cost to the ASBR.

Lowest Priority:

Type 2 external routes (C) are given the lowest priority because they represent external information that does not consider internal OSPF costs.

The security policy specifies that traffic originating from 12.1.1.2 and destined for the untrust zone is permitted. Since the source address of the packet (12.1.1.1) does not match this rule, the packet matches the default implicit deny rule. However, rule 1 does not deny all other traffic explicitly, so the packet is forwarded based on further configurations ​.

For single-hop BFD (Bidirectional Forwarding Detection), the configuration must include the local and remote discriminators to uniquely identify the session endpoints. Additionally, enabling BFD globally is a prerequisite for initiating BFD sessions. Configuring multicast IP addresses is unnecessary for single-hop BFD, as it operates over direct links. Huawei's configuration guidelines specify these requirements to ensure effective deployment and operation of BFD​​.

 Understanding BFD (Bidirectional Forwarding Detection):

BFD is a protocol used to detect link faults quickly between two routers.

Single-hop BFD operates on directly connected links and is commonly used for fast fault detection in routing protocols like OSPF and BGP.

HCIP-Datacom-Core Technology Training Material (BFD Basics and Configuration)​​.

 Mandatory Configurations for Single-Hop BFD:

A. Configure the remote discriminator of a BFD session:The remote discriminator is used to uniquely identify the BFD session at the remote end. This is essential for session establishment.

B. Configure the local discriminator of a BFD session:The local discriminator uniquely identifies the BFD session at the local end. This is required to establish a BFD session.

D. Enable BFD globally:BFD must be enabled globally on the router for the protocol to operate and for session configurations to take effect.

 Optional Configuration:

C. Configure a multicast IP address for BFD:This is not required for single-hop BFD, as it operates over direct links using unicast communication. Multicast is used in other scenarios, like multi-hop BFD.

 Conclusion:The correct configurations for single-hop BFD are A, B, and D.

Comprehensive and Detailed Step-by-Step Explanation:

IS-IS Area Division:

IS-IS divides areas by routers, not by links. A router is assigned to a specific IS-IS area, but it can belong to multiple levels:

Level 1: Maintains the LSDB (Link State Database) for the local area only.

Level 2: Maintains the LSDB for the backbone area and exchanges routes between areas.

Behavior of a Level 1-2 Router:

A router configured as Level 1-2 must maintain two separate LSDBs:

One for intra-area routes (Level 1).

One for inter-area routes (Level 2).

Incorrect Statement:

The statement that an IS-IS router only needs to maintain the LSDB of its area is incorrect because Level 1-2 routers maintain LSDBs for both levels.

Comprehensive and Detailed Step-by-Step Explanation:

Bidirectional Forwarding Detection (BFD):

BFD is a lightweight protocol that provides rapid fault detection on links independent of the underlying routing protocol or media.

Requirements for BFD:

Both devices at the endpoints of the link must support and configure BFD for it to operate.

If one device does not support BFD, the feature cannot be used for link detection.