A network engineer wants to automate the backup of router configurations using Python and NETCONF. Which YANG model should the engineer use to access the running configuration?
Trap 1: urn:ietf:params:netconf:capability:rollback-on-error:1.0
This capability provides error rollback, not config retrieval.
Trap 2: urn:ietf:params:netconf:capability:candidate:1.0
Candidate capability allows using a candidate datastore, but for retrieval, any datastore works.
Trap 3: urn:ietf:params:netconf:capability:confirmed-commit:1.0
This capability enables confirmed commits, not retrieving config.
- A
urn:ietf:params:netconf:capability:rollback-on-error:1.0
Why wrong: This capability provides error rollback, not config retrieval.
- B
urn:ietf:params:netconf:capability:candidate:1.0
Why wrong: Candidate capability allows using a candidate datastore, but for retrieval, any datastore works.
- C
urn:ietf:params:netconf:capability:confirmed-commit:1.0
Why wrong: This capability enables confirmed commits, not retrieving config.
- D
urn:ietf:params:netconf:capability:xpath:1.0
Why wrong: XPath capability enables filtering, not required for full config retrieval.
- E
urn:ietf:params:netconf:capability:writable-running:1.0 [correct]
Why wrong: This capability allows writing to running, but retrieving is standard.