200-901 Understanding and Using APIs Practice Question
Which THREE of the following are valid NETCONF operations? (Choose three.)
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
<edit-config>
<edit-config> (A) is a valid NETCONF operation defined in RFC 6241; it loads all or part of a configuration into the specified target datastore (running, candidate, or startup) and is one of the core base protocol operations. <get-config> (C) is also a base NETCONF operation from RFC 6241; it retrieves all or part of a specified configuration datastore and is distinct from <get>, which returns both state and configuration data. <close-session> (E) is a valid NETCONF session-level operation from RFC 6241 that gracefully terminates the NETCONF session and releases any locks and resources held by the client. <rpc> (B) is not an operation but the transport-framing wrapper element that carries every NETCONF operation, and <commit> (D) is not a standalone NETCONF operation; committing the candidate datastore is performed via the <commit> element inside an <rpc> as part of the candidate capability, not as a base operation itself.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
<edit-config>
Why this is correct
`<edit-config>` is a standard NETCONF operation, defined in RFC 6241, that loads configuration data into a target datastore such as running or candidate. It satisfies the stem's requirement for valid NETCONF operations, unlike RESTCONF-specific verbs or SNMP primitives, making it one of the three correct choices.
- ✗
<rpc>
Why it's wrong here
<rpc> is the envelope, not an operation.
- ✓
<get-config>
Why this is correct
<get-config> is a base NETCONF operation that retrieves all or part of a specified configuration datastore, such as running or candidate. It returns configuration data only, unlike <get>, which also returns state and operational data.
- ✗
<commit>
Why it's wrong here
<commit> is part of candidate capability, not base operation.
- ✓
<close-session>
Why this is correct
<close-session> is a standard NETCONF operation, issued by the client to gracefully terminate an active NETCONF session and release associated resources. It belongs to the base protocol operations defined in RFC 6241, alongside <get>, <edit-config> and <lock>, so it satisfies the stem's requirement for a valid NETCONF operation.
Go deeper
Related to this question
About these practice questions
Courseiva writes every 200-901 question from scratch — 975 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 200-901 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-901 exam.