200-901 · Question #68
RESTCONF supports which three methods? (Choose three.)
The correct answer is B. patch C. put E. get. RESTCONF maps network configuration operations to standard HTTP methods including GET, PUT, and PATCH; lock, get-config, and edit-config are NETCONF RPC operations that do not exist in RESTCONF.
Question
RESTCONF supports which three methods? (Choose three.)
Options
- Alock
- Bpatch
- Cput
- Dget-config
- Eget
- Fedit-config
How the community answered
(30 responses)- A3% (1)
- B93% (28)
- F3% (1)
Why each option
RESTCONF maps network configuration operations to standard HTTP methods including GET, PUT, and PATCH; lock, get-config, and edit-config are NETCONF RPC operations that do not exist in RESTCONF.
lock is a NETCONF RPC operation used to lock a configuration datastore for exclusive access; RESTCONF has no equivalent lock operation as it relies on HTTP semantics.
PATCH is a valid RESTCONF method defined in RFC 8040 used to apply partial modifications to an existing resource without replacing it entirely.
PUT is a valid RESTCONF method that creates or fully replaces a target resource at a specified URI, directly mapping to the HTTP PUT semantic.
get-config is a NETCONF RPC operation for reading a specific datastore such as running or candidate; it does not exist in RESTCONF, which uses HTTP GET instead.
GET is a core RESTCONF method used to retrieve configuration or operational state data from a resource, mapping directly to the HTTP GET method.
edit-config is a NETCONF RPC operation for modifying configuration datastores; RESTCONF replaces this with HTTP methods such as PUT, POST, and PATCH.
Concept tested: RESTCONF HTTP methods versus NETCONF RPC operations
Source: https://www.rfc-editor.org/rfc/rfc8040
Topics
Community Discussion
No community discussion yet for this question.