Which Junos API supports direct modification of the Ephemeral database?

The Juniper Extension Toolkit (JET) API is specifically designed for high-performance, programmatic interaction with Junos devices. It utilizes gRPC services to enable applications to directly and rapidly modify the ephemeral configuration database. This database is an alternate, non-validating datastore intended for fast configuration updates from automation tools and SDN controllers, bypassing the standard commit model for speed. The other listed APIs do not provide this direct modification capability for the ephemeral instance.

B. WebSocket: This API is primarily used for streaming telemetry and event notifications, not for modifying configuration databases.

C. SOAP: This legacy XML API interacts with the standard candidate and active configuration databases, not the ephemeral database.

D. REST: The Junos REST API is used to manage the standard configuration databases and does not offer direct, high-speed access to the ephemeral database.

1. Juniper Networks TechLibrary

"Understanding the Ephemeral Configuration Database". In the overview section

it explicitly states: "Applications can use the Juniper Extension Toolkit (JET) APIs or the NETCONF and Junos XML protocol to configure the ephemeral database." This directly links the JET API to the ephemeral database.

2. Juniper Networks TechLibrary

"Ephemeral Configuration Database User Guide". This guide provides a dedicated section titled "Configure the Ephemeral Database Using the JET API

" which details the process and confirms that JET is the intended tool for this function.

3. Juniper Networks TechLibrary

"Juniper Extension Toolkit (JET) Overview". The overview describes JET as a "rich set of APIs for control

management

and service planes" and highlights its use for "programmatic configuration of the device

" which includes the high-speed ephemeral database.