Juniper PyEZ is a Python library that simplifies the management and automation of Junos devices. It is built on top of the NETCONF protocol. NETCONF utilizes a Remote Procedure Call (RPC) model to facilitate communication between a client (the automation script) and the server (the Junos device). PyEZ provides a framework that maps Python methods to the specific RPCs defined by the Junos XML API, allowing developers to execute operational commands and manage configurations without manually constructing the underlying XML RPCs.

A. REST API: PyEZ is fundamentally based on the NETCONF protocol, not the Junos REST API, which is a separate, HTTP-based interface for device management.

B. JET API: The Juniper Extension Toolkit (JET) is used for developing applications that run directly on the Junos device (on-box), whereas PyEZ is an off-box library.

D. XML API: While the Junos XML API defines the structure and vocabulary for the RPCs, the actual communication mechanism that PyEZ uses is the RPC model provided by NETCONF.

1. Juniper Networks TechLibrary, Junos PyEZ Overview. "Junos PyEZ is a microframework for Python that enables you to manage and automate devices running Junos OS. It enables you to connect to a Junos device over a NETCONF session and execute RPCs." (Source: Juniper Networks Official Documentation, Junos OS > Automation > Junos PyEZ)

2. Juniper Networks TechLibrary, Automation Scripting User Guide, Understanding the Junos XML API. "Client applications request information and control the configuration of a device running Junos OS by sending remote procedure calls (RPCs) to the Junos XML protocol server on the device... The Junos XML protocol server is integrated into the Junos OS and does not need to be downloaded separately." (Source: Juniper Networks Official Documentation, Junos OS > Automation > Automation Scripting)

3. Juniper Networks TechLibrary, NETCONF XML Management Protocol Developer Guide, NETCONF Session Overview. "The NETCONF protocol uses a remote procedure call (RPC) paradigm. A client encodes an RPC in XML and sends it to a server. The server responds with a reply that is also encoded in XML." (Source: Juniper Networks Official Documentation, Junos OS > Automation > NETCONF)