nerdexam
Cisco

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.

Submitted by ricky.ec· Mar 6, 2026

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)
  • A
    90% (18)
  • B
    5% (1)
  • C
    5% (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</rpc>]]>]]>Correct

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.

B</rpc-reply>

`</rpc-reply>` is used to close a NETCONF *response* message sent by the server, not a *request* initiated by the client.

C</rpc>

While `</rpc>` closes the RPC element, it lacks the necessary `]]>]]>` end-of-message delimiter for proper NETCONF message framing.

D<rpc message.id="9.0"><notificationoff/>

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

#NETCONF#XML syntax#API request termination

Community Discussion

No community discussion yet for this question.

Full 350-401 Practice