StudyToCert

All certifications / A+ Core 2 / Lessons

CompTIA A+ Core 2 220-1202 · Domain 1: Operating systems

OS types and purposes: Windows, macOS, Linux, ChromeOS, iOS/iPadOS, Android; vendor life cycles and end-of-life

▶ Watch the overview video

Last reviewed September 30, 2026 · Leer en español

An operating system (OS) is the software layer that sits between the hardware and the programs you run. It manages memory, schedules work on the CPU, talks to devices through drivers, stores files and enforces who is allowed to do what. Applications never talk to the hardware directly; they ask the OS. As a support technician you will meet several operating systems every week, and the A+ exam expects you to know what each one is for, who makes it, what hardware it runs on and how it is kept up to date and supported.

Desktop and laptop operating systems come first. Microsoft Windows dominates business desktops because of its huge software catalog and its tight integration with Active Directory domains and Group Policy. Apple macOS runs only on Apple Mac hardware and is popular with creative and development teams; because Apple controls both the hardware and the software, drivers are rarely a problem. Linux is a family of open-source distributions (Ubuntu, Fedora, Debian, Red Hat Enterprise Linux and many more) built on the Linux kernel; it runs most web servers, many network appliances and plenty of developer workstations, and is usually free to use. ChromeOS, from Google, is a lightweight, browser-centred OS on Chromebooks; it is cheap to manage, keeps most data in the cloud, updates itself and is very common in schools.

Mobile operating systems are the second group. Apple iOS runs on iPhone and iPadOS on iPad; both are closed ecosystems, and apps normally come only from the App Store after Apple reviews them. Google Android is based on the Linux kernel and is licensed to many phone makers (Samsung, Google Pixel, Motorola and others), who each add their own customizations and choose how long to support each model. That diversity is why Android update timing varies by manufacturer and sometimes by carrier, while Apple ships each update to all supported devices on the same day. Android also allows apps from sources other than the Google Play Store, which adds flexibility and risk.

Every vendor publishes a life cycle for its products. During mainstream support the product receives new features, bug fixes and security patches. Some vendors then offer an extended period with security fixes only, sometimes as a paid program. At end-of-life (EOL), often called end of support, the vendor stops issuing patches entirely. The software keeps working, but every newly discovered vulnerability stays open forever, vendors stop helping with problems, and new applications and drivers gradually stop supporting it. Compliance frameworks usually forbid running EOL software on systems that handle sensitive data. Mobile devices reach EOL when the vendor stops shipping OS updates to that model, which often happens while the hardware still works fine.

The distinctions the exam tests are mostly about fit and compatibility. Software is written for a particular OS, so a Windows application will not run natively on macOS, and an Android APK (Android package) will not install on an iPhone; the right OS depends on the software the user needs. Choose Windows when the user needs line-of-business Windows applications or domain management, macOS for Apple-centred creative workflows, Linux for servers and appliances, ChromeOS for low-cost, web-based fleets such as classrooms, and iOS or Android for phones and tablets. Know the update channels too: Windows uses Windows Update, macOS uses Software Update in System Settings, Linux distributions use their package managers, ChromeOS updates automatically in the background, and phones receive over-the-air (OTA) updates.

Consider a worked example. A clinic runs a reception PC on an OS version that has just reached end of support, and it hosts an old scheduling program that the vendor never updated. You cannot simply leave it, because new vulnerabilities will never be patched. First you check whether the scheduling vendor offers a supported version on a current OS; if so, you budget, test and schedule the migration. If the program truly cannot move, you isolate the PC on its own network segment, block internet access, restrict who can sign in, document the accepted risk and set a date to replace it.

Common mistakes: believing EOL means the OS stops booting (it keeps working, it just stops being patched); assuming every Android phone gets updates at the same time as Google's own devices; thinking ChromeOS runs traditional Windows desktop software natively; and forgetting that a phone model can reach EOL while it still looks new. Another trap is treating Linux as a single product. It is a kernel shared by many distributions, each with its own support schedule and package manager.

Exam questions usually describe a need and ask which OS or action fits. 'Inexpensive devices for students that mostly use web apps' points to ChromeOS. 'Runs only on Apple hardware' is macOS. 'Open source, runs most web servers' is Linux. 'Updates depend on the manufacturer and carrier' is Android. 'The vendor no longer releases security patches' means end-of-life, and the answer is to upgrade, replace or, if neither is possible, isolate the system and document the risk.

Key terms

Operating system (OS)
The software that manages hardware resources and provides services to applications and users.
Distribution (distro)
A packaged version of Linux that combines the Linux kernel with tools, a package manager and default software.
ChromeOS
Google's lightweight, browser-centred operating system for Chromebooks that updates itself automatically.
Over-the-air (OTA) update
An operating system update delivered wirelessly to a mobile device.
Life cycle
The vendor's published timeline of support phases for a product, from release to retirement.
End-of-life (EOL)
The point after which a vendor stops providing patches and support for a product.
Extended support
A later support phase, sometimes paid, in which only security fixes are provided.
Real-world example

A school district replaces aging Windows laptops in its classrooms with Chromebooks. Students work almost entirely in web-based office apps, the devices update themselves overnight, and teachers can wipe and reassign a lost device through the management console. The district keeps a small lab of Windows PCs for one design program that has no web version.

Exam tip: End-of-life does not mean the OS stops working; it means no more security patches. Answers about EOL systems point to upgrading or replacing them, or isolating them if they cannot be replaced.

Check yourself

A user needs to run a Windows-only accounting program. Can you give them an iPad instead of a laptop?

Not for native use, because applications are written for a specific OS and a Windows desktop program will not install on iPadOS.

Why do different Android phones receive the same Android update at different times?

Android is licensed to many manufacturers who customize it and decide when, or whether, to ship updates to each model, sometimes with carrier involvement.

What changes when an OS reaches end-of-life?

The vendor stops releasing patches and support, so new vulnerabilities remain unfixed even though the system still runs.

A legacy EOL system cannot be upgraded. What is the best mitigation?

Isolate it on a restricted network segment, limit who can reach it, document the accepted risk and plan its replacement.

Study A+ Core 2 for free
A week-by-week plan with every lesson, quizzes, checkpoint tests, a practice exam and hands-on labs.
Open the A+ Core 2 study plan