200-901 Network Fundamentals Practice Question
A network automation engineer is using `ncclient` to configure a Cisco IOS XE device via NETCONF. The engineer wants to retrieve the running configuration using the `<get-config>` operation with a source of `<running/>`. Which XML element must be included in the RPC to specify the data store?
⚠ Common exam trap
The trap here is mixing up the `<source>` and `<target>` elements, where source is used for reading with `<get-config>` and target is used for writing with `<edit-config>`.
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
✓
`<source><running/></source>`
The NETCONF `<get-config>` operation requires a `<source>` element to identify the configuration datastore to retrieve. The `<running/>` element within `<source>` selects the running configuration. Other elements like `<target>` are used for editing, `<config>` for edit payloads, and `<filter>` for narrowing results. The engineer must use `<source><running/></source>` to correctly specify the datastore for retrieval.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
`<target><running/></target>`
Why it's wrong here
The `<target>` element is used in edit-config operations to specify the datastore to modify, not to retrieve data. For `<get-config>`, the correct element is `<source>`. Using `<target>` in a `<get-config>` RPC would be invalid and likely result in an error. This option confuses the direction of the operation: target is for writing, source is for reading. Therefore, it is incorrect for retrieving configuration.
- ✓
`<source><running/></source>`
Why this is correct
In NETCONF, the `<get-config>` RPC requires a `<source>` element that identifies the configuration datastore to retrieve. The `<running/>` element inside `<source>` specifies the running configuration. This is defined in RFC 6241 and is mandatory for `<get-config>`. Without it, the server cannot determine which datastore to query. The engineer must include this exact structure to retrieve the running config successfully.
- ✗
`<config><running/></config>`
Why it's wrong here
The `<config>` element is used within `<edit-config>` to contain the configuration data being applied. It is not used in `<get-config>` to specify the datastore. In `<get-config>`, the datastore is specified via `<source>`. Including `<config>` would be structurally invalid for a retrieval operation. This option misplaces the element from a write operation into a read operation, making it incorrect for this scenario.
- ✗
`<filter><running/></filter>`
Why it's wrong here
The `<filter>` element is optional in `<get-config>` and is used to select a subset of the configuration, not to specify the datastore. It can contain XPath or subtree filters to limit the returned data. The datastore itself is always specified with `<source>`. Using `<filter>` to identify the running datastore is incorrect because filters refine the data after the source is chosen. This option confuses filtering with datastore selection.
Go deeper
Related to this question
About these practice questions
This 200-901 question is part of Courseiva's 975-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Cisco exam blueprint
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.