Huawei H12-891_V1.0 Exam With Confidence Using Practice Dumps

In MPLS LDP, there are two types of sessions:

Direct LDP sessions: Established between directly connected LSRs using LDP Hellos over a link.

Remote LDP sessions (also called targeted LDP sessions): Established between non-directly connected LSRs. These require manual configuration of the remote peer.

In this scenario, SWA and SWC are not directly connected, so a remote (targeted) LDP session must be set up.

For a remote LDP session:

You must configure the remote peer using the command:

[SWA-MPLS-LDP] targeted-peer x.x.x.x

Where x.x.x.x is the LSR ID of SWC (33.3.3.3 in this case).

The current configuration does not include this required step.

Thus, the correct statement is:

D. You need to create a remote peer and specify an LSR ID for the remote peer.

Comprehensive and Detailed In-Depth Explanation:

During a network migration test, it is crucial not only to verify that the network itself is functioning correctly but also to ensure that upper-layer application services are running properly on the newly migrated network. Migration testing aims to confirm that the transition has not disrupted service functionality.

Option A and C focus solely on network performance, which is necessary but insufficient.

Option B refers to command outputs, which are technical checks and do not guarantee service continuity.

Option D correctly identifies that successful migration is indicated by proper operation of upper-layer application services, as the primary purpose of a network is to support these applications.

NETCONF defines datastores to manage device configurations:

running: Active configuration in use

candidate: Staging area for changes before applying

startup: Configuration loaded on reboot

NETCONF operations:

< commit > : Applies changes from candidate → running → ✅

< delete-config > : Deletes a specified datastore (e.g., startup) → ✅

< validate > : Validates syntax/logic in the candidate datastore → ✅

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

Correct answer: D