LFCS Service Configuration Practice Question
A Linux administrator is configuring a custom systemd service that must not start until a network share is mounted. The mount is managed by a systemd mount unit named mnt-data.mount. Which directive should be added to the [Unit] section of the service unit to enforce this ordering?
⚠ Common exam trap
Many candidates confuse a dependency directive like Requires= with an ordering directive like After=, assuming that requiring a unit also ensures it starts first.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
After=mnt-data.mount
The service must wait for the mount unit to be active before starting. The After= directive explicitly defines ordering, ensuring the service starts only after mnt-data.mount has activated. Requiring the mount alone does not guarantee order, and Before= would reverse the desired sequence.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Before=mnt-data.mount
Why it's wrong here
Before= does the opposite: it orders the service to start before mnt-data.mount. That would mean the service attempts to start before the mount is available, likely causing it to fail if it accesses the mount point. This is not the desired behavior.
- ✓
After=mnt-data.mount
Why this is correct
After= ensures that the service starts only after mnt-data.mount has finished activating. This is the correct directive for ordering, as it tells systemd to delay the service start until the specified unit is active, which is exactly what is needed for the mount to be available.
- ✗
Wants=mnt-data.mount
Why it's wrong here
Wants= creates a weak dependency, meaning systemd will try to start mnt-data.mount when the service starts, but it does not enforce ordering. The service could still start before the mount is active, so it does not guarantee the required sequence.
- ✗
Requires=mnt-data.mount
Why it's wrong here
Requires= establishes a hard dependency: if mnt-data.mount fails to activate, the service will not start. However, it does not enforce ordering, so the service could attempt to start before the mount is active, causing failures if the service accesses the mount point prematurely.
Go deeper
Related to this question
About these practice questions
One of 406 original LFCS practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Linux Foundation exam blueprint
This LFCS practice question is part of Courseiva's free Linux Foundation certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the LFCS exam.