Quick Answer
The correct command is chmod 755 /var/log because this permission set (owner rwx, group r-x, others r-x) enforces the principle of least privilege for securing the log directory. The root owner retains full write access, the adm group gets read and execute permissions needed by tools like syslog or logrotate, and all other users are restricted to read-only access—eliminating the dangerous world-writable 777 setting flagged in the audit. On the CompTIA Linux+ XK0-005 exam, this question tests your understanding of standard Linux filesystem security and the specific roles of the adm group in log management; a common trap is confusing group write access with the need for only read/execute. Remember the memory tip: "755 keeps logs alive but only root can drive"—the first digit (7) gives the owner full control, while the trailing 55 locks out write access for everyone else.
This XK0-005 practice question tests your understanding of security. 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 security audit reveals that the /var/log directory has permissions 777. Which command should restore secure permissions, assuming the owner is root and group is adm?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "which command"
Why it matters: Tests specific CLI syntax. Recall the exact command and its required context — near-synonyms and partial matches are common distractors.
chmod 777 /var/log
Why wrong: World-writable, which is the current insecure state.
chmod 755 /var/log
Sets permissions to rwxr-xr-x, appropriate for a shared log directory.
chmod 700 /var/log
Why wrong: Only owner has access, too restrictive for system logs.
chmod 750 /var/log
Why wrong: Denies read access to others, which may break some services.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
chmod 755 /var/log
Option B is correct because /var/log typically contains sensitive system logs, and permissions of 755 (owner: rwx, group: r-x, others: r-x) allow the root owner full access, the adm group read/execute access (needed for log reading tools), and others read-only access without write permissions. This aligns with security best practices where only root should write to /var/log, and the 777 permission from the audit is overly permissive and a security risk.
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.
chmod 777 /var/log
Why it's wrong here
World-writable, which is the current insecure state.
chmod 755 /var/log
Why this is correct
Sets permissions to rwxr-xr-x, appropriate for a shared log directory.
Clue confirmation
The clue word "which command" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
chmod 700 /var/log
Why it's wrong here
Only owner has access, too restrictive for system logs.
chmod 750 /var/log
Why it's wrong here
Denies read access to others, which may break some services.
Common exam traps
The trap here is that candidates may choose 750 thinking it is more secure, but the XK0-005 exam expects the standard Linux permission of 755 for /var/log to maintain compatibility with common log-reading utilities and the adm group's intended read access.
Detailed technical explanation
Under the hood, Linux file permissions use a 3-digit octal mode where each digit represents owner, group, and others: 7 = rwx (4+2+1), 5 = r-x (4+0+1), 0 = ---. The /var/log directory often contains logs written by syslog-ng or rsyslog running as root, and the 'adm' group is traditionally used to grant read access to system administrators without giving them root privileges. In a real-world scenario, setting permissions to 755 ensures that log rotation scripts (logrotate) running as root can write new logs, while tools like 'journalctl' or 'tail -f /var/log/syslog' work for users in the adm group and others with read access.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Security — study guide chapter
Learn the concepts, then practise the questions
Security 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
Security — This question tests Security — Read the scenario before looking for a memorised answer..
The correct answer is: chmod 755 /var/log — Option B is correct because /var/log typically contains sensitive system logs, and permissions of 755 (owner: rwx, group: r-x, others: r-x) allow the root owner full access, the adm group read/execute access (needed for log reading tools), and others read-only access without write permissions. This aligns with security best practices where only root should write to /var/log, and the 777 permission from the audit is overly permissive and a security risk.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "which command". Tests specific CLI syntax. Recall the exact command and its required context — near-synonyms and partial matches are common distractors.
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.