- A
`Restart=on-abort` and `MaxStartups=3`
Why wrong: MaxStartups is not a systemd directive.
- B
`Restart=on-failure` and `StartLimitBurst=5` and `StartLimitIntervalSec=60`
Why wrong: Burst count should be 3 and interval 30 seconds.
- C
`Restart=always` and `RestartSec=10`
Why wrong: This restarts indefinitely without a burst limit.
- D
`Restart=on-failure` and `StartLimitBurst=3` and `StartLimitIntervalSec=30`
This correctly limits restarts to 3 times within 30 seconds.
Quick Answer
The correct set of directives is `Restart=on-failure`, `StartLimitBurst=3`, and `StartLimitIntervalSec=30`. This combination works because `Restart=on-failure` ensures the service only restarts after a crash, not on normal stops, while `StartLimitBurst=3` and `StartLimitIntervalSec=30` together define the burst rate: systemd will allow up to three restart attempts within a 30-second window, and if that limit is exceeded, it automatically places the unit in a failed state—exactly matching the requirement to stop retrying. On the CompTIA Linux+ XK0-005 exam, this tests your understanding of systemd’s restart rate limiting, a common scenario for critical services where uncontrolled restart loops could mask deeper issues. A frequent trap is confusing `StartLimitBurst` with `RestartSec` or forgetting that `StartLimitIntervalSec` defaults to a 10-second window if omitted. Memory tip: think “3 strikes in 30 seconds, then you’re out”—the burst limit is like a baseball pitcher’s count, and exceeding it ends the game.
XK0-005 Scripting, Containers and Automation Practice Question
This XK0-005 practice question tests your understanding of scripting, containers and automation. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 Linux server runs a critical service managed by a systemd service unit. The administrator needs to configure the service to automatically restart if it crashes, but only up to 3 times within a 30-second window. If the service restarts more than 3 times in 30 seconds, systemd should stop attempting to restart and leave the service in a failed state. Which set of directives should be added to the [Service] section of the unit file to achieve this behavior?
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
`Restart=on-failure` and `StartLimitBurst=3` and `StartLimitIntervalSec=30`
Option D is correct because it uses `Restart=on-failure` to trigger a restart only when the service crashes (not on other stops), combined with `StartLimitBurst=3` and `StartLimitIntervalSec=30` to limit restarts to 3 attempts within a 30-second window. When the burst limit is exceeded, systemd automatically places the unit in a failed state, exactly matching the requirement.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
`Restart=on-abort` and `MaxStartups=3`
Why it's wrong here
MaxStartups is not a systemd directive.
- ✗
`Restart=on-failure` and `StartLimitBurst=5` and `StartLimitIntervalSec=60`
Why it's wrong here
Burst count should be 3 and interval 30 seconds.
- ✗
`Restart=always` and `RestartSec=10`
Why it's wrong here
This restarts indefinitely without a burst limit.
- ✓
`Restart=on-failure` and `StartLimitBurst=3` and `StartLimitIntervalSec=30`
Why this is correct
This correctly limits restarts to 3 times within 30 seconds.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse `Restart=always` (which restarts on any exit, including intentional stops) with `Restart=on-failure` (which only restarts on crashes), or they misremember the default values of `StartLimitBurst` and `StartLimitIntervalSec`, leading them to pick options with incorrect burst counts or intervals.
Detailed technical explanation
How to think about this question
Under the hood, systemd tracks restart attempts per unit using a counter that resets after `StartLimitIntervalSec` (default 10 seconds). The `StartLimitBurst` directive (default 5) defines the maximum number of starts within that interval; once exceeded, the unit transitions to a 'failed' state unless `StartLimitAction` is overridden (e.g., to reboot). In real-world scenarios, this prevents a flapping service from consuming resources or generating log noise, while still allowing transient failures to recover automatically.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the XK0-005 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Scripting, Containers and Automation — study guide chapter
Learn the concepts, then practise the questions
- →
Scripting, Containers and Automation practice questions
Targeted practice on this topic area only
- →
All XK0-005 questions
510 questions across all exam domains
- →
CompTIA Linux+ XK0-005 study guide
Full concept coverage aligned to exam objectives
- →
XK0-005 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related XK0-005 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Security practice questions
Practise XK0-005 questions linked to Security.
Troubleshooting practice questions
Practise XK0-005 questions linked to Troubleshooting.
Scripting, Containers and Automation practice questions
Practise XK0-005 questions linked to Scripting, Containers and Automation.
System Management practice questions
Practise XK0-005 questions linked to System Management.
XK0-005 fundamentals practice questions
Practise XK0-005 questions linked to XK0-005 fundamentals.
XK0-005 scenario practice questions
Practise XK0-005 questions linked to XK0-005 scenario.
XK0-005 troubleshooting practice questions
Practise XK0-005 questions linked to XK0-005 troubleshooting.
Practice this exam
Start a free XK0-005 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 XK0-005 question test?
Scripting, Containers and Automation — This question tests Scripting, Containers and Automation — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: `Restart=on-failure` and `StartLimitBurst=3` and `StartLimitIntervalSec=30` — Option D is correct because it uses `Restart=on-failure` to trigger a restart only when the service crashes (not on other stops), combined with `StartLimitBurst=3` and `StartLimitIntervalSec=30` to limit restarts to 3 attempts within a 30-second window. When the burst limit is exceeded, systemd automatically places the unit in a failed state, exactly matching the requirement.
What should I do if I get this XK0-005 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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 25, 2026
This XK0-005 practice question is part of Courseiva's free CompTIA 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 XK0-005 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.