JN0-106 Routing Fundamentals Practice Question

Answer analysis

Option-by-option breakdown

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

• ✓

  Power cycle the device, interrupt the boot process by pressing the space bar when prompted, select the recovery option (option 2) from the boot menu, set the new root password and reboot.

  Why this is correct

  This is the correct order because root password recovery requires physical access to the console: power cycling to restart, interrupting the boot loader to access options, selecting recovery to boot into single-user mode, and then changing the password before rebooting.

• ✗

  Power cycle the device, press Ctrl+C during Junos kernel load to enter the boot loader, type 'boot -s' at the loader prompt, then set the new root password and reboot.

  Why it's wrong here

  This is incorrect because pressing Ctrl+C during kernel load does not reliably enter the boot loader; the correct method is to press the space bar when the 'Hit [Space] to halt boot' message appears. Also, 'boot -s' is not the standard boot loader command for Junos.

• ✗

  Connect via SSH, run 'request system root-authentication plain-text-password', enter the new password, then reboot the device.

  Why it's wrong here

  This is incorrect because the root password cannot be reset remotely if forgotten; physical console access is required. The command 'request system root-authentication' changes the password only when you already have root access, which is not the case here.

• ✗

  Boot the device normally, log in with any credentials, use 'cli' to enter CLI mode, run 'set system root-authentication plain-text-password', then reboot.

  Why it's wrong here

  This approach assumes you can authenticate at all, but the entire problem is that the root password is lost or unknown. On Junos, normal login requires valid credentials for any user with shell access, and if root's password is gone you cannot reach the CLI to run configuration commands. Furthermore, even if you somehow had another admin account, changing root's password from configuration mode would require superuser privileges (which typically come from root or a user in the super-user login class) — so this method is circular and does not address the recovery scenario. The actual recovery path bypasses normal authentication entirely by interrupting the boot loader and entering single-user mode, which is why this option is incorrect.

Go deeper

Related to this question