What happens to a candidate configuration after a commit?

When a commit operation is performed in the context of Juniper devices, the candidate configuration that has been modified becomes the active configuration. The process of committing involves validating and applying the changes made in the candidate configuration to the device's running configuration.

Once committed, these changes take effect immediately, allowing them to influence the behavior of the device. The active configuration is what the device uses to determine how to process traffic and perform its networking functions.

The other options describe scenarios that do not reflect the state of the configuration after a commit. For instance, the candidate configuration is not deleted or unchanged after a commit – it transitions into the active state instead. Moreover, although configurations can be propagated to other routers in specific configurations (like with synchronization in certain scenarios), this is not the default behavior during a commit and does not happen automatically across all routers in a network just because a commit is executed.