JNCIA-DevOps NETCONF And XML API Practice Question
What is the purpose of the <hello> element exchanged immediately after establishing a NETCONF SSH session?
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
✓
To exchange supported protocol capabilities and namespace identifiers.
The <hello> element is used by both client and server to exchange supported capabilities and session parameters.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
To exchange supported protocol capabilities and namespace identifiers.
Why this is correct
The <hello> element enables capability negotiation between client and server.
- ✗
To authenticate the SSH username and password.
Why it's wrong here
SSH authentication happens prior to the NETCONF subsystem startup and <hello> exchange.
- ✗
To request an immediate reboot of the Junos routing engine.
Why it's wrong here
Rebooting requires a dedicated <request-system-reboot> RPC.
- ✗
To lock the candidate configuration database automatically.
Why it's wrong here
Locking requires an explicit <lock> RPC.
About these practice questions
One of 307 original JNCIA-DevOps practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.