Question 500
In a Linux incident, an engineer reports: A service must not start until its database network mount is available. What is the correct interpretation?
Explanation
Correct Answer
A bare After= directive does not by itself guarantee the dependency exists. This explains the symptom rather than a coincidental service condition. Verification: The service starts only after its required mount is ready.
Incorrect Answers
Disable only removes automatic enablement and does not prohibit manual starts. That can explain why an emergency policy must prevent any dependency from starting a dangerous service, whereas the current evidence supports unit ordering and requirement dependencies can express startup constraints.
The alternative describes systemd-analyze critical-chain shows service ordering on the boot path, which is relevant when a host boots slowly and operations wants to identify its critical startup chain. It does not explain this case because a bare After= directive does not by itself guarantee the dependency exists.
Running now is not the same as being enabled for future boots. That can explain why an administrator starts a systemd service but it does not start automatically after reboot, whereas the current evidence supports unit ordering and requirement dependencies can express startup constraints.





CompTIA Linux+ (XK0-006) Practice Tests