Which statement describe the difference between OpenConfig and native YANG data models?

Native YANG data models are developed by a specific network device vendor, such as Cisco, Juniper, or Arista. They are designed to provide a complete and detailed representation of all the configuration and operational state data available on that vendor's specific platform and operating system (e.g., Cisco IOS XE). Because they are tightly coupled with the device's software, they expose all features, including proprietary ones, that are relevant only to that platform. This contrasts with OpenConfig models, which are vendor-neutral and developed by a consortium of network operators to ensure interoperability across different platforms.

A. This statement is incorrect because native models are, by definition, platform-dependent, not independent. Vendor-neutral models (like OpenConfig or IETF) are designed for platform independence.
B. Native models are developed and maintained by network vendors as part of their operating system development, not by individual, unaffiliated developers.
C. This statement incorrectly describes OpenConfig models. OpenConfig models are developed by network operators (not vendors) and are explicitly designed to be vendor-neutral, not platform-specific. ---

1. Cisco Systems

Inc.

"Programmability Configuration Guide

Cisco IOS XE Bengaluru 17.6.x

" Chapter: YANG Data Models.

Section: Cisco-Specific (Native) YANG Models: "Cisco-specific YANG models are also called native models. These models are generated from the Cisco IOS XE Software configuration and operational data... They are bound to the underlying device system

which is tied to a particular software release." This directly supports the answer that native models are vendor-developed and platform-specific.

2. Cisco Systems

Inc.

"YANG Data Models

" Cisco IOS XR Data Models Configuration Guide.

Section: Native Data Models: "Native models represent the complete feature set of the router. These models are vendor-specific

and are generated by Cisco." This confirms that native models are vendor-specific and cover the full feature set of the platform.

3. OpenConfig.

"OpenConfig

" openconfig.net.

About Section: "OpenConfig is an informal working group of network operators sharing the goal of moving our networks toward a more dynamic

programmable

and vendor-neutral footing." This source clarifies that OpenConfig models are operator-driven and vendor-neutral

directly contradicting option C.