352-001 · Question #741
Which three NETCONF datastores are valid? (Choose three)
The correct answer is A. Running C. Candidate E. Startup. NETCONF defines three datastores for managing device configuration: running, candidate, and startup. Other terms like capabilities and notifications refer to different NETCONF constructs.
Question
Which three NETCONF datastores are valid? (Choose three)
Options
- ARunning
- BCapabilities
- CCandidate
- DNotification
- EStartup
- FState
How the community answered
(42 responses)- A88% (37)
- B5% (2)
- D2% (1)
- F5% (2)
Why each option
NETCONF defines three datastores for managing device configuration: running, candidate, and startup. Other terms like capabilities and notifications refer to different NETCONF constructs.
The running datastore holds the current active configuration on the device and is mandatory in all NETCONF implementations per RFC 6241.
Capabilities in NETCONF are a set of advertised features exchanged during session establishment, not a datastore.
The candidate datastore is an optional NETCONF datastore that allows configuration changes to be staged and validated before being committed to the running datastore.
Notifications are a NETCONF mechanism for event-driven messaging from device to client, defined in RFC 5277, not a configuration datastore.
The startup datastore is an optional NETCONF datastore that stores the configuration loaded at device boot, distinct from the currently active running configuration.
State data in NETCONF (operational state) is read-only data accessible via get operations, not a named configuration datastore.
Concept tested: NETCONF datastore types per RFC 6241
Source: https://datatracker.ietf.org/doc/html/rfc6241#section-5.1
Topics
Community Discussion
No community discussion yet for this question.