Courseiva
Junos OS FundamentalseasyMultiple ChoiceObjective-mapped

JN0-106 Junos OS Fundamentals Practice Question

A junior network administrator is setting up a Juniper MX router for the first time. After powering on the device, the administrator notices that the LED on the front panel blinks amber and the device does not complete the boot process. The console displays messages reporting file system errors. The administrator has no previous configuration changes and the device was shipped with factory defaults. Which action should the administrator take to resolve the boot issue?

⚠ Common exam trap

Many candidates confuse a boot failure due to file system corruption with a password issue or a need to reinstall the OS, but the amber LED and file system error messages point directly to a corrupted file system that can be repaired with fsck in single-user mode.

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

Boot into single-user mode and run file system checks.

The amber blinking LED and file system errors indicate a corrupted file system, which is common on factory-default devices if the flash memory was not properly initialized. Booting into single-user mode (option A) allows the administrator to run 'fsck' (file system check) to repair the root file system without loading the full Junos OS, which is the standard recovery procedure for such boot failures.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Boot into single-user mode and run file system checks.

    Why this is correct

    Entering single-user mode (e.g., by interrupting the boot process at the U-Boot loader and issuing `boot -s`) provides a maintenance shell before normal Junos processes start. From there, you can manually run filesystem consistency checks with `fsck` (or `check`) on the root and /var partitions. Repairing corrupted metadata in this mode is the standard first-line recovery step for a device that fails to boot cleanly, as it addresses the underlying filesystem errors without the risk of an immediate full reinstall.

  • Perform a password recovery procedure to gain access.

    Why it's wrong here

    The password recovery procedure, initiated at the boot loader (such as choosing the `recovery` option or sending break), resets the root password to blank and restores password recovery capability; it does not modify or repair filesystem data. Boot failures are typically caused by corrupted driver metadata, unsupported file structures, or power failures causing inconsistent journals, none of which are addressed by clearing authentication credentials. In fact, running password recovery may even cause configuration loss if not carefully backed up, making it an inappropriate and potentially harmful first response.

  • Use the 'request system software add' command from the boot loader.

    Why it's wrong here

    The `request system software add` command is a Junos CLI command that runs only from an operational shell, not from the boot loader. The U-Boot stage offers a limited set of commands — such as `boot`, `load`, and `go` — and has no access to the Junos CLI or its package management system. Attempting this action from the boot loader is therefore syntactically impossible; software installation or upgrade would require booting into the main system or using a different recovery method.

  • Reinstall the Junos OS using a USB flash drive with the software image.

    Why it's wrong here

    Reinstalling Junos from a USB image is a high-impact, last-resort action that overwrites the entire filesystem layout and should never be chosen before attempting lightweight repair steps. Modern Junos devices include hidden rescue and backup partitions that can often be booted after a corruption event, which is both faster and less disruptive than a USB install. Even when a fresh install is ultimately required, you should first perform a filesystem check to confirm that corruption is the actual cause and to attempt to salvage configuration or log data.

Visual reference

Client Recursive Resolver Root DNS (13 root servers) TLD DNS (.com, .org, …) Authoritative example.com query IP addr answer

About these practice questions

One of 156 original JN0-106 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

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.