Question 390
Following a supported configuration correction, the original issue was: A NETCONF RPC returns an `<rpc-error>` element but a script reports success because the SSH TCP session remained connected. Which observation verifies success?
Explanation
Correct Answer
A negative test captures the intended operation failure despite healthy transport and leaves the configuration unchanged. This confirms the approved response: Parse the NETCONF reply envelope and fail the operation when the RPC reports a relevant error. It is relevant because: Transport session success is not equivalent to NETCONF RPC completion or valid datastore modification.
Incorrect Answers
A safe fixture updates the intended keyed service instance and leaves similarly named entries untouched. This would validate ANOTHER scenario: A RESTCONF configuration client uses a full URI with a raw slash inside a YANG list key and accidentally addresses a different resource path. The specific correction here is: Parse the NETCONF reply envelope and fail the operation when the RPC reports a relevant error.
The intended interface change appears in the supported datastore and the controller reports successful RPC completion. This would validate 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. The specific correction here is: Parse the NETCONF reply envelope and fail the operation when the RPC reports a relevant error.
A controlled request succeeds over authenticated TLS while plaintext attempts are rejected. This would validate ANOTHER scenario: An operations client sends an unencrypted HTTP call to a management endpoint that requires TLS and reports a protocol failure as an unreachable routing prefix. The specific correction here is: Parse the NETCONF reply envelope and fail the operation when the RPC reports a relevant error.