Operating Systems and File Management
What the domain covers
Operating Systems and File Management tests the OS as a resource manager, the difference between GUI and CLI, and safe file/folder operations. Expect questions on paths, extensions, copy versus move, Recycle Bin behaviour and backups.
Core rules
- OS functions: process management, memory management, file management, device management, security and user interface.
- GUI uses windows, icons and menus; CLI accepts typed commands and is powerful but unforgiving.
- A file name has a base name and an extension that tells the OS which program opens it. A path can be absolute (from the drive root, e.g.
D:\School\IT\notes.txt) or relative (from the current folder). - Copy leaves the original and creates a duplicate; move removes the original from its old location. Deleting to the Recycle Bin is reversible; deleting from a pen drive or using Shift+Delete is usually not.
- Use meaningful folder names, keep backups on a separate device/cloud, and set read/write permissions deliberately.
Worked example
In D:\School\IT\notes.txt, D: is the drive, School and IT are folders, notes is the file name and .txt is the extension. If this file is moved to D:\School\notes.txt, it is no longer inside the IT folder; the file itself is unchanged, only its location is.
Traps
- Saying “copy” when the original disappears - that is a move.
- Assuming every deleted file goes to the Recycle Bin; network and removable drives may bypass it.
- Ignoring hidden extensions:
invoice.pdf.exeis an executable, not a PDF. - Confusing a folder with a drive.