For CompTIA A+ Core 2 (220-1202), Domain 1, Objective 1.8, you need to recognize key macOS system folders and explain what they're for. A system folder is a well-known directory that macOS uses to store apps, user data, settings, and core operating system files. When you know these locations, troubleshooting gets faster because you stop guessing where things "might" be. You also reduce risk because you're less likely to delete something important or place sensitive files in the wrong spot.
By the end of this article, you'll be able to identify the five folders from the objective, describe what belongs in each one, and avoid common mistakes that cause slow performance, login confusion, and broken apps. You'll also build safer habits that match how macOS protects system files in newer releases.
The five macOS folders you must recognize for Core 2
Objective 1.8 names five folders you should treat as landmarks: /Applications, /Users, /Library, /System, and /Users/Library. Think of them like rooms in a building. Each room has a purpose, and mixing items between rooms creates clutter and security issues.
/Applications stores most installed apps that all users can run. Many macOS apps are "app bundles" that you can drag into this folder.
/Users contains home folders for each local user. This is where personal files live, along with user-level settings and caches.
/Library holds system-wide support files and settings that apply to the whole Mac. If something in this folder changes, multiple users may feel it.
/System contains core macOS components. On modern macOS, you typically read from this location, not write to it.
/Users/Library (also shown as ~/Library inside a user account) stores per-user support files, preferences, and caches. It matters because two users on the same Mac can run the same app with different settings.
macOS separates system files from user files for stability and safety. If everyday work lived next to core OS components, a single mistake could harm the whole machine. This split also supports least privilege, because standard users shouldn't need to touch the operating system to do normal work.
A quick path guide, absolute paths vs what you see in Finder
Finder shows a friendly view of storage, but the exam expects you to recognize UNIX-style absolute paths that start with /. In other words, /Applications is a real folder at the top level of the startup disk, even if Finder labels the disk with a name like "Macintosh HD".
Also, Finder hides some locations by default. The user Library folder is the classic example. You might not see /Users/username/Library unless you use Finder's Go menu or change view settings.
A helpful rule: if the path starts with
/System, treat it as "look, don't touch" during routine support.
This difference between what Finder shows and what the file system contains can explain why a user says, "The folder isn't there," while it exists in the correct path.
What changes on Apple silicon and newer macOS versions
Newer macOS versions, including those common on Apple silicon Macs, place stronger limits on modifying system files. A major change is the read-only system volume design, which makes many core OS items harder to alter, even for admin accounts.
From an exam perspective, this protection changes your mindset more than the folder names. You can still identify /System and describe its purpose, but you should assume you won't "fix" most issues by moving system files around. Instead, you verify settings, check storage, confirm permissions, and use approved tools or updates.
This matters during troubleshooting because some older habits are now unsafe or ineffective. For example, copying files into /System to "replace" something is not a normal fix on modern macOS. When the OS protects itself, your first steps should focus on user space and supported repair actions.
What belongs in each folder, and what can go wrong
Knowing the folder names is only step one. The real skill is matching a symptom to the right location, then making a safe first check. In support work, the safest checks are usually observation steps: confirm where something is stored, verify free space, and review security prompts. After that, you can choose a targeted change.
/Applications, where apps live and why drag-and-drop installs work
Most Mac apps live in /Applications as .app bundles. That design is why drag-and-drop installs work so often: the app's internal files stay packaged together. As a result, placing the app in /Applications makes it available to all users, and it keeps the system organized.
A common problem is duplicate apps. Users download an app, run it from Downloads, then later install a second copy into /Applications.