YANG emerged in 2010 as a specialised data modelling language, originally defined to describe data sent over the NETCONF network management protocol. It provides a standardised framework for defining how network devices are configured and managed, enabling the detailed specification of network devices’ configuration, operational data, and policies in a structured, modular, and extensible manner. Think of YANG as a schema or blueprint that tells the network exactly what shape the configuration data should take before any protocol touches the device.
In the context of CCNP Enterprise, YANG connects structured data models with network-management operations, but a model is not itself a transport protocol or command language. Cisco IOS XE, IOS XR and NX-OS releases expose different combinations of native, IETF and OpenConfig YANG models; not every platform models every configurable feature, and a model’s presence does not guarantee its API operation is implemented. Engineers should check current software and model capabilities before automating routing, interface or security functions.
What NETCONF Protocol Does
NETCONF, specified in IETF RFC 6241, uses XML-based RPCs and is commonly transported over SSH on port 830. It provides operations to retrieve and change configuration and optional locking and transaction features, but a candidate datastore, confirmed commit and rollback are not universal: the server must advertise those capabilities. CLI systems can also provide platform-specific rollback facilities. Real change safety comes from supported datastores, validated payloads and explicit post-change verification, not an unconditional claim that one interface is always more reliable.
NETCONF get and get-config retrieve data, while edit-config changes a permitted configuration datastore. Copy-config, delete-config, lock and unlock are available only as supported by the server’s datastore capabilities and permissions. Optional :candidate, :startup and :confirmed-commit capabilities must be checked rather than assumed. When candidate is supported, an operator can stage and commit changes; other platforms may require carefully managed running-datastore edits and an external recovery plan. An RPC success response is not proof that traffic or the application recovered.
What RESTCONF Protocol Does
RESTCONF, specified in IETF RFC 8040, provides an HTTP-based interface to YANG-modeled resources and is normally protected using HTTPS. GET, POST, PUT, PATCH and DELETE have defined resource semantics, but POST does not universally mean creating any arbitrary top-level object, and whether an operation is permitted depends on the YANG schema, server implementation and authorization. Its familiar web API style may simplify a client, yet access control, supported revisions, validation and error handling remain just as important as transport convenience.
RESTCONF defines YANG-modeled JSON and XML representations, but RFC 8040 requires a server to support at least one encoding, not necessarily both. Check media-type support rather than assuming every device returns JSON by default. NETCONF’s RFC 6241 RPC protocol uses XML and may provide additional optional capabilities such as candidate and confirmed commit. Neither protocol is universally better: select from the operations, data models, datastores, authorization and transaction behavior the deployed software actually supports.
How the Three Connect
YANG, NETCONF and RESTCONF are related but not interchangeable. YANG models data structure, types, constraints and whether nodes represent configuration or operational state. NETCONF uses XML RPCs over its supported datastores, while RESTCONF exposes YANG-modeled resources through HTTP operations. Useful automation combines a supported model revision, an authenticated interface, a valid operation and verification of the actual device state. This prevents the mistaken expectation that a syntactically valid YANG-shaped payload always works across every vendor.
Cisco IOS XE, IOS XR and NX-OS support different sets of YANG modules, NETCONF services and RESTCONF functions by software version and platform. A capability exchange and YANG library can help establish which modules and datastores a particular device implements. Do not assume an identical JSON document, NETCONF RPC or model path works on all releases; unsupported features and authorization failures can return structured errors. Safe automation discovers those capabilities, tests a bounded change and checks the resulting operational state.
Where CCNP Exam Tests These
The 350-401 qualification path requires ENCOR 350-401 plus an eligible concentration. In ENCOR v1.2, the 15% Automation and Artificial Intelligence domain asks for high-level YANG principles and interpretation of API responses. The separate 10% Network Assurance domain explicitly requires candidates to configure and verify NETCONF and RESTCONF. These are distinct issuer task verbs, so don’t assign both exclusively to an imagined automation-only implementation domain. REST APIs knowledge supports them, while full model-driven script development is a deeper concentration topic.
The current 300-435 ENAUTO v2.0 is a 90-minute concentration recognized under CCNP Enterprise and CCNP Automation. Its five weighted domains are Network Automation Foundation 10%, Device-Level Network Automation 25%, Controller-Based Network Automation 30%, Operations 20%, and AI in Automation 15%. It names describing native/IETF/OpenConfig models, constructing JSON and XML payloads from YANG models, interpreting module trees, building Python ncclient or RESTCONF solutions and troubleshooting model-driven work. The scope also reaches controllers, telemetry, Jinja2, Ansible and AI-assisted automation; follow the current v2.0 blueprint rather than retired DevNet assumptions.
YANG Models Types Explained
There are three main categories of YANG models that appear in CCNP Enterprise study material, and distinguishing between them is important for both exam preparation and real-world application. The first category is native models, which are vendor-specific models written by Cisco for their own platforms. These models expose features and configuration options that are unique to Cisco devices and may not be available through any standardised model. Native models are often the only option for configuring advanced platform-specific features, but they sacrifice portability because they only work with Cisco devices.
IETF models are standardized through the Internet Engineering Task Force, while OpenConfig models provide operator-oriented interfaces. Neither guarantees identical operation across all manufacturers: module revisions, deviations, supported leaves and backend behavior can differ. Check the YANG library and use a read-only discovery test before relying on a multi-vendor workflow. ENAUTO v2.0 names native, IETF and OpenConfig models as descriptive knowledge and separately requires constructing valid payloads using actual model structure.
NETCONF Operations In Practice
A NETCONF-over-SSH session commonly begins with a <hello> exchange announcing protocol capabilities. Detailed supported YANG modules are discovered through the platform’s YANG library and related documentation; do not assume every module is advertised fully in the initial hello message. A Python ncclient workflow should check credentials, datastore availability and the intended model before sending get-config or edit-config RPCs. Capture request, response and device-state evidence, including structured errors.
The NETCONF get-config operation retrieves configuration from a specified datastore; edit-config attempts a change to an authorized target. The candidate datastore, confirmed-commit and rollback facilities are optional server capabilities rather than universal promises. With candidate support, staged changes can be validated and committed under the applicable locking and error-handling rules. Without it, engineers need a controlled update, recovery plan and operational verification. Even a successful RPC is not proof that the service or network forwarding recovered.
RESTCONF Practical Use Cases
RESTCONF can integrate with curl, Postman and Python HTTP clients, but a standards-compliant server is not required to implement both JSON and XML. Verify content negotiation, HTTPS/TLS, permissions, the YANG resource path and HTTP errors rather than assuming JSON is always the default. Platform-specific RESTCONF resources and transaction boundaries still matter; familiar web tooling does not eliminate the need for configuration diff, rollback planning and device-state verification.
A practical RESTCONF workflow on a Cisco IOS-XE device involves constructing a URL that identifies the specific resource being accessed, formatted according to the YANG model hierarchy. For example, retrieving the configuration of a specific interface would involve an HTTP GET request to a URL that encodes the device address, the RESTCONF root path, and the YANG module and container path that corresponds to interfaces. The response arrives as JSON or XML and can be parsed, processed, and acted upon programmatically. RESTCONF is also useful for building dashboards and monitoring tools that periodically poll device state and configuration data, because the HTTP request model is simple to implement in virtually any programming language.
Automation Domain Study Tips
ENCOR v1.2 divides YANG and protocol management between Network Assurance (10%), which requires configuring and verifying NETCONF and RESTCONF, and Automation and Artificial Intelligence (15%), which covers high-level data-model principles and API response interpretation. A full ncclient application is more specifically aligned with ENAUTO v2.0 than with every ENCOR exam question. Practice legitimate device configuration checks and basic protocol requests, and use Cisco’s current issuer task verbs to decide how far each study lab must go.
Cisco sandbox reservations and local virtual routers can provide useful legitimate practice, but image support, YANG modules, device features and access vary by platform and release. Begin with capability discovery, perform a read-only get-config or RESTCONF GET and then make a reversible controlled change if the server permits. Verify the actual operational result and log any errors. Building Python ncclient and RESTCONF solutions is valuable ENAUTO v2.0 preparation, but Cisco does not guarantee a particular live exam item format or an always-available free lab.
The significance of YANG, NETCONF, and RESTCONF extends well beyond passing a certification exam. Enterprises today are increasingly adopting software-driven network architectures, cloud integration platforms, and AI-enhanced monitoring tools, all of which rely on robust data models and standardised programmatic interfaces. A network engineer who can only configure devices through a CLI becomes a bottleneck in environments where hundreds or thousands of devices need consistent, auditable, and repeatable configuration management. Model-driven automation removes that bottleneck by enabling programmatic configuration workflows that scale without proportional increases in manual effort.
Model-driven automation can be valuable in infrastructure reliability and network engineering, but knowledge of YANG/NETCONF/RESTCONF does not guarantee hiring or future salary growth. Competence means checking implemented models, securing credentials, handling errors and verifying the effects of an intended change. Network automation skills are strongest when paired with routing fundamentals and operational change controls rather than treating a certification as proof of every production scenario.