A systemd host has no printers attached, yet cups.service is running and listening. Which TWO commands leave cups.service not started at the next boot? (Choose two.)

LPIC-1 Exam 102-500, objective 110. Security medium

Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.

Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.

How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.

The options

Choose 2.

Correct systemctl disable cups.service

Correct. disable removes the symlinks that the unit's [Install] section created under /etc/systemd/system, so nothing pulls the unit in at boot. The currently running instance keeps going until it is stopped or the machine reboots.

Correct systemctl mask cups.service

Correct, and stronger. mask symlinks the unit name to /dev/null, so it cannot be started at boot, by hand, or as another unit's dependency until it is unmasked.

Not correct systemctl stop cups.service

Wrong on its own. stop ends the running instance now but changes nothing on disk, so the enablement symlinks are still there and the service comes back at the next boot.

Not correct systemctl reload cups.service

Wrong. reload asks the running daemon to re-read its configuration, which is the ExecReload command in the unit. It neither stops the service nor alters whether it starts at boot.

Not correct systemctl kill cups.service

Wrong. kill sends a signal to the processes of the unit, by default SIGTERM to the main process. Like stop, it is a runtime action with no effect on boot-time enablement.

Why

systemd separates runtime state from boot-time enablement: start and stop act now, enable and disable act on the symlink farm that decides what runs at boot, and the combined form is systemctl disable --now. mask is the enablement lock, useful when a dependency of another unit would otherwise drag the service back in. Only mask survives a package upgrade that re-runs the vendor preset.

Where this comes from

Cited
manual page systemctl(1)

Practise this

Reading one question is not practice. The trainer will draw a short set from objective 110 and space the ones you get wrong.

Practise LPIC-1 Exam 102-500

More questions on this objective

All questions on Security

Practise LPIC-1 Exam 102-500