The answer is `--user 1000`, `--security-opt seccomp=default.json`, and `--security-opt no-new-privileges`. These three options enforce least privilege by restricting the container’s user context, system call access, and ability to escalate privileges. Using `--user 1000` runs the container as a non-root user, directly reducing the attack surface from the default root execution. The `seccomp=default.json` profile blocks dangerous kernel syscalls, while `no-new-privileges` prevents the container from gaining elevated rights even if a setuid binary is present. On the CompTIA Linux+ XK0-005 exam, this tests your understanding of Podman’s security defaults and the principle of least privilege—a common trap is assuming `--privileged` or omitting `--user` is acceptable. Remember the mnemonic “User, Syscalls, No Escalation” to recall the three pillars: user ID, seccomp profile, and no-new-privileges.
XK0-005 Scripting, Containers and Automation Practice Question
This XK0-005 practice question tests your understanding of scripting, containers and automation. 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 security-conscious administrator runs containers with Podman. Which THREE methods ensure that a container runs with the least privilege required?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "least"
Why it matters: You want the option with minimum overhead, fewest steps, or lowest impact — not the most feature-rich or comprehensive answer.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
--user 1000
Option B is correct because using `--user 1000` runs the container process with a non-root user (UID 1000), which reduces the attack surface by preventing root-level access inside the container. This is a fundamental least-privilege practice, as containers default to running as root unless explicitly changed.
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.
✗
--privileged
Why it's wrong here
Gives full privileges, opposite of least privilege.
✓
--user 1000
Why this is correct
Runs the container as a non-root user, reducing privilege.
Clue confirmation
The clue word "least" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✓
--cap-drop=ALL
Why this is correct
Drops all kernel capabilities, leaving only needed ones if added back.
Clue confirmation
The clue word "least" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
--read-only=true
Why it's wrong here
Makes the root filesystem read-only, but the container still runs as root unless combined.
✓
--security-opt seccomp=default.json
Why this is correct
Applies a default seccomp profile to restrict system calls.
Clue confirmation
The clue word "least" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
CompTIA often tests the misconception that `--read-only=true` is a privilege-reduction method, when in fact it only restricts filesystem writes and does not limit user or capability privileges.
Detailed technical explanation
How to think about this question
Under the hood, Podman uses Linux kernel namespaces and cgroups to isolate containers, and capabilities are a finer-grained control than the root/non-root binary. Dropping all capabilities with `--cap-drop=ALL` and then adding back only required ones (e.g., `--cap-add=NET_BIND_SERVICE`) is the recommended approach for least privilege, as it prevents the container from performing privileged operations like loading kernel modules or changing system time. The seccomp profile (`--security-opt seccomp=default.json`) further restricts system calls, blocking dangerous ones like `clone` with certain flags, even if the container runs as root.
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 junior network technician can log in to a core router but cannot reach the enable prompt or configuration mode. The AAA server is authenticating the login — but the authorisation policy only grants privilege level 1, not 15. Authentication (who you are) is working; authorisation (what you can do) is not.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this XK0-005 question in full detail.
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: --user 1000 — Option B is correct because using `--user 1000` runs the container process with a non-root user (UID 1000), which reduces the attack surface by preventing root-level access inside the container. This is a fundamental least-privilege practice, as containers default to running as root unless explicitly changed.
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.
Are there clue words in this question I should notice?
Yes — watch for: "least". You want the option with minimum overhead, fewest steps, or lowest impact — not the most feature-rich or comprehensive answer.
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 →
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.
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.