CompTIA A+ Core 2: Windows vs macOS vs Linux on the same desk

Where does each OS show up on Core 2

Most of the operating-systems objectives on Core 2 are Windows-specific, which tracks with how many corporate fleets still run Windows. macOS and Linux share the rest. The blueprint expects you to install, configure, and troubleshoot all three, not just identify them.

• Windows. Installation methods, editions, system tools (Task Manager, Event Viewer, services.msc), command line (cmd and PowerShell), the registry, networking config, and the GUI tools (Settings, Control Panel) that touch most help-desk tickets.
• macOS. System Preferences (System Settings on newer releases), Time Machine, Disk Utility, Activity Monitor, common keyboard shortcuts, and Terminal commands. The objectives treat macOS as a peer OS, not an afterthought.
• Linux. Common distributions, the shell, file permissions, package management at a conceptual level, and the commands that overlap with Windows and macOS troubleshooting tasks.

The exam often phrases a scenario as "a user on macOS reports X, which utility do you open." Or "an admin on a Linux server wants to view the network configuration, which command do they run." Pattern questions, not deep-dive questions.

What are the command equivalents across the three OSes

The fastest study win on Core 2 is a side-by-side table of common tasks and the command on each OS. Learn the table and most "which command does X" questions turn into a lookup instead of a guess.

• View network config. Windows: ipconfig. macOS: ifconfig (still works) or ifconfig -a. Linux: ip a on modern distros, ifconfig on older.
• List files in a directory. Windows: dir. macOS: ls. Linux: ls.
• View running processes. Windows: Task Manager or tasklist. macOS: Activity Monitor or top. Linux: top or htop or ps aux.
• Check the file system. Windows: chkdsk. macOS: Disk Utility First Aid. Linux: fsck on an unmounted volume. These look at the on-disk structure: the directory entries, the allocation tables, bad sectors.
• Check the operating system's own files. Windows: sfc /scannow, which scans and repairs protected Windows system files. It does not check the file system, and those two jobs get mixed up constantly. macOS: Disk Utility First Aid, with a reinstall over the top when system files are damaged. Linux: package verification, for example rpm -V or debsums.
• Test connectivity. All three: ping and traceroute (Windows uses tracert).
• Resolve a hostname. All three: nslookup works everywhere. dig works on macOS and Linux.

A sample of what ip a looks like on a typical Linux box, which is the format the exam may show in an exhibit:

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue
    inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq
    link/ether 00:1a:2b:3c:4d:5e brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.42/24 brd 192.168.1.255 scope global eth0

That output gives you interface names, MAC addresses, IPv4 with CIDR, and broadcast addresses. If you can read it, you can answer "what is the IP of eth0" or "what is the subnet of this host" in one glance.

How do the file systems differ

Each OS has a default file system that the exam expects you to recognize. The differences matter when you mount external drives, plan backups, or troubleshoot disk errors.

• NTFS. Windows default. Journaled. Supports large files and volumes, file-level permissions, encryption (EFS), compression. macOS reads NTFS by default but cannot write without a third-party driver.
• APFS. macOS default since 2017. Designed for SSDs. Supports snapshots, fast cloning, native encryption. Not readable by Windows or Linux without extra tooling.
• ext4. Linux default on most distributions. Journaled, large file support, mature and stable. Windows does not read ext4 natively.
• exFAT. Cross-platform interchange. Readable and writable by Windows, macOS, and most Linux distros. Use for external USB drives that travel between machines.
• FAT32. Legacy. 4 GB per-file limit, 32 GB partition limit on Windows. Still common on USB sticks shipped from the factory.

Work a scenario through that list and it collapses fast. Say a user needs to move a 10 GB file between a Windows laptop and a macOS laptop on a USB drive. FAT32 stops at 4 GB per file. NTFS reads on macOS but will not write without a third-party driver. APFS is not readable on Windows without extra tooling. That leaves exFAT. The reasoning is the part worth keeping, because the same four constraints answer a lot of drive-format questions.

Where does each OS actually live on a desk

The real-world use cases are not exam content directly, but they make the objectives stick. Windows lives on the corporate office desk, the accounting workstation, the law office, the school front office, anywhere the user community needs the Microsoft stack (Office, Outlook, Active Directory, SharePoint). It also lives on the gaming PC at home.

macOS lives in creative shops, video production, marketing teams, executives who like the hardware, and a lot of startups. It is Unix-flavored, which is why so many shell commands carry over from Linux, but it runs Apple's own Darwin kernel and its own user-space layer. macOS users open Terminal far more often than Windows users open cmd.

Linux lives on servers, on the back-office boxes nobody sees, on the developer workstations, on the network appliances, and inside almost every cloud platform. The dental office probably runs a Linux NAS for backups without knowing it. The IT shop's monitoring server is Linux. The exam tests you on it because the real job will put you in front of a Linux shell within the first six months.

What this looks like in our platform

The Study Mode deck for Core 2 OS objectives walks through the command tables, the file-system differences, and the GUI utilities side by side. The Help Desk Simulator includes tickets across all three OS families. You might fix a stuck Print Spooler on Windows, reset a Wi-Fi profile on macOS, and tail a log on Linux all in one session. The grading checks whether you used the correct command for the platform.

If you are tracking toward the A+, the A+ track page has the full Core 2 objective map. Operating systems is domain 1. If you want to know how the four Core 2 domains are weighted, CompTIA publishes the percentages in the exam objectives PDF, and that is the number to trust rather than one quoted in a study post, including this one.

Where to go next

Once the command table is automatic, the next step is the security domain on Core 2. Windows security (UAC, Defender, BitLocker), macOS security (Gatekeeper, FileVault), and Linux permissions (rwx, chmod, sudo) all build on the OS knowledge you just locked in. Same pattern. Three families, one task, three commands. The exam rewards the match. So does the next ticket on the queue.

About the authors

Nick Miller

Founder and Lead Author

IT Service Center Manager and former CTE / IT teacher. Owner of Revtek IT Solutions. Writes everything that ships under his name and reviews every line of Revy-assisted drafting before publish.

LinkedIn ↗

R

Revy

Study buddy · AI co-author

Revy helps draft and structure these posts. Every piece is reviewed, edited, and fact-checked by Nick before publish. We disclose this here because it is the right thing to do. See the AI Policy for the full stance.