Rebooting through systemd | LinuC Level 1 101 Exam original practice question

1.01.3Basic

Restart a system managed by systemd through the normal shutdown path.

Which command is appropriate?

Hint 1: Focus on the requirement

Select the systemd action that requests a managed reboot rather than stopping PID 1 directly.

Hint 2: Key terms

Review the short definitions before comparing the boot and systemd choices.

systemctl reboot: A systemctl action that requests an orderly reboot through systemd.
Managed reboot: A reboot coordinated by the init system after service and filesystem shutdown work.
Systemd transaction: The set of ordered unit operations systemd performs for a requested action.
PID 1: The system process that coordinates service lifecycle and shutdown.

Detailed explanation

Correctsystemctl reboot

Correct. systemctl reboot requests a normal system restart.

Incorrectsystemctl halt --restart

Incorrect. halt --restart is not the standard systemctl syntax.

Incorrectsystemctl isolate reboot.service

Incorrect. reboot.service is not normally isolated as a target this way.

Incorrectsystemctl stop systemd

Incorrect. Stopping systemd directly would break system management.

An example you can run in a temporary verification environment.

systemctl reboot --help 2>/dev/null | head || true

rebootのhelp。再起動は行わない

Environment: systemctl helpのみ
Use read-only commands or a disposable Linux instance when checking boot metadata.
Exact unit names and command output can vary slightly by distribution.

Foundation review

A managed reboot follows the systemd shutdown path instead of treating the init process like an ordinary service.

Confirm users, jobs, updates, and redundancy before requesting a reboot.

Question IDKL-101-347

Environmentsystemctl helpのみ

Last technical review2026-08-13

More practice in this area