220-1102 Operating Systems Practice Question
A technician is supporting a warehouse desktop. The immediate goal is to correct Linux file permissions. Which tool, control, or procedure is the best fit?
⚠ Common exam trap
Test-takers frequently confuse Windows administrative tools (like Local Users and Groups or Event Viewer) with Linux utilities, assuming a generic 'system tool' can manage permissions across both operating systems.
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
✓
chmod
The `chmod` command is the standard Linux utility for changing file permissions (read, write, execute) for the owner, group, and others. Since the goal is to correct Linux file permissions, `chmod` is the direct and correct tool for this task.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
chmod
Why this is correct
The `chmod` command directly modifies the file mode bits in the inode metadata, which controls read, write, and execute permissions for the owner, group, and others on a Linux filesystem. This satisfies the stem’s constraint of correcting file permissions on a warehouse desktop running Linux, as no other tool (e.g., `chown` for ownership or `umask` for defaults) alters the permission bits themselves.
- ✗
Local Users and Groups
Why it's wrong here
The Local Users and Groups snap-in (lusrmgr.msc) manages the local account database, including user credentials and group memberships, on a Windows system. While these determine the access token a user receives, they do not directly alter the file system mode bits stored in an inode; correcting a permission fault on a Linux warehouse desktop requires changing the permission bits themselves. Reassigning a user to a different group does not rewrite the existing file's owner/group/other execute flags, so this console cannot achieve the immediate goal.
- ✗
System Restore
Why it's wrong here
System Restore on Windows uses Volume Shadow Copy snapshots to roll back registry keys, system files, and installed drivers to a previous restore point. It does not inspect or modify the inode metadata containing read/write/execute permissions on a Linux filesystem, and restoring an earlier state could even overwrite unrelated system changes while leaving the file's mode bits untouched. This tool is fundamentally a Windows state-reversion mechanism, not a permission-editing utility, making it unsuitable for the needed fix.
- ✗
Event Viewer
Why it's wrong here
Event Viewer reads Windows event logs (Application, Security, Setup, and System) and is primarily used for diagnostic troubleshooting after an incident. It can show error codes or audit failures related to access denied, but it has no capability to set or change permission bits in a Linux inode; viewing log entries cannot adjust the file mode that governs access. Its role is to identify the symptom's source, not to act as a correction mechanism, so it cannot serve as the immediate fix.
Go deeper
Related to this question
About these practice questions
One of 925 original 220-1102 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 220-1102 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 220-1102 exam.