How does the Junos REST API handle configuration commits compared to NETCONF workflow behavior?
This correctly highlights the contrast between NETCONF's rigid RPC sequence and REST's resource-oriented transaction handling.
Why this answer
In NETCONF, changes are made to the candidate datastore and must be explicitly committed using the <commit> RPC. In the Junos REST API, configuration changes made via PUT, POST, or DELETE can either auto-commit depending on the API call parameters or require a separate commit action, but unlike NETCONF's explicit candidate/running model, REST abstracts transactions into resource endpoints where commit behaviors are managed via query parameters or dedicated commit endpoints.