OpenConfig YANG separates config from state data
Short answer
A OpenConfig YANG is the vendor-agnostic model that keeps configuration and operational state in separate containers
Question
Key Takeaways
It tests recognition that OpenConfig is an open, multi-vendor YANG schema set whose
configandstatecontainers separate intended configuration from measured operational data.
This 300-610 question asks which data-modeling approach is vendor-neutral while splitting configuration from operational state. OpenConfig YANG (A) is the answer because its schemas keep config and state data in distinct containers.
Common mistake: Option D, IETF YANG, is tempting because YANG's `config` flag separates configuration from state, but IETF models are published by a standards body rather than delivered as the unified vendor-agnostic schema set the question describes; option C, native YANG, is inherently vendor-specific.
Expert Analysis
What the question is testing
The wording combines two requirements: the model must be vendor-agnostic (not tied to one vendor's CLI/data tree) and it must keep configuration data and operational/state data in separate containers. That pairing points to a specific YANG modeling style rather than to any YANG usage in general.
How the two data paths are separated
In a NETCONF/RESTCONF session the client edits the intended configuration and separately reads operational state. OpenConfig models formalise this split: configuration leaves sit under config containers flagged config true, while live counters, interfaces status and other measured values live under separate state containers that cannot be written. So a get-config operation touches only the config containers and a plain get returns the state containers — one request path for what an operator wants, another for what the device actually reports. That is exactly the "separate containers or models" behaviour described.
Why the other options fail
Option C, native YANG, is by definition vendor-specific: each vendor (Cisco NX-OS, IOS XR, etc.) publishes its own schemas, so it is not vendor-agnostic. Option D, IETF YANG, is standards-based and does distinguish config from non-config nodes through YANG's config statement, but its models are published by the IETF and do not deliver the vendor-neutral, unified schema set the phrase "vendor-agnostic programming model" refers to; a comment arguing for D on the basis of config/operational separation misses the first requirement. Option B, "open YANG", is not a recognised modelling framework — it is a distractor built from the word "open".
Conclusion
Option A, OpenConfig YANG, satisfies both conditions: it is developed by an open, multi-vendor community and its models explicitly segregate intended configuration from operational state data, which is why it is the answer used for this objective on the 300-610 exam.
Official Reference
This link opens the official vendor documentation in a new tab.
Exam Strategy
On data-modeling questions, treat the two qualifiers in the stem as a checklist: "vendor-agnostic" eliminates native/vendor YANG, while "separate containers for config and operational data" separates the remaining standards options. Read each option against both qualifiers instead of matching one familiar keyword; distractors such as "open YANG" often repackage a single word from the correct answer.
Frequently Asked Questions
Why is native YANG not vendor-agnostic?
How does OpenConfig keep configuration and operational state separate?
config containers and measured values under separate state containers. NETCONF get-config returns only configuration, while a plain get retrieves the operational state.Is IETF YANG a wrong answer for this question?
config statement to mark writable nodes, but it is not the unified, vendor-agnostic schema set described by the question. The combination of vendor-agnostic plus separate config/state containers identifies OpenConfig YANG.Community Votes
67% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 3
-
garza_javi 👍 1 Answered AOpenConfig YANG is a vendor-agnostic data modeling initiative designed to provide consistent network configuration and operational state management across different networking vendors. Its key characteristics include: - Vendor independence: Provides standardized data models across multiple manufacturers. - Separate data containers: Distinguishes between configuration data and operational state data. - Consistent interfaces: Supports network automation through protocols such as NETCONF and gNMI. - Structured modeling: Uses YANG to define configuration, state, and other network information.
-
Ayman_B 👍 1 Answered AA is correct .. CHATGPT is wrong OpenConfig YANG > they clearly separate intended configuration from operational state
-
Ayman_B 👍 1 Answered Daccording to CHATGPT : IETF YANG Clearly separate: config state (operational) do the answer is D
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.