- A
Run 'systemctl mask myapp.service' to prevent manual stops.
Why wrong: Masking prevents the service from being started at all.
- B
Run 'systemctl enable myapp.service' to enable the service.
Correct: Enabling creates symlinks for automatic start at boot.
- C
Set 'Restart=on-failure' in the [Service] section of the service file.
Why wrong: This only restarts on failure, not on normal exit.
- D
Set 'Restart=always' in the [Service] section of the service file.
Correct: Restart=always makes the service restart regardless of exit reason.
- E
Add 'After=network.target' to the [Unit] section of the service file.
Why wrong: This only ensures ordering, not auto-start or restart.
LFCS Service Configuration Practice Question
This LFCS practice question tests your understanding of service configuration. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A system administrator needs to ensure that a custom service named 'myapp.service' starts automatically after a reboot and also restarts automatically no matter how the service stops, even if it exits normally. Which two actions should the administrator take? (Choose two.)
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
Run 'systemctl enable myapp.service' to enable the service.
To start automatically on boot, the service must be enabled via 'systemctl enable'. To restart on any exit, 'Restart=always' must be set in the service file. 'Restart=on-failure' does not cover normal exits; 'After' and 'mask' are irrelevant.
Key principle: Count usable hosts — not total addresses — and remember that the network and broadcast addresses are not available to hosts in standard IPv4 subnets.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Run 'systemctl mask myapp.service' to prevent manual stops.
Why it's wrong here
Masking prevents the service from being started at all.
- ✓
Run 'systemctl enable myapp.service' to enable the service.
Why this is correct
Correct: Enabling creates symlinks for automatic start at boot.
Related concept
CIDR notation defines the prefix length.
- ✗
Set 'Restart=on-failure' in the [Service] section of the service file.
Why it's wrong here
This only restarts on failure, not on normal exit.
- ✓
Set 'Restart=always' in the [Service] section of the service file.
Why this is correct
Correct: Restart=always makes the service restart regardless of exit reason.
Related concept
CIDR notation defines the prefix length.
- ✗
Add 'After=network.target' to the [Unit] section of the service file.
Why it's wrong here
This only ensures ordering, not auto-start or restart.
Common exam traps
Common exam trap: usable hosts are not the same as total addresses
Subnetting questions often tempt you into counting all addresses. In normal IPv4 subnets, the network and broadcast addresses are not usable host addresses.
Detailed technical explanation
How to think about this question
Subnetting questions test whether you can identify the network, broadcast address, usable range, mask and correct subnet. Slow down enough to calculate the block size correctly.
KKey Concepts to Remember
- CIDR notation defines the prefix length.
- Block size helps identify subnet boundaries.
- Network and broadcast addresses are not usable hosts in normal IPv4 subnets.
- The required host count determines the smallest suitable subnet.
TExam Day Tips
- Write the block size before choosing the subnet.
- Check whether the question asks for hosts, subnets or a specific address range.
- Do not confuse /24, /25, /26 and /27 host counts.
Key takeaway
Count usable hosts — not total addresses — and remember that the network and broadcast addresses are not available to hosts in standard IPv4 subnets.
Real-world example
How this comes up in practice
A network engineer segments a warehouse floor into three subnets: 20 scanners, 5 printers, and 2 management hosts. Picking the wrong mask wastes addresses or leaves too few usable hosts. Exam questions test whether you can apply CIDR notation, calculate block size, and identify the correct usable-host range for a given prefix.
What to study next
Got this wrong? Here's your next step.
Review block sizes, usable host formulas (2^n − 2), and how to find network and broadcast addresses for /24 through /30. Then practise related LFCS subnetting questions on CIDR, address ranges, and subnet selection.
- →
Service Configuration — study guide chapter
Learn the concepts, then practise the questions
- →
Service Configuration practice questions
Targeted practice on this topic area only
- →
All LFCS questions
513 questions across all exam domains
- →
Linux Foundation Certified System Administrator LFCS study guide
Full concept coverage aligned to exam objectives
- →
LFCS practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related LFCS practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
User and Group Management practice questions
Practise LFCS questions linked to User and Group Management.
Operation of Running Systems practice questions
Practise LFCS questions linked to Operation of Running Systems.
Essential Commands practice questions
Practise LFCS questions linked to Essential Commands.
Networking practice questions
Practise LFCS questions linked to Networking.
Service Configuration practice questions
Practise LFCS questions linked to Service Configuration.
Storage Management practice questions
Practise LFCS questions linked to Storage Management.
LFCS fundamentals practice questions
Practise LFCS questions linked to LFCS fundamentals.
LFCS scenario practice questions
Practise LFCS questions linked to LFCS scenario.
LFCS troubleshooting practice questions
Practise LFCS questions linked to LFCS troubleshooting.
Practice this exam
Start a free LFCS practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this LFCS question test?
Service Configuration — This question tests Service Configuration — CIDR notation defines the prefix length..
What is the correct answer to this question?
The correct answer is: Run 'systemctl enable myapp.service' to enable the service. — To start automatically on boot, the service must be enabled via 'systemctl enable'. To restart on any exit, 'Restart=always' must be set in the service file. 'Restart=on-failure' does not cover normal exits; 'After' and 'mask' are irrelevant.
What should I do if I get this LFCS question wrong?
Review block sizes, usable host formulas (2^n − 2), and how to find network and broadcast addresses for /24 through /30. Then practise related LFCS subnetting questions on CIDR, address ranges, and subnet selection.
What is the key concept behind this question?
CIDR notation defines the prefix length.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 24, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.