Question 640
Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A RESTCONF client writes a string into a YANG enumeration field whose allowed values are explicitly limited. Which continuing control best reduces recurrence of this problem?
Explanation
Correct Answer
For this scenario, the observed situation is: A RESTCONF client writes a string into a YANG enumeration field whose allowed values are explicitly limited. The most directly supported response is: Supply a permitted enum value and validate against the current YANG schema before transmission. Technical basis: YANG type constraints restrict allowable values independently of XML or JSON syntax. Evidence of success: The device accepts the model-compliant value and rejects an invalid enum test. Ongoing protection: Generate tests for schema bounds and value types from the module definitions.
Incorrect Answers
The alternative guards against: SNMPv3 can provide authentication and privacy protections absent from common community-only SNMPv2c use. The root condition for this case is: YANG type constraints restrict allowable values independently of XML or JSON syntax. The focused prevention check is: Generate tests for schema bounds and value types from the module definitions.
The alternative guards against: TLS encryption alone does not prove peer identity without certificate validation. The root condition for this case is: YANG type constraints restrict allowable values independently of XML or JSON syntax. The focused prevention check is: Generate tests for schema bounds and value types from the module definitions.
That recurring practice manages a separate exposure: IPFIX supports template-defined flow fields whose interpretation can change by exporter. The present case instead depends on: YANG type constraints restrict allowable values independently of XML or JSON syntax. The suitable ongoing safeguard is: Generate tests for schema bounds and value types from the module definitions.