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

MP-BGP (Multiprotocol BGP) is an extension of BGP that supports multiple address families, including VPNv4 routes.

MP-BGP introduces a new BGP path attribute called MP_REACH_NLRI (for route advertisement) and MP_UNREACH_NLRI (for route withdrawal).

These attributes are used for:

Advertising VPNv4 and VPNv6 routes

Withdrawing unreachable VPNv4/VPNv6 routes

Supporting other AFI/SAFI combinations beyond IPv4 unicast

✅ Official Reference from Huawei:

" MP-BGP introduces MP_REACH_NLRI and MP_UNREACH_NLRI attributes to advertise or withdraw VPNv4/VPNv6 routes. "

— [Huawei HCIA-Datacom Certification Guide – BGP/MPLS VPN Section]

OSPF maintains Link-State Databases (LSDBs) that contain link-state advertisements describing the topology of an area. Router-LSAs are flooded within their originating area, allowing connected routers in that area to maintain synchronized topology information.

In the exhibit, the original R2–R3 connection is interrupted during the migration. R3 remains connected to R1 in Area 1, while R4 becomes connected to R2.

Because R4 receives R3 ' s backup configuration, both devices use the same OSPF router ID. However, their portions of Area 1 are separated by the disconnected link.

Therefore, R2 receives R4 ' s Router-LSA, while R1 receives R3 ' s Router-LSA.

R3 cannot receive R4 ' s area-scoped Router-LSA through the Area 0 connection, and R2 does not receive R3 ' s Router-LSA through the broken Area 1 path.

Thus, B and C are correct.

HCIP-Datacom-Advanced Routing & Switching Technology V1.0 Training Material.pdf

================

Comprehensive and Detailed In-Depth Explanation:

To verify the correct answer, we need to analyze Bidirectional Forwarding Detection (BFD) behavior and the provided configuration.

1. Understanding BFD Configuration Parameters

BFD (Bidirectional Forwarding Detection) is a protocol used for fast failure detection between directly connected devices.

Key Configuration Parameters in BFD:

Peer IP (bind peer-ip)

This specifies the destination router’s IP address for the BFD session.

✅ Correctly configured on both R1 and R2.

Discriminator Local/Remote (discriminator local X / remote Y)

These values must match between the two routers.

✅ Correctly configured (R1: local 1, remote 2; R2: local 2, remote 1).

Min-TX Interval (min-tx-interval)

Defines the minimum transmit interval for BFD packets.

❌ Missing from R2’s configuration (could be a cause for mismatch).

Min-RX Interval (min-rx-interval)

Defines the minimum receive interval for BFD packets.

❌ Missing from R2’s configuration (could be a cause for mismatch).

2. Analyzing the Configuration on R1 and R2

✅ Configuration on R1 (Correct)

shell

CopyEdit

bfd tor2 bind peer-ip 10.0.12.2

discriminator local 1

discriminator remote 2

min-tx-interval 1500

min-rx-interval 1500

This configuration is correct.

❌ Configuration on R2 (Incomplete)

shell

CopyEdit

bfd tor1 bind peer-ip 10.0.12.1

discriminator local 2

discriminator remote 1

Missing min-tx-interval and min-rx-interval.

3. Why the Answer is FALSE?

A BFD session does NOT go down due to mismatched timing parameters.

BFD dynamically negotiates timing values, meaning even if R2 is missing min-tx/min-rx values, the session should still establish.

However, the session will fail if the peer IP or discriminator values are incorrect (which they are NOT in this case).

The actual cause of failure in this case is likely the missing min-tx and min-rx settings on R2, NOT a mismatch between R1 and R2.

Yes, this is true. In OSPFv3:

Each router generates one Link-LSA per link.

The Link-LSA contains:

The router ' s link-local address

IPv6 prefixes associated with the interface

Options that are advertised to neighbors on the same link

It is not flooded throughout the OSPF area; it is only sent on the local link (similar to a Hello packet ' s behavior).

✅ Official Reference from Huawei:

" Each router sends a Link-LSA on every attached link. This LSA is not flooded beyond the link and includes link-local address, prefix list, and interface options. "

— [Huawei HCIA-Datacom OSPFv3 Chapter – LSA Types]

Link-LSA (ID 0.0.0.4):This LSA is originated by each router to describe its link-local IPv6 address and prefixes.The value 0.0.0.4 maps to the interface on R1, which has Router ID 10.0.1.1.✅ So the origin router is 10.0.1.1.

Network-LSA (ID 0.0.0.5):This LSA is generated by the DR on the link. In the diagram, R4 (10.0.4.4) is connected to the shared network (GE0/0/1).✅ So the origin router is 10.0.4.4.

Inter-Area-Prefix-LSA (ID 0.0.0.1):This LSA is used to describe routes from other areas and is generated by an ABR.In this case, R3 (Router ID 10.0.3.3) acts as the ABR.✅ So the origin router is 10.0.3.3.

Intra-Area-Prefix-LSA (ID 0.0.0.2):This references a Network-LSA, and the reference type is 1 (Network-LSA).Since the Network-LSA (0.0.0.5) came from 10.0.4.4, this also must have been generated by R4.✅ So the origin router is 10.0.4.4.

✅ Final Answer Summary:

Number

Origin Router

1

10.0.1.1

2

10.0.4.4

3

10.0.3.3

4

10.0.4.4

Official Huawei Extract:

" Each router in OSPFv3 generates Link-LSAs for each interface. The DR generates Network-LSAs. ABRs generate Inter-Area LSAs, and the Intra-Area-Prefix LSA references either Router or Network LSAs depending on the link type. "

— [Huawei HCIA-Datacom OSPFv3 LSAs Section]