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?
Trap 1: Use the 'commit and-quit' command to apply changes.
Commit and-quit applies changes but no automatic rollback.
Trap 2: Use the 'commit check' command before committing.
Commit check only validates syntax; does not provide automatic rollback.
Trap 3: Use the 'rollback 0' command after committing.
Rollback 0 reverts to previous committed config, not a confirm mechanism.
- A
Use the 'commit and-quit' command to apply changes.
Why wrong: Commit and-quit applies changes but no automatic rollback.
- B
Use the 'commit confirmed' command with a timeout.
Commit confirmed provides automatic rollback if not confirmed.
- C
Use the 'commit check' command before committing.
Why wrong: Commit check only validates syntax; does not provide automatic rollback.
- D
Use the 'rollback 0' command after committing.
Why wrong: Rollback 0 reverts to previous committed config, not a confirm mechanism.