Bitzu

JN0-106 ยท The Junos CLI and configuration model

Rollback, save, load and compare

rollback 0-49, show | compare, save, load merge/override/replace/set, rollback and commit, and viewing the commit history.

Key points

  • Junos stores up to 50 committed configurations, numbered 0 (latest) to 49 (oldest). rollback n loads one into the candidate, and you still need commit to activate it. show | compare lists differences against the active configuration (+ added, - removed). save writes the configuration to a file; load merge, override, replace or set brings a file or typed text back in. show system commit lists the commit history.

Source: https://juniper.net/documentation/en_US/junos13.1/topics/task/configuration/junos-software-configuration-previous-version-restoring.html

Practice questions

Single choice

What is the highest rollback number Junos accepts?

  1. 9
  2. 10
  3. 49
  4. 99
Show answer

Answer: C. 49

Numbers run from 0 to 49, so 50 configurations are kept and 49 is the oldest.

Select all that apply

Which of these are valid load operations?

  1. load merge
  2. load override
  3. load set
  4. load append
  5. load copy
Show answer

Answer: A. load merge, B. load override, C. load set

merge, override and set are all load operations. append and copy do not exist.

True or false

Running 'rollback 1' in configuration mode immediately changes the active configuration.

Show answer

Answer: False

False. rollback 1 only loads the previous committed configuration into the candidate; nothing is active until you commit.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More JN0-106 topics in this module