Question 260
A core network change board wants to avoid: A RESTCONF configuration client uses a full URI with a raw slash inside a YANG list key and accidentally addresses a different resource path. Which ongoing safeguard fits best?
Explanation
Correct Answer
Include special-character and compound-key tests for RESTCONF clients. This helps prevent recurrence of the issue: A RESTCONF configuration client uses a full URI with a raw slash inside a YANG list key and accidentally addresses a different resource path. Acceptance evidence should be: A safe fixture updates the intended keyed service instance and leaves similarly named entries untouched.
Incorrect Answers
Require RPC reply and postchange readback checks for configuration jobs. That is a sensible control for ANOTHER scenario: A NETCONF RPC returns an `<rpc-error>` element but a script reports success because the SSH TCP session remained connected. It is less targeted to this issue than: Include special-character and compound-key tests for RESTCONF clients.
Discover NETCONF capabilities at every new device onboarding. That is a sensible control for ANOTHER scenario: A network controller sends NETCONF `edit-config` to a device but selects the candidate datastore on a platform that advertises running-only support. It is less targeted to this issue than: Include special-character and compound-key tests for RESTCONF clients.
Capacity-test subscription modes against real supported model leaves before large-scale activation. That is a sensible control for ANOTHER scenario: A provider subscribes to a gNMI counter in SAMPLE mode but expects only updates when the value changes, saturating the collector with unnecessary periodic messages. It is less targeted to this issue than: Include special-character and compound-key tests for RESTCONF clients.