A network engineer needs to commit a configuration change but wants to ensure the change can be easily reverted if it causes issues. Which approach should the engineer take?
The 'commit confirmed' command with a timeout (e.g., 'commit confirmed 5') activates the configuration for a temporary interval, defaulting to 10 minutes. If the administrator does not issue a confirming 'commit' before the timer expires, Junos automatically rolls back to the previous configuration. This self-reverting behavior prevents permanent lockouts caused by misconfigured access settings.
Why this answer
The 'commit confirmed' command allows the engineer to commit a configuration change with a default timeout of 10 minutes (configurable). If the change causes issues and the engineer does not confirm the commit within the timeout period, Junos automatically reverts to the previous active configuration, providing a safe rollback mechanism.
Exam trap
The trap here is that candidates often confuse 'commit check' (syntax validation) with a rollback mechanism, or assume 'rollback 0' provides automatic reversion, when in fact it requires manual execution after the fact.
How to eliminate wrong answers
Option A is wrong because 'commit and-quit' is not a valid Junos command; the correct command is 'commit and-quit' to exit the configuration mode after committing, but it does not provide any automatic rollback capability. Option C is wrong because 'commit check' only validates the syntax and semantics of the candidate configuration without applying it; it does not allow reverting a change after it has been committed. Option D is wrong because 'rollback 0' reverts to the most recently committed configuration, but it must be issued manually after the change is already active, and it does not provide an automatic or timed rollback.