ExamGecko
Home / CompTIA / XK0-005 / Practice Test 1
Ask Question

CompTIA XK0-005 Practice Test 1

Add to Whishlist
00:00:00
Show Answer
Report Issue   Restart test

Question 1 / 40

A Linux administrator is scheduling a system job that runs a script to check available disk space every hour. The Linux administrator does not want users to be able to start the job. Given the following:

CompTIA XK0-005 image Question 1 99642 10022024175436000000

The Linux administrator attempts to start the timer service but receives the following error message:

CompTIA XK0-005 image Question 1 99642 10022024175436000000

Which of the following is MOST likely the reason the timer will not start?

The checkdiskspace.timer unit should be enabled via systemctl.
The checkdiskspace.timer unit should be enabled via systemctl.
The timers.target should be reloaded to get the new configuration.
The timers.target should be reloaded to get the new configuration.
The checkdiskspace.timer should be configured to allow manual starts.
The checkdiskspace.timer should be configured to allow manual starts.
The checkdiskspace.timer should be started using the sudo command.
The checkdiskspace.timer should be started using the sudo command.
Comment (0)
Suggested answer: C
Explanation:

The most likely reason the timer will not start is that the checkdiskspace.timer should be configured to allow manual starts. By default, systemd timers do not allow manual activation via systemctl start, unless they have RefuseManualStart=no in their [Unit] section. This option prevents users from accidentally starting timers that are meant to be controlled by other mechanisms, such as calendar events or dependencies. To enable manual starts for checkdiskspace.timer, the administrator should add RefuseManualStart=no to its [Unit] section and reload systemd.

The other options are not correct reasons for the timer not starting. The checkdiskspace.timer unit does not need to be enabled via systemctl enable, because enabling a timer only makes it start automatically at boot time or after a system reload, but does not affect manual activation. The timers.target does not need to be reloaded to get the new configuration, because reloading a target only affects units that have a dependency on it, but does not affect manual activation. The checkdiskspace.timer does not need to be started using the sudo command, because the administrator is already running systemctl as root, as indicated by the # prompt. Reference: systemd.timer(5) - Linux manual page; systemctl(1) - Linux manual page

asked 02/10/2024
MIGUEL PARADA VAZQUEZ
37 questions