Operating Systems and File Management
Operating Systems and File Management tests what an OS does, how files and folders are organised, and how to perform safe file operations. Questions often ask you to read a file path, choose an extension, or explain GUI vs CLI.
Core rules
- An OS manages hardware, provides a user interface, runs applications, manages memory and storage, and enforces permissions. Examples: Windows, Linux, Android.
- A GUI uses windows, icons, menus and a pointer; a CLI accepts typed commands. A file is a named collection of data; a folder/directory groups files.
- The extension suggests the file type: .txt text, .docx Word, .xlsx spreadsheet, .pptx presentation, .jpg image, .mp3 audio, .mp4 video, .exe program, .html web page.
- A path locates a file. In Windows, backslash separates folders; in Linux and URLs, forward slash is used. The root is the top-level directory.
- Copy duplicates; move relocates; rename changes the name but not the content; delete sends to Recycle Bin (or Trash) until emptied. A shortcut is a link, not the file itself.
Worked example
For the path C:\Users\Student\notes.txt, identify the file name, extension and parent folder. Reasoning: the last component after the final backslash is notes.txt, so the file name is notes and the extension is .txt. The component immediately before it is Student, so the parent folder is Student. C:\ is the drive/root area; Users and Student are folders along the path.
Traps
- Saying a .txt file cannot contain numbers; extensions describe format, not content.
- Thinking deleting a folder keeps its files; deleting a folder removes its contents too.
- Confusing a shortcut with the original file.
- Using the wrong slash in Windows paths or URLs.
- Assuming emptying the Recycle Bin can always be undone; it usually cannot.