350-401 · Question #718
An administrator is configuring NETCONF using the following XML string. What must the administrator end the request with?
The correct answer is A. </rpc>]]>]]>. NETCONF requests, encapsulated within an <rpc> tag, require a specific end-of-message delimiter for proper framing over a character-based transport like SSH.
Question
An administrator is configuring NETCONF using the following XML string. What must the administrator end the request with?
Options
- A</rpc>]]>]]>
- B</rpc-reply>
- C</rpc>
- D<rpc message.id="9.0"><notificationoff/>
How the community answered
(20 responses)- A90% (18)
- B5% (1)
- C5% (1)
Why each option
NETCONF requests, encapsulated within an `<rpc>` tag, require a specific end-of-message delimiter for proper framing over a character-based transport like SSH.
A NETCONF request, encapsulated within an `<rpc>` element, must be terminated with the `]]>]]>` character sequence after the closing `</rpc>` tag to signify the end of the message over a character-based transport like SSH.
`</rpc-reply>` is used to close a NETCONF *response* message sent by the server, not a *request* initiated by the client.
While `</rpc>` closes the RPC element, it lacks the necessary `]]>]]>` end-of-message delimiter for proper NETCONF message framing.
This is an opening `<rpc>` tag, indicating the start of a request or operation, not the termination of an existing request.
Concept tested: NETCONF message framing and termination
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/prog/configuration/1612/b_1612_programmability_cg/netconf_yang.html
Topics
Community Discussion
No community discussion yet for this question.