Quick Answer
The answer is `--restart=always`. This Docker run option ensures that a containerized web application automatically restarts after any unexpected exit, regardless of the exit code or reason for termination, including crashes or system reboots. The `always` policy is the most aggressive restart mode, designed for high-availability services that must recover without manual intervention. On the CompTIA Linux+ XK0-005 exam, this question tests your understanding of Docker container lifecycle management and the distinction between restart policies like `always`, `unless-stopped`, and `on-failure`. A common trap is confusing `always` with `unless-stopped`; remember that `always` will restart even if the container was manually stopped, while `unless-stopped` respects a manual stop. For the exam, a useful memory tip is: “Always means always—even if you stop it, Docker starts it back up.”
This XK0-005 practice question tests your understanding of scripting, containers and automation. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 DevOps engineer needs to ensure that a containerized web application always restarts automatically if the container exits unexpectedly. Which Docker run option should be used?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "always"
Why it matters: Absolute qualifier. An answer using 'always' is only correct if there are genuinely no exceptions — absolute statements are often wrong in networking.
--restart=on-failure
Why wrong: Only restarts if container exits with non-zero code.
--restart=unless-stopped
Why wrong: Restarts except when container is stopped manually.
--restart=no
Why wrong: No restart policy.
--restart=always
Always restarts regardless of exit status.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
--restart=always
The `--restart=always` policy ensures that the container restarts regardless of the exit code or reason for termination, including unexpected crashes. This is the correct choice for a containerized web application that must maintain high availability by automatically recovering from any unexpected exit.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
--restart=on-failure
Why it's wrong here
Only restarts if container exits with non-zero code.
--restart=unless-stopped
Why it's wrong here
Restarts except when container is stopped manually.
--restart=no
Why it's wrong here
No restart policy.
--restart=always
Why this is correct
Always restarts regardless of exit status.
Clue confirmation
The clue word "always" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
CompTIA often tests the subtle distinction between `--restart=always` and `--restart=unless-stopped`, where candidates mistakenly choose `unless-stopped` thinking it provides the same automatic restart but without the risk of restarting after a manual stop, missing that the requirement explicitly says 'always restarts automatically' regardless of how the container exits.
Detailed technical explanation
Docker's restart policies are implemented by the Docker daemon's container manager, which tracks the container's exit status and applies exponential backoff (starting at 100ms, doubling up to 1 minute) between restart attempts to prevent resource exhaustion. In production, `--restart=always` is often paired with `--stop-signal` and `--stop-timeout` to ensure graceful shutdowns before forced termination, avoiding data corruption in stateful services.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
What to study next
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
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise XK0-005 questions linked to Security.
Practise XK0-005 questions linked to Troubleshooting.
Practise XK0-005 questions linked to Scripting, Containers and Automation.
Practise XK0-005 questions linked to System Management.
Practise XK0-005 questions linked to XK0-005 fundamentals.
Practise XK0-005 questions linked to XK0-005 scenario.
Practise XK0-005 questions linked to XK0-005 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Scripting, Containers and Automation — This question tests Scripting, Containers and Automation — Read the scenario before looking for a memorised answer..
The correct answer is: --restart=always — The `--restart=always` policy ensures that the container restarts regardless of the exit code or reason for termination, including unexpected crashes. This is the correct choice for a containerized web application that must maintain high availability by automatically recovering from any unexpected exit.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "always". Absolute qualifier. An answer using 'always' is only correct if there are genuinely no exceptions — absolute statements are often wrong in networking.
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 30, 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.