Junos Rescue Configuration: Saving and Loading
A network engineer accidentally committed a configuration on a Juniper router that caused a loss of management access via SSH and SNMP. The engineer has console access and the device is still operational. Before the change, the engineer had saved a rescue configuration using 'request system configuration rescue save'. Which action should the engineer take to restore management access most quickly?
Quick Answer
The answer is to execute 'rollback rescue' from configuration mode and then commit. This is correct because the 'request system configuration rescue save' command stores a known-good configuration snapshot that can be instantly recalled using 'rollback rescue', which replaces the active candidate configuration with the rescue configuration without requiring a reboot. On the JNCIA-Junos exam, this scenario tests your understanding of Junos rescue configuration recovery methods when management access is lost but console access remains—a common trap is thinking you need to reboot or load a previous file, but the rescue configuration is the fastest path since it bypasses the need for network access. Remember the memory tip: "Rescue is the rollback that saves your back."
⚠ Common exam trap
It's easy for candidates to confuse 'rollback rescue' with a boot-time recovery mechanism, assuming the rescue configuration loads automatically on reboot, when in fact it requires a manual command after the device is operational.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
At the shell prompt, execute 'cli -c "rollback rescue"' and then commit.
The 'request system configuration rescue save' command stores a rescue configuration that can be rolled back to using 'rollback rescue' in configuration mode. Since the engineer has console access, they can enter configuration mode and execute 'rollback rescue' followed by 'commit' to instantly revert to the last known working configuration, restoring SSH and SNMP access without requiring a reboot.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
At the shell prompt, execute 'cli -c "rollback rescue"' and then commit.
Why this is correct
This loads the rescue configuration without rebooting.
- ✗
At the configuration mode, execute 'rollback 0'.
Why it's wrong here
This rolls back to the previously committed configuration, not rescue.
- ✗
Power cycle the device; it will automatically boot with the rescue configuration.
Why it's wrong here
Rescue configuration is not automatically loaded at boot.
- ✗
Reboot the device and press the space bar to load the rescue configuration.
Why it's wrong here
Pressing space bar enters the boot loader, not rescue config; rescue is not automatically loaded.
Go deeper
Related to this question
About these practice questions
Courseiva writes every JN0-106 question from scratch — 156 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on JN0-106
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Which TWO statements about the rescue configuration are correct? (Choose two.)
hard- A.The rescue configuration is automatically saved after every commit.
- B.The 'rollback rescue' command loads the factory-default configuration.
- ✓ C.The rescue configuration is designed to provide a method of last-resort recovery.
- ✓ D.The rescue configuration can be saved by issuing the 'request system configuration rescue save' command.
- E.The rescue configuration can be used to restore only a subset of the configuration.
Why C: The rescue configuration is explicitly designed to provide a method of last-resort recovery. It allows an administrator to save a known-good configuration that can be loaded even if the active configuration becomes corrupted or inaccessible, ensuring the device can be brought back to a functional state.
Variation 2. Which TWO statements about configuration storage in Junos are true?
easy- ✓ A.The rescue configuration is stored in /config/rescue.conf.gz.
- B.The rollback configurations are stored in /config/juniper.conf.0.gz, .1.gz, etc.
- ✓ C.The active configuration is stored in /config/juniper.conf.gz.
- D.The candidate configuration is stored in /config/.
- E.The factory default configuration is stored in /etc/config/.
Why A: The rescue configuration is stored as a compressed file at /config/rescue.conf.gz on Junos devices. This configuration is saved using the 'request system configuration rescue save' command and can be loaded with 'rollback rescue' to recover from a configuration that prevents the device from booting properly.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This JN0-106 practice question is part of Courseiva's free Juniper Networks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the JN0-106 exam.