Question 560
While investigating a network policy migration for fictional Cedarbridge Care Systems, the team reports: A RESTCONF PATCH request sends a bare CLI string as JSON and the IOS XE server rejects it as malformed model data. Which result most directly verifies that the proposed correction worked?
Explanation
Correct Answer
The device accepts the configured YANG node and a GET of the corresponding resource returns the intended model-shaped value. This directly verifies the related correction: Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths. It checks the technical distinction: RESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. Applied here, the relevant facts are: A RESTCONF PATCH request sends a bare CLI string as JSON and the IOS XE server rejects it as malformed model data. The question asks which result most directly verifies that the proposed correction worked.
Incorrect Answers
The proposed action belongs to the mechanism: This directly verifies the related correction: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations. Here the stated fault follows a different mechanism: This directly verifies the related correction: Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths. The corrective choice is “The device accepts the configured YANG node and a GET of the corresponding resource returns the intended model-shaped value”.
This alternative is a response to another technical cause: This directly verifies the related correction: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations. The reported case instead depends on: This directly verifies the related correction: Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths. The action that directly addresses it is “The device accepts the configured YANG node and a GET of the corresponding resource returns the intended model-shaped value”.
The proposed action belongs to the mechanism: This directly verifies the related correction: Refresh managed state and review a generated Terraform plan before applying only the intended network changes. Here the stated fault follows a different mechanism: This directly verifies the related correction: Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths. The corrective choice is “The device accepts the configured YANG node and a GET of the corresponding resource returns the intended model-shaped value”.