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

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

In OSPF:

An NSSA (Not-So-Stubby Area) allows external route injection via Type 7 LSAs.

These Type 7 LSAs are generated by ASBRs inside the NSSA (R4 in this case) when external or direct routes are imported.

ABRs (such as R2) between the NSSA and backbone translate Type 7 LSAs into Type 5 LSAs for flooding into other areas.

Clarification of options:

A: Incorrect — default route is not involved here; it ' s a specific route (10.1.4.4/32).

B: Correct — R2 translates Type 7 LSAs into Type 5.

C: Incorrect — default route is not being advertised.

D: Correct — R4 imports a direct route and generates Type 7 LSAs for it.

Correct answers: B, D

Comprehensive and Detailed In-Depth Explanation:

By default, OSPF does not automatically associate a domain ID with a process ID. The concept of " domain ID " is primarily used when redistributing routes between OSPF and BGP, particularly in MPLS VPN scenarios. The domain ID in OSPF helps maintain loop prevention and correct route advertisement between different OSPF domains. You can manually configure the domain ID using the domain-id command within the OSPF process view, but it is not inherently set to the process ID.