Operating Systems is 28% of A+ Core 2. Many questions are really tool-selection questions: what do you need to learn about the system, and which utility gives you that evidence with the least unrelated change?
Fast rule: Match the tool to the kind of evidence you need: current state, history, configuration, connectivity, or repair. Task Manager shows what is happening now; Event Viewer shows what happened before; management tools change configuration; network commands test connectivity; repair commands fix a specific layer.
1. Tool-selection decision map
| Need | Useful tool | Why |
|---|---|---|
| See running processes and resource use | Task Manager | Processes, performance, startup, services, users |
| Find logged errors | Event Viewer | System, application, and other Windows event logs |
| Inspect hardware/driver state | Device Manager | Devices, drivers, disabled hardware, errors |
| Manage partitions and volumes | Disk Management / diskpart | Disk, partition, and volume configuration |
| Check IP settings | ipconfig | Address, gateway, DNS, DHCP-related information |
| Ask DNS directly | nslookup | Name-resolution evidence |
| Check Windows protected files | sfc | System-file integrity and repair |
2. Match Windows GUI tools to the support task
| Tool | Best use | Scenario clue |
|---|---|---|
| Task Manager | Processes, performance, startup items, services, users | One process is consuming CPU/RAM or starting automatically |
| Event Viewer | Review logged system/application events | Need error history around a crash, service failure, or login issue |
| Device Manager | Hardware and driver state | Unknown device, driver problem, disabled adapter |
| Disk Management | Partitions, volumes, drive letters, formatting | New disk needs a volume or drive letter |
| Performance Monitor | Collect performance counters over time | Intermittent resource problem needs a trend |
| Resource Monitor | Detailed CPU, memory, disk, and network activity | Need more detail than a quick Task Manager view |
| System Information | Hardware, components, and OS details | Need a broad system inventory |
| Task Scheduler | Run tasks at triggers/times | Automate a recurring local action |
| Services | Inspect/start/stop Windows services | A required service is stopped or misconfigured |
| Registry Editor | Direct registry editing | Only when the required supported change is specifically in the registry |
Registry editing is powerful and risky. If a safer supported management surface solves the same problem, prefer it.
3. Use Windows network commands by question
| Command | Question it answers |
|---|---|
ipconfig | What IP configuration does this Windows client have? |
ping | Can I get an ICMP response from this destination when ICMP is allowed? |
nslookup | What does DNS return for this name or address? |
tracert | Which routed hops appear on the path? |
pathping | What path and packet-loss evidence can be gathered across hops? |
netstat | Which connections and listening ports exist? |
hostname | What is this computer's host name? |
If IP connectivity works but a name fails, nslookup is more targeted than repeatedly running ping. If the question is about a listening process or connection, netstat is more useful than ipconfig.
4. Use system and file commands for the right layer
Useful Core 2 commands include:
whoamifor the current security identitysfc /scannowfor protected Windows system fileschkdskfor filesystem/disk-related checksdiskpartfor command-line disk/partition workformatto create a filesystem on a volumerobocopyfor robust file/directory copyingnet usefor network-share connectionsnet userfor local user-account tasksgpupdateto refresh Group Policygpresultto report applied Group Policywinverto display Windows version/build informationmdto create a directoryrmdirto remove a directory
Do not confuse a filesystem check with a protected-system-file check. chkdsk and sfc answer different questions.
5. Separate installation and recovery choices
| Choice | Best clue |
|---|---|
| Clean install | Fresh OS deployment with applications/settings rebuilt |
| Upgrade | Move to newer OS while preserving supported user/application state |
| Image deployment | Apply a prepared standard system image |
| Remote/network install | Deliver installation across the network |
| Zero-touch deployment | Minimize manual technician steps |
| Repair install/recovery | Restore OS function without immediately treating the machine as a new build |
| Multiboot | Keep more than one bootable OS |
Modern Unified Extensible Firmware Interface (UEFI) Windows installations commonly pair with GUID Partition Table (GPT). Master Boot Record (MBR) is the older partitioning scheme.
Before installation or upgrade, think about data backup, hardware compatibility, required applications, drivers, licensing, lifecycle support, and rollback.
6. Know macOS support tools by purpose
At A+ depth, recognize common macOS tools and features:
- Finder: files, folders, mounted locations, applications
- Spotlight: search
- Keychain: stored credentials and certificates
- Time Machine: backup and restore
- Disk Utility: storage/volume tasks
- FileVault: full-disk encryption
- Force Quit: terminate an unresponsive application
- Terminal: command-line access
- Mission Control: window/workspace management
- iCloud/Continuity: synchronization and cross-device features
Common application/distribution items include .dmg, .pkg, and .app.
Choose the tool that matches the support task. FileVault is an encryption control; it is not the tool for repairing a disk volume.
7. Use Linux commands by function
| Need | Common command |
|---|---|
| List/navigate files | ls, cd, pwd |
| Copy/move/remove | cp, mv, rm |
| Search text | grep |
| Change permissions/ownership | chmod, chown |
| Run with elevated privilege | sudo |
| Process information | ps, top, kill |
| Disk/filesystem space | df, du |
Package-management and network commands vary by distribution and current toolset, so learn the purpose of the command families in the objectives rather than assuming one distribution is universal.
8. Keep Windows settings tied to user impact
Core 2 also expects support decisions involving:
- User accounts and permissions
- Windows Update
- Firewall and network profiles
- Wired, wireless, cellular, and VPN connections
- Static vs dynamic addressing
- File and printer sharing
- Proxy settings
- Power settings
- Applications and default apps
- Privacy and device settings
- Accessibility
- Cloud productivity and synchronization
If a laptop loses one USB device after sleep, power management can be more relevant than DNS. If only corporate resources fail for a remote user, verify the VPN before rebuilding Windows.
9. Scenario comparisons
Need to find why a service failed at 2:15 a.m.
Use Event Viewer for historical event evidence. Task Manager shows current state, not the same history.
One process is consuming nearly all CPU right now
Task Manager is the fastest first look.
User has an IP address but a hostname will not resolve
Use nslookup to question DNS directly. ipconfig can confirm configured DNS servers, but it does not replace the lookup test.
New drive is visible to Windows but has no usable volume
Disk Management is appropriate for partition/volume work.
Windows system files may be corrupted
Use sfc rather than chkdsk when the specific question is protected system-file integrity.
Linux command must run with administrative privilege
sudo is the relevant privilege-elevation clue.
10. Common exam traps
- Choosing a familiar command that answers a different question.
- Using
chkdskwhen the scenario asks about protected Windows system files. - Using
sfcfor a DNS problem. - Picking Registry Editor before a safer supported management tool.
- Treating Task Manager as historical logging.
- Treating Event Viewer as a live process manager.
- Confusing Disk Management with Device Manager.
- Assuming every Windows network failure requires reinstalling the adapter.
- Mixing operating systems and filesystems as if they were the same thing.
- Choosing an upgrade when the requirement calls for a clean standardized deployment.
11. Rapid review grid
| Clue | Tool |
|---|---|
| Current process/resource use | Task Manager |
| Logged system/application error | Event Viewer |
| Driver/device state | Device Manager |
| Partition/volume work | Disk Management / diskpart |
| IP configuration | ipconfig |
| DNS query | nslookup |
| Connections/listening ports | netstat |
| Protected Windows files | sfc |
| Linux elevated command | sudo |