Courseiva
AI and Network OperationsmediumMultiple SelectObjective-mapped

CCNA AI and Network Operations Practice Question

Which THREE statements accurately describe the characteristics of NETCONF and RESTCONF for programmatic network configuration?

⚠ Common exam trap

Cisco often tests the misconception that NETCONF uses HTTP methods like RESTCONF, leading candidates to incorrectly select option A as a correct statement about NETCONF.

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

NETCONF uses XML-encoded RPCs over a secure transport such as SSH or TLS.

NETCONF uses XML-encoded Remote Procedure Calls (RPCs) over a secure transport such as SSH or TLS, making option B correct. RESTCONF supports both XML and JSON encoding and uses standard HTTP methods (GET, POST, PUT, PATCH, DELETE), so option C is correct. Both NETCONF and RESTCONF rely on YANG data models to define the structure of configuration and operational data, confirming option D. Option A is incorrect because NETCONF does not use HTTP methods; that is a characteristic of RESTCONF. Option E is wrong because RESTCONF does not use a separate commit operation; changes are applied immediately with each HTTP request, unlike NETCONF's candidate config and commit model.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • NETCONF uses HTTP methods such as GET, POST, PUT, and DELETE to manipulate configuration data.

    Why it's wrong here

    NETCONF does not run over HTTP; it uses XML-based Remote Procedure Calls (RPCs) carried over a secure, connection-oriented transport such as SSH (port 830) or TLS. Operations like <get-config>, <edit-config>, and <commit> are exchanged as XML messages, not as HTTP GET/POST/PUT/DELETE requests. HTTP method semantics are specific to RESTCONF, which is a distinct protocol.

  • NETCONF uses XML-encoded RPCs over a secure transport such as SSH or TLS.

    Why this is correct

    NETCONF is a network management protocol that encodes all operations, such as <get>, <get-config>, and <edit-config>, as XML Remote Procedure Calls (RPCs). These RPCs are transmitted over a secure, connection-oriented transport: SSH is mandatory for NETCONF (RFC 6242), and TLS is supported as an alternative transport. This XML/RPC architecture differs fundamentally from RESTCONF's HTTP-based REST semantics.

  • RESTCONF supports both XML and JSON encoding and uses HTTP methods.

    Why this is correct

    RESTCONF is a RESTful protocol defined in RFC 8040 that leverages standard HTTP methods (GET, POST, PUT, DELETE, PATCH, HEAD, OPTIONS) to access YANG-defined data. It uses HTTP as the transport, thereby inheriting features like caching, authentication, and TLS security. Unlike NETCONF's XML-only encoding, RESTCONF supports both XML and JSON, allowing lighter-weight JSON for web-based tooling.

  • Both NETCONF and RESTCONF rely on YANG data models to define the structure of configuration and operational data.

    Why this is correct

    YANG is a data modeling language used to define the hierarchical structure of configuration and operational data for network devices. Both NETCONF and RESTCONF rely on YANG modules to describe the exact structure of the datastore, which can be queried or modified with protocol-specific operations. This common data model allows interoperability, as the same YANG module can be used with either protocol.

  • NETCONF uses a separate commit operation to apply changes, while RESTCONF uses a similar commit mechanism.

    Why it's wrong here

    NETCONF provides a candidate configuration datastore with a distinct <commit> operation (and optional <rollback>) to atomically apply a set of changes. RESTCONF, however, does not implement a separate commit phase; every HTTP request (e.g., POST, PUT, PATCH) directly modifies the intended running datastore immediately. Therefore, saying RESTCONF uses a similar commit mechanism is incorrect; RESTCONF cannot provide multi-change atomic transactions like NETCONF's candidate datastore.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The 200-301 exam frequently reuses these exact scenarios with slightly different constraints.

NETCONF uses XML-encoded RPCs over a secure transport such as SSH or TLS.Correct answer

Why this is correct

NETCONF is a network management protocol that encodes all operations, such as <get>, <get-config>, and <edit-config>, as XML Remote Procedure Calls (RPCs). These RPCs are transmitted over a secure, connection-oriented transport: SSH is mandatory for NETCONF (RFC 6242), and TLS is supported as an alternative transport. This XML/RPC architecture differs fundamentally from RESTCONF's HTTP-based REST semantics.

NETCONF uses HTTP methods such as GET, POST, PUT, and DELETE to manipulate configuration data.Wrong answer — click to see why

Why this is wrong here

NETCONF does not use HTTP methods; it uses XML-encoded Remote Procedure Calls (RPCs) over secure transports like SSH or TLS. HTTP methods are characteristic of RESTCONF, not NETCONF.

Why candidates choose this

Students may confuse NETCONF with RESTCONF, assuming both use HTTP methods since both are used for network configuration. The similar-sounding names and overlapping functionality can lead to this misconception.

NETCONF uses a separate commit operation to apply changes, while RESTCONF uses a similar commit mechanism.Wrong answer — click to see why

Why this is wrong here

RESTCONF does not have a separate commit operation; changes are applied immediately with each HTTP request (e.g., PUT or POST). NETCONF uses a distinct commit operation to apply candidate configuration changes, but RESTCONF lacks this mechanism.

Why candidates choose this

Students might assume that because both protocols use YANG models and serve similar purposes, they would share a commit mechanism. However, RESTCONF follows RESTful principles where each request is atomic and immediately applied.

Analysis generated from the official 200-301blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

About these practice questions

Courseiva writes every 200-301 question from scratch — 1,389 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This 200-301 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-301 exam.