JNCIA-DevOps NETCONF And XML API Practice Question
When executing a NETCONF transaction on a Junos device, an automation script encounters an error or needs to discard changes made in the candidate datastore. Which THREE RPC elements or concepts apply to discarding or rolling back changes in Junos NETCONF workflows? (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
✓
Unlocking the configuration datastore using <unlock> ensures other administrators are not permanently locked out if a script terminates unexpectedly.
Junos NETCONF supports discarding candidate changes via <discard-changes>, rolling back committed configurations via rollback IDs in commit operations, and unlocking datastores upon error cleanup.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The <rollback-config> operation is a standalone top-level NETCONF protocol operation defined in RFC 6241.
Why it's wrong here
<rollback-config> is not part of RFC 6241; rollbacks in Junos are handled via commit parameters or proprietary extensions.
- ✗
The <abort> RPC can be used mid-transaction to cancel an active streaming configuration edit.
Why it's wrong here
The <abort> RPC is not used for candidate datastore reversion in standard Junos NETCONF; <discard-changes> is used instead.
- ✓
Unlocking the configuration datastore using <unlock> ensures other administrators are not permanently locked out if a script terminates unexpectedly.
Why this is correct
Using <unlock> releases the datastore lock, which is a best practice in robust script error-handling blocks.
- ✓
The <discard-changes> RPC is used to revert the candidate configuration to match the current running configuration.
Why this is correct
<discard-changes> discards all changes made in the candidate datastore since the last commit or lock.
- ✓
A commit operation can include a rollback parameter (e.g., <rollback>1</rollback>) to revert to a previous configuration checkpoint.
Why this is correct
Junos supports rolling back to previous numbered configurations during commit operations.
About these practice questions
This JNCIA-DevOps question is part of Courseiva's 306-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 August 2026 · checked against the official Juniper Networks exam blueprint
This JNCIA-DevOps practice question is part of Courseiva's free Juniper Networks 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 JNCIA-DevOps exam.