The correct answer is setting `--log-opt max-size=10m` when running the container and configuring journald to limit log storage. These two methods work together to prevent unbounded log growth in production: Docker’s `--log-opt max-size` truncates and rotates the container’s log file at a specified size, while journald’s `SystemMaxUse=` or `MaxRetentionSec=` directives in `/etc/systemd/journald.conf` cap the total disk space consumed by all journaled logs, including container stdout. On the CompTIA Linux+ XK0-005 exam, this question tests your understanding of container log management at both the runtime and system levels—a common trap is assuming only one method suffices, but production environments require both to avoid disk exhaustion. Remember the mnemonic “Docker cuts, journald caps” to recall that `log-opt` handles per-container rotation, while journald enforces a system-wide limit.
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 container produces a large amount of log output to stdout. Which TWO methods effectively manage log size in a production environment?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure journald limits for container logging
Option B is correct because journald can be configured to limit the size of log data it stores, including container logs that are sent to the journal. In a production environment, setting `SystemMaxUse=` or `MaxRetentionSec=` in `/etc/systemd/journald.conf` prevents unbounded log growth. Option E is correct because Docker's `--log-opt max-size=10m` truncates the container's log file when it reaches 10 MB, rotating it automatically, which directly manages log size at the container runtime level.
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.
✗
Use docker logs --tail 100 to limit output
Why it's wrong here
Only limits the display, not the stored log size.
✓
Configure journald limits for container logging
Why this is correct
Journald can be configured to cap log storage for containers.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use a bind mount to redirect logs to /dev/null
Why it's wrong here
Discards logs, which is not a management strategy and loses data.
✗
Configure the application inside the container to log to a file
Why it's wrong here
Changes logging destination but does not limit size.
✓
Set the --log-opt max-size=10m when running the container
Why this is correct
Limits the log file size per container using the log driver.
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 confuse `docker logs --tail` (a display filter) with actual log size management, or assume that redirecting logs to `/dev/null` is a valid production strategy, when in fact it destroys forensic data and violates operational best practices.
Detailed technical explanation
How to think about this question
Docker's logging drivers, such as `json-file`, support `max-size` and `max-file` options to rotate logs automatically, creating compressed archives when the size threshold is reached. Journald, when used as the logging driver (`--log-driver=journald`), relies on its own rate-limiting and size-based retention policies, which can be tuned via `journalctl --vacuum-size=` or persistent configuration. In high-throughput production systems, combining both approaches—setting `max-size` on the container and journald limits on the host—provides defense in depth against disk exhaustion.
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.
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: Configure journald limits for container logging — Option B is correct because journald can be configured to limit the size of log data it stores, including container logs that are sent to the journal. In a production environment, setting `SystemMaxUse=` or `MaxRetentionSec=` in `/etc/systemd/journald.conf` prevents unbounded log growth. Option E is correct because Docker's `--log-opt max-size=10m` truncates the container's log file when it reaches 10 MB, rotating it automatically, which directly manages log size at the container runtime level.
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 →
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.