Question 370
For an optical transport engineering team, operators addressed: Two providers exchange YANG model payloads that use identical local leaf names but different module namespaces, so parsing associates traffic counters with the wrong schema. What is the strongest acceptance evidence?
Explanation
Correct Answer
A fixture containing the two modules resolves both leaf values to their correct models without ambiguity. This confirms the approved response: Preserve the full module namespace and revision for each data path and parse namespace-qualified fields. It is relevant because: YANG namespaces and revisions give modeled nodes meaning beyond their unqualified display names.
Incorrect Answers
The targeted interface changes while other interfaces remain byte-for-byte unchanged. This would validate ANOTHER scenario: A YANG list declares an interface name as its key but a RESTCONF update sends a request to the list root without an instance identifier, modifying the wrong scope. The specific correction here is: Preserve the full module namespace and revision for each data path and parse namespace-qualified fields.
Counter retrieval succeeds and a controlled mutation remains rejected by schema or datastore rules. This would validate ANOTHER scenario: A network operator attempts to PATCH a YANG counter marked `config false`, then blames access control when the edit is rejected. The specific correction here is: Preserve the full module namespace and revision for each data path and parse namespace-qualified fields.
A compatibility test only edits leaves present in each device's advertised schema, with unsupported devices safely excluded. This would validate ANOTHER scenario: A controller deploys a single RESTCONF configuration template to devices running different firmware but fails when one model revision lacks the targeted leaf. The specific correction here is: Preserve the full module namespace and revision for each data path and parse namespace-qualified fields.