H12-891_V1.0 Exam Dumps : HCIE-Datacom V1.0

Option B is incorrect because it falsely states that EBGP cannot be configured on Spoke-PE or Spoke-CE if the Hub-CE and Hub-PE run IGP. In reality, EBGP can still be used between Spoke sites and PE devices, regardless of the protocol between the Hub PE and CE. EBGP is often used for PE-CE communication, including in Hub-and-Spoke architectures.

Exact Extract - Huawei HCIE-Datacom VPN Section:

“In Hub & Spoke deployments, EBGP can be deployed between Spoke-CE and Spoke-PE. The choice of routing protocol between Hub-CE and Hub-PE does not limit this.”

MP-BGP is an extension of BGP-4 that supports multi-protocol address families such as IPv6, VPNv4, etc. When PE and CE exchange BGP routes, there is no need to create a BGP process per VPN on the CE. The CE typically runs a standard BGP process, while the PE maintains separate VPN routing tables (VRFs).

Exact Extract - Huawei HCIE-Datacom MP-BGP Chapter:

“CE devices use standard BGP, and multiple VPNs can share the same BGP process on the CE. The PE handles VPN route separation through VRFs and MP-BGP.”

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