350-501 · Question #85
Refer to the exhibit. This output is included at the end of an output that was provided by a device using NETCONF. What does the code show?
The correct answer is C. It shows NETCONF uses remote procedure calls. The XML output showing "<rpc-reply>" indicates that NETCONF communication is based on Remote Procedure Calls (RPCs), where client requests are RPCs and server responses are RPC replies.
Question
Refer to the exhibit. This output is included at the end of an output that was provided by a device using NETCONF. What does the code show?
Options
- AIt shows the hostname of the device as rpc-reply
- BIt shows that the running configuration is blank
- CIt shows NETCONF uses remote procedure calls.
- DIt shows that the full configuration is being modeled by VANG
How the community answered
(41 responses)- A5% (2)
- B2% (1)
- C90% (37)
- D2% (1)
Why each option
The XML output showing "<rpc-reply>" indicates that NETCONF communication is based on Remote Procedure Calls (RPCs), where client requests are RPCs and server responses are RPC replies.
"<rpc-reply>" is a NETCONF protocol element indicating a response to an RPC, not the hostname of the device.
The exhibit shows only the closing tag of an rpc-reply. It does not provide enough context to determine if the running configuration is blank; it only indicates the end of a response.
NETCONF is built upon Remote Procedure Calls (RPCs), where operations like retrieving configuration or executing commands are sent as XML-encoded RPC requests, and the device responds with XML-encoded RPC replies. The "<rpc-reply>" tag explicitly signifies such a response.
There is no information in the provided exhibit to suggest that the configuration is being modeled by "VANG"; this is an unsupported assertion.
Concept tested: NETCONF RPC structure
Source: https://www.rfc-editor.org/rfc/rfc6241#section-4
Topics
Community Discussion
No community discussion yet for this question.