Operating Systems and File Management
Operating Systems and File Management tests your understanding of what an OS controls, how files and folders are organised, and how paths and file operations work. Questions often ask you to identify an OS function, interpret a file path, or choose the safe file-management action.
Core rules and concepts
- An OS manages processes, memory, files, devices and users. The kernel runs in privileged mode; the GUI and CLI are interfaces for users.
- A file system arranges files in a hierarchy. An absolute path starts from the root; a relative path starts from the current folder.
- Extensions such as .docx, .jpg or .exe suggest file type, but content and associated application determine actual behaviour.
- Copy leaves the original in place; move removes it from the source. Delete may send a file to the Recycle Bin, while permanent deletion bypasses it.
- Permissions control read, write and execute access. Backups protect against deletion, corruption and device failure.
Worked example
The path C:/Users/Ravi/Documents/report.docx is absolute. Drive C: is the root volume; Users, Ravi and Documents are folders; report.docx is the file; .docx is the extension. A relative path such as Documents/report.docx depends on the current folder. If you copy the file to another folder, both copies remain; if you move it, only the destination copy remains. That distinction explains why copy is safer before editing.
Traps that cost marks
- Deleting a desktop shortcut and thinking the original file is gone.
- Ignoring hidden extensions, so report.docx.exe looks like a document.
- Confusing absolute and relative paths when the current folder changes.
- Emptying the Recycle Bin and then expecting ordinary undo to restore the file.