XK0-004 · Question #450
An administrator schedules downtime on a system to find out why it takes so long to boot. Which of the following commands will help the administrator determine the issue with this system?
The correct answer is C. systemct1 status unit-files. Inspecting systemd unit file states with systemctl helps an administrator identify which services are enabled at boot and may be contributing to slow startup times.
Question
An administrator schedules downtime on a system to find out why it takes so long to boot. Which of the following commands will help the administrator determine the issue with this system?
Options
- Asystemd-analyze blame
- Bsyated-analyze time
- Csystemct1 status unit-files
- Dsystemct1 mask start
How the community answered
(32 responses)- B3% (1)
- C91% (29)
- D6% (2)
Why each option
Inspecting systemd unit file states with systemctl helps an administrator identify which services are enabled at boot and may be contributing to slow startup times.
systemd-analyze blame reports per-unit initialization timing but does not expose unit file enablement state or configuration issues that would reveal the root cause of a slow boot.
syated-analyze time is not a valid command; even the correct form systemd-analyze time returns only a high-level total boot duration, not per-unit file state details.
systemctl with the unit-files argument displays the enabled or disabled state of all systemd unit files, allowing an administrator to identify unnecessary or misconfigured services that load at boot. This view provides actionable configuration details needed to determine which services are causing the delay.
systemctl mask permanently disables a unit by symlinking it to /dev/null and is a remediation action, not a diagnostic command that provides boot performance information.
Concept tested: systemd boot diagnostics via unit file state inspection
Source: https://www.freedesktop.org/software/systemd/man/systemctl.html
Topics
Community Discussion
No community discussion yet for this question.