1.0 Operating Systems

The operating system is the bridge between the user, applications, and the physical computer.

An operating system, or OS, is the core software layer that makes hardware usable. Without it, the CPU, memory, storage, keyboard, mouse, display, printer, network adapter, firmware, and connected peripherals are just individual parts waiting for organized instructions. The OS coordinates those parts so a user can sign in, launch apps, store data, change settings, connect devices, print, browse, communicate, and get work done.

Think of the OS as the traffic controller, translator, and workspace manager for the whole computer.

• Resource management: The OS schedules CPU time, allocates RAM, manages storage access, handles virtual memory, and prioritizes processes so programs can run without constantly fighting each other.
• Hardware communication: The OS uses built-in services, drivers, kernel components, and device management tools to communicate with keyboards, mice, printers, cameras, storage, USB devices, displays, network adapters, Bluetooth radios, and other hardware.
• Application platform: The OS gives applications common services such as windows, menus, file access, networking, printing, security prompts, update channels, and APIs instead of forcing every app to control hardware directly.
• User interface: The OS provides graphical desktops, touch interfaces, command-line shells, accessibility tools, search, notifications, settings apps, and account sign-in methods.
• Security boundary: The OS enforces user permissions, file permissions, authentication, encryption, firewall rules, malware protection, updates, audit logs, and separation between standard users and administrators.

The OS also handles the everyday work users expect but rarely think about. It organizes files and folders, launches and closes applications, tracks user profiles, mounts file systems, controls input and output, stores system settings, loads services at startup, manages power states, connects to wired and wireless networks, and provides troubleshooting and management tools.

For the A+ exam, do not treat an operating system as only "Windows versus macOS." Objective 1.1 is about understanding why different OS types exist and what each one is best suited to do. A technician must match the OS to the device, the user, the application requirements, the hardware, the file system, the security model, and the vendor lifecycle.

Common OS-selection clues:

• Device type: Desktop, laptop, tablet, smartphone, server, kiosk, thin client, embedded device, or cloud instance.
• User role: Home user, student, technician, developer, power user, frontline worker, administrator, or enterprise employee.
• Application need: Windows-only software, mobile apps, browser-based work, creative tools, server services, development tools, or line-of-business applications.
• Management need: Local settings only, mobile device management, Group Policy, domain join, directory integration, remote wipe, update control, or endpoint monitoring.
• Lifecycle risk: Supported systems receive updates and security patches; end-of-life systems become compatibility and security liabilities.

Technician mindset:

• If the user cannot launch an app, check whether the OS edition, version, architecture, update level, and application dependencies support it.
• If a device is not working, verify the OS can communicate with the hardware through the correct driver, firmware setting, service, or built-in support.
• If a file cannot be copied, opened, encrypted, shared, or secured correctly, consider the file system, permissions model, path length, ownership, and compatibility with the destination system.
• If a system feels slow, check OS-managed resources such as startup apps, background services, storage health, memory pressure, updates, and power settings.
• If the system is no longer receiving updates, treat it as a lifecycle and security risk, not just an old computer.

Windows is the most common desktop operating system platform in business, education, government, and home environments.

When an A+ question mentions a standard office workstation, domain-joined laptop, gaming PC, point-of-sale terminal, shared classroom computer, training lab PC, medical office system, dispatch computer, or managed business endpoint, Windows should be one of the first operating system types you consider. Its huge market presence means technicians see it often, vendors support it heavily, and many commercial software publishers design, test, and certify Windows versions of their tools.

Why Windows is everywhere:

• Strong industry backing: Microsoft, OEMs, peripheral vendors, software vendors, managed service providers, and enterprise IT teams all build around Windows support.
• Multiple editions: Windows 10, Windows 11, Windows Server, and edition families such as Home, Pro, Enterprise, Education, and Server editions fit different users and environments.
• Software compatibility: Windows has a huge ecosystem of productivity apps, line-of-business applications, games, drivers, utilities, security tools, remote support tools, and management agents.
• Hardware support: Windows commonly supports desktops, laptops, tablets, docking stations, printers, scanners, smart card readers, webcams, storage, and specialized business peripherals.
• Enterprise management: Windows works with centralized identity, policy, patching, encryption, remote access, endpoint protection, and monitoring platforms.

Edition selection matters. Windows Home may be appropriate for a basic personal system, but it usually lacks the business features expected in managed environments. Windows Pro is a common fit for small business and technician scenarios because it supports features such as domain join, BitLocker availability, Remote Desktop host capability, Hyper-V support on capable systems, and stronger management options. Enterprise and Education editions add larger-scale features for organizations. Windows Server is not a desktop replacement; it is designed for server roles such as directory services, file services, print services, DNS, DHCP, virtualization, application hosting, and centralized management.

That flexibility is the big advantage. A technician can support basic home systems, business desktops, enterprise laptops, specialized hardware, and server workloads using related Windows knowledge. Windows also integrates well with common business services such as Microsoft accounts, Active Directory, Microsoft Entra ID, Group Policy, BitLocker, Microsoft Defender, Remote Desktop, Windows Update, Windows Update for Business, PowerShell, Event Viewer, Device Manager, Services, Task Manager, and enterprise management platforms.

Popularity also creates risk. Because Windows is widely deployed, attackers spend a lot of time targeting Windows systems, Windows users, Windows applications, Windows credentials, and Windows management tools. A large Windows environment needs strong patching, endpoint protection, least privilege, backups, monitoring, secure remote access, application control, and careful configuration. The more hardware and software Windows supports, the more compatibility questions a technician must verify before installing, upgrading, or troubleshooting.

Common Windows scenario clues:

• A user needs a specific commercial desktop application, accounting package, CAD tool, or Windows-only line-of-business program.
• A business wants domain sign-in, centralized policies, BitLocker, managed updates, remote support, and standardized device configuration.
• A technician needs to check drivers, Device Manager, Event Viewer, Services, Task Manager, Windows Security, Windows Update, or PowerShell.
• An upgrade question mentions TPM, Secure Boot, CPU support, RAM, storage capacity, UEFI firmware, application testing, or driver compatibility.
• A security question mentions ransomware, phishing, local administrator rights, unpatched systems, endpoint protection, or a large attack surface.

Technician mindset:

• Choose the correct Windows edition for the job. Home, Pro, Enterprise, Education, and Server editions do not provide the same features.
• Check hardware requirements before upgrading, especially TPM, Secure Boot, CPU support, RAM, storage, graphics, and firmware mode.
• Verify application, driver, and peripheral compatibility before changing versions or replacing hardware.
• Document licensing, activation state, backup status, user data location, encryption recovery keys, and rollback options before major changes.
• Treat unsupported Windows versions as security risks because they may no longer receive updates.
• Expect Windows questions to include security, patching, licensing, domain management, remote access, file systems, and compatibility clues.

Linux is a powerful, open-source operating system family inspired by Unix principles, but Linux itself is not Unix.

Linux is built around the Linux kernel, which is the core software that helps the operating system communicate with hardware, schedule processes, manage memory, mount file systems, and enforce permissions. What most users call "Linux" is usually a full Linux distribution, or distro, that combines the kernel with system tools, package management, a shell, optional desktop environment, utilities, documentation, and support resources.

Open source is the big idea.

• Linux is free to use, modify, and share under open-source licensing.
• Developers, vendors, administrators, students, and hobbyists can inspect and improve the software.
• Communities and companies build distributions for different goals, from beginner-friendly desktops to hardened servers.

Linux is flexible because it comes in many distributions. Ubuntu is common on desktops, labs, training environments, and servers because it is approachable and well documented. Debian is known for stability and a strong package ecosystem. Red Hat Enterprise Linux and Fedora are common in enterprise and development environments. Other distributions may focus on security testing, lightweight hardware, cloud workloads, containers, firewalls, or embedded systems.

For Core 2, Linux matters because technicians may support mixed environments. You might see Linux on web servers, development workstations, network appliances, virtualization hosts, cybersecurity tools, cloud instances, older hardware, kiosks, IoT-style devices, and repair or recovery media. Even if the user's main computer is Windows, Linux may appear behind the scenes in infrastructure or troubleshooting tools.

Advantages that show up in scenarios:

• Cost: Many Linux distributions have no license fee, which can reduce deployment cost.
• Hardware versatility: Linux can run on powerful servers, desktops, single-board computers, and older systems that may not handle newer commercial OS requirements.
• Customization: Administrators can tune services, desktop environments, startup behavior, storage, security, and package selection.
• Community support: Documentation, forums, package maintainers, developers, and vendor communities often provide fast help and frequent updates.
• Command-line control: The shell is a major strength for automation, scripting, remote administration, and repeatable troubleshooting.

Linux also has tradeoffs. Some hardware, especially consumer laptops, specialty peripherals, fingerprint readers, graphics adapters, Wi-Fi chipsets, docking stations, and vendor-specific function keys, may have limited or uneven driver support. Commercial application support can also vary. A business may rely on software that only supports Windows or macOS, which can make Linux a poor desktop choice even when the OS itself is stable and secure.

Technician mindset:

• Ask which distribution and version is installed before assuming commands, package tools, services, or desktop settings are identical.
• Match the package manager to the distro, such as APT on Debian/Ubuntu families or DNF/YUM on Fedora and Red Hat families.
• Verify driver support before installing Linux on laptops, wireless adapters, graphics hardware, printers, docking stations, or specialty devices.
• Use Linux when a scenario values control, scripting, services, security tooling, server roles, or lightweight operation.
• Do not assume "free" means "no support plan." Businesses may still need vendor-backed Linux support, documentation, maintenance windows, and trained administrators.

macOS is Apple's desktop operating system, built specifically for genuine Apple computers.

macOS runs on Mac hardware such as MacBook Air, MacBook Pro, iMac, Mac mini, Mac Studio, and Mac Pro systems. Unlike Windows or many Linux distributions, macOS is not intended to be installed on any generic PC hardware. Apple controls the operating system, hardware design, firmware, drivers, update process, security features, and much of the user experience, which is why macOS often feels polished and consistent across supported devices.

What macOS is designed to do well:

• Provide a clean desktop experience: macOS emphasizes simple navigation, consistent menus, Spotlight search, Finder, Mission Control, Dock-based launching, and a visual interface that is approachable for many users.
• Integrate with Apple devices: Macs work tightly with iPhone, iPad, Apple Watch, AirPods, iCloud, Messages, FaceTime, AirDrop, Handoff, Continuity Camera, and Apple ID services.
• Support creative and productivity workflows: macOS is common in design, photography, video, audio, education, executive, development, and general productivity environments.
• Use Apple's hardware platform: macOS is tuned for Apple hardware, including Apple silicon systems, battery behavior, displays, trackpads, cameras, microphones, and built-in security components.
• Reduce configuration sprawl: Fewer supported hardware combinations can mean fewer driver surprises compared to broad PC ecosystems.

Security is a major macOS selling point, but the exam answer should still stay balanced. macOS includes built-in protections such as Gatekeeper, FileVault, System Integrity Protection, privacy permissions, signed software checks, sandboxing, notarization expectations, and regular security updates. Apple silicon Macs also include hardware-backed security features. These protections reduce risk, but they do not make a Mac immune to phishing, malicious profiles, unsafe browser extensions, credential theft, outdated software, or poor administrator practices.

The strongest macOS advantage is the controlled ecosystem. When the user's work already lives in Apple services or creative applications, macOS can be the smoothest fit. A Mac user may expect iCloud Drive, Keychain, Photos, Messages, FaceTime, AirDrop, seamless device handoff, excellent trackpad gestures, and reliable sleep/wake behavior. In those scenarios, macOS is not just an OS choice; it is part of the user's workflow.

macOS also has tradeoffs. The biggest limitation is hardware: macOS is for Apple computers only. Apple hardware typically costs more up front, has fewer low-cost configuration options, and may have limited repair or upgrade paths compared to many PCs. Some business applications, specialized peripherals, management agents, games, accounting tools, or line-of-business programs may be Windows-first or Windows-only. A smaller enterprise ecosystem can also mean fewer technicians, fewer certified support options, and more planning when Macs must integrate into a Windows-heavy organization.

Common macOS scenario clues:

• The user needs tight integration with iPhone, iPad, iCloud, AirDrop, Messages, FaceTime, or Apple ID services.
• The user works in a creative role that relies on Mac-supported audio, video, design, photography, or publishing tools.
• The organization wants a polished desktop experience with a controlled hardware and software ecosystem.
• The scenario mentions Apple-only hardware, Apple silicon, FileVault, Gatekeeper, System Settings, Finder, Keychain, or Time Machine.
• The downside clue mentions higher upfront cost, limited upgradeability, Apple hardware only, or fewer enterprise-focused options than Windows.

Technician mindset:

• Verify the exact Mac model, macOS version, processor family, storage capacity, warranty status, and update compatibility before making changes.
• Check whether the required application supports macOS and whether it supports Intel Macs, Apple silicon Macs, or both.
• Use Apple-focused tools and concepts such as Finder, System Settings, Disk Utility, Time Machine, FileVault, Keychain Access, Activity Monitor, Terminal, and recoveryOS when troubleshooting.
• Plan for account and data services: Apple ID, iCloud, local user accounts, mobile device management enrollment, activation lock, and backup status can all affect service work.
• Do not assume macOS is malware-proof. Keep updates current, avoid unnecessary admin rights, validate software sources, and protect credentials.
• When a business is mostly Windows-based, confirm file sharing, printing, authentication, remote access, management, and application compatibility before recommending macOS.

Chrome OS is Google's fast, simple, and secure operating system built around the Chrome browser, web apps, cloud services, and Chromebook hardware.

Chrome OS, also called ChromeOS in current Google branding, is designed for users whose work happens mostly online. Instead of making the local computer the center of everything, Chrome OS puts the browser, Google account, web applications, cloud storage, and automatic updates at the center of the experience. This makes it a strong fit for schools, lightweight business use, shared devices, kiosks, frontline workers, and users who mostly need email, documents, video meetings, learning platforms, browser-based tools, and cloud files.

Built on Linux, but not used like a traditional Linux desktop.

• Chrome OS uses the Linux kernel, which helps provide stability, hardware control, process management, and security foundations.
• Most users do not manage Chrome OS like Ubuntu, Fedora, Debian, or Red Hat; the normal experience is browser-first and heavily managed by Google services.
• Some Chrome OS devices support Linux development environments or Android apps, but those are additions, not the core user model.
• The OS is designed to update automatically and reduce the amount of manual maintenance expected from the user.

The biggest advantage is simplicity. A Chromebook can be quick to deploy, quick to reset, and easy for a nontechnical user to operate. User data is often tied to the Google account and cloud services, so replacing a failed device can be much less painful than rebuilding a traditional desktop. Sign in, sync settings, reconnect to cloud files, and the user may be productive again quickly.

Where Chrome OS fits well:

• Education: Students can use managed Chromebooks for assignments, research, testing platforms, video calls, and classroom web apps.
• Shared workstations: Guest mode, account-based sign-in, easy resets, and web-focused workflows fit libraries, labs, front desks, and shared carts.
• Budget deployments: Many Chromebooks are affordable compared with traditional laptops, especially when the workflow does not require heavy local software.
• Cloud-first businesses: Organizations using Google Workspace, browser-based tools, SaaS apps, and cloud storage can standardize around Chrome OS.
• Kiosk and frontline use: Managed Chrome OS devices can serve as check-in stations, signage, inventory terminals, or simple task-based endpoints.

Chrome OS also has limitations. It is cloud-friendly and often cloud-dependent. Many tasks work best with reliable internet access, cloud authentication, and web services. Offline modes exist for some apps, but Chrome OS is not the best fit when the user needs heavy local applications, advanced gaming, specialized Windows or macOS software, full desktop virtualization, complex local file workflows, or hardware that requires traditional desktop drivers.

Hardware choices are another exam clue. Chrome OS usually appears on Chromebooks, Chromeboxes, and similar Chrome devices from multiple hardware partners. That gives buyers choice and affordability, but the device must still match the user. Low-end Chromebooks may be fine for web browsing and schoolwork, but they may struggle with large video calls, many browser tabs, Android apps, Linux containers, or long support expectations. Always check memory, storage, screen size, keyboard quality, Wi-Fi support, ports, touchscreen needs, and update lifecycle.

Management is a major strength in organizations. Admins can use Google Admin console and Chrome Enterprise tools to enforce policies, manage extensions, configure networks, control sign-in, wipe devices, set kiosk mode, push bookmarks, restrict apps, and manage updates. For a technician, that means a Chrome OS issue may not be a broken device; it may be a policy, account, enrollment, extension, or network configuration problem.

Technician mindset:

• Confirm whether the user's apps are browser-based, Android-based, Linux-based, or require a traditional Windows or macOS desktop.
• Check internet access, Google account status, device enrollment, sync state, policy restrictions, and extension behavior before replacing hardware.
• Verify the device's automatic update expiration or support lifecycle before buying, deploying, or recommending a Chromebook.
• For performance issues, check browser tabs, extensions, storage space, available RAM, updates, and whether the hardware is too low-end for the workload.
• For managed devices, remember that settings may be controlled by the organization, not the local user.
• Use Chrome OS when the workflow is web-first; avoid it when the scenario needs heavy local software, specialized drivers, advanced gaming, or Windows-only applications.

iPadOS is Apple's tablet operating system designed specifically for iPad hardware, combining the simplicity of iOS with productivity features built for a larger touch display.

iPadOS shares its roots with iOS, but it is not just "a big iPhone screen." Apple split iPadOS into its own platform so the iPad could support tablet-focused workflows: larger layouts, multitasking, Apple Pencil input, external keyboards, trackpads, file management, side-by-side apps, and display features that make more sense on an iPad than on a phone. For the A+ exam, iPadOS belongs in the mobile/tablet operating system category, not the traditional desktop operating system category.

What iPadOS is built for:

• Touch-first computing: Users interact through gestures, touch controls, on-screen keyboards, Apple Pencil, and optional keyboard or trackpad accessories.
• Tablet productivity: iPadOS supports Split View, Slide Over, Stage Manager on supported models, multitasking gestures, widgets, drag and drop, and app layouts optimized for the iPad display.
• Web and app access: Safari provides a desktop-class browsing experience, while the App Store supplies iPad-focused apps for school, business, creativity, communication, and field work.
• Apple ecosystem integration: iPadOS works with iCloud, AirDrop, Handoff, Continuity, Sidecar, Universal Control on supported setups, Messages, FaceTime, Photos, and Apple ID services.
• Mobility: iPads are light, battery-powered, easy to carry, and often available with Wi-Fi or cellular connectivity.

iPadOS is especially useful when the user needs a device that sits between a phone and a laptop. It can be easier to carry than a notebook, easier to draw on than a laptop, and better for reading, forms, signatures, point-of-sale, inventory, note taking, training, video calls, and field workflows than a small phone screen. Add a Magic Keyboard, Bluetooth keyboard, Apple Pencil, or external display support on compatible models, and the iPad can become a surprisingly capable productivity endpoint.

The image's "extend your view" clue points to Sidecar. With supported Macs and iPads, Sidecar can turn an iPad into a second display or drawing tablet for macOS. That matters in scenario questions because iPadOS can complement a Mac workflow instead of replacing it. A designer might use Apple Pencil on an iPad as a creative input device, while a traveling user might use the iPad as a lightweight second screen.

Security and management are also important. iPadOS uses Apple's controlled app distribution model, app sandboxing, device encryption, biometric unlock options, passcodes, Find My, activation lock, privacy permissions, rapid updates, and mobile device management support. In schools and businesses, iPads can be supervised, enrolled, remotely wiped, restricted, assigned apps, and configured through MDM. A technician should always consider whether a setting is local, Apple ID-related, or controlled by an organization.

iPadOS has limits. It does not run full desktop Windows applications, macOS applications, traditional desktop drivers, or every browser extension/workflow a laptop user may expect. File access is more app-centered than a full desktop OS, and external peripheral support depends on the model, port, adapter, app support, and iPadOS version. For some users, an iPad can replace a laptop; for others, it is best as a companion device.

Common iPadOS scenario clues:

• The user needs a tablet for mobility, forms, drawing, note taking, classroom use, signatures, video calls, or field service.
• The scenario mentions Apple Pencil, Magic Keyboard, Split View, Slide Over, Sidecar, Safari, App Store, iCloud, FaceTime, or AirDrop.
• A Mac user wants a second display or tablet input surface while traveling.
• An organization wants managed tablets for students, kiosks, sales floors, healthcare rounds, inspections, or frontline workflows.
• The downside clue mentions needing desktop apps, full driver support, complex local file workflows, or a traditional laptop replacement.

Technician mindset:

• Identify the exact iPad model, iPadOS version, storage capacity, Wi-Fi or cellular status, Apple ID state, warranty status, and MDM enrollment before troubleshooting.
• Check whether the user's required apps are available in the App Store and whether they support the needed accessories or workflow.
• For keyboard, Apple Pencil, display, or Sidecar issues, verify compatibility by model, accessory generation, Bluetooth status, USB-C or Lightning adapter, and software version.
• For business or school devices, confirm whether restrictions, supervised mode, app assignments, content filters, or remote management policies are controlling behavior.
• Do not recommend iPadOS when the user clearly needs full desktop software, Windows-only applications, traditional drivers, or heavy local multitasking.
• Back up through iCloud or a supported computer before resets, repairs, ownership changes, or major updates.

iOS is Apple's mobile operating system for iPhone, built for secure, touch-first communication, apps, camera use, location services, and everyday mobile productivity.

iOS powers the iPhone. It is designed for a smaller handheld screen, cellular mobility, battery efficiency, quick app launching, camera-heavy workflows, secure messaging, mobile payments, notifications, and constant network movement between Wi-Fi and cellular. Where macOS targets Apple desktops and laptops, and iPadOS targets tablets, iOS is focused on the smartphone experience.

About iOS:

• Made for iPhone: iOS is designed exclusively for Apple iPhones and cannot be installed on non-Apple phones or generic mobile hardware.
• Unix foundation: iOS has a Unix-based foundation that supports stability, permissions, process isolation, and security design.
• Proprietary software: iOS is closed-source, so Apple controls the platform, update process, default apps, security model, and user experience.
• Apple ecosystem only: iOS works tightly with Apple ID, iCloud, App Store, Messages, FaceTime, AirDrop, Find My, Apple Pay, Apple Watch, AirPods, and other Apple services.

The biggest strength of iOS is the controlled experience. Apple designs the hardware, operating system, app review process, update path, built-in security controls, and default user interface as one ecosystem. That creates a smooth experience for many users: consistent gestures, reliable app installation, easy updates, strong backup options, privacy prompts, and dependable integration with other Apple devices.

iOS apps are distributed differently than traditional desktop software. Most user apps come from the Apple App Store, where developers submit apps for review before release. Apps are built using Apple's development tools, such as the iOS SDK and Xcode, typically on a Mac. This review and distribution model helps reduce risk and improve consistency, but it also means users and organizations have less freedom than on an open desktop platform.

Security is central to iOS. Important concepts include passcodes, Face ID, Touch ID on supported older devices, device encryption, app sandboxing, privacy permissions, Find My, activation lock, rapid security updates, signed apps, secure boot processes, and Apple's app review model. These controls make iOS a strong choice for everyday mobile use, but technicians should still watch for phishing, malicious configuration profiles, unsafe links, credential theft, compromised Apple IDs, outdated devices, and risky user behavior.

iOS also has practical limitations. It does not run Windows desktop apps, macOS apps, traditional drivers, or full desktop management tools. File handling is app-centered, peripheral support depends on the iPhone model and adapter, and deep customization is more limited than Android or traditional desktop platforms. iOS is ideal when the user needs a trusted, mobile, Apple-integrated smartphone; it is not a replacement for every desktop, server, or specialized computing workflow.

Common iOS scenario clues:

• The scenario mentions iPhone, cellular data, SIM or eSIM, Apple ID, iCloud, Face ID, App Store, Messages, FaceTime, Find My, Apple Pay, or Apple Watch pairing.
• The user needs secure mobile communication, camera use, navigation, notifications, mobile apps, MFA prompts, or on-the-go access to cloud services.
• An organization needs managed phones through MDM, remote wipe, passcode policy, app deployment, Wi-Fi/VPN profiles, or supervised Apple devices.
• The problem involves app permissions, notification settings, storage space, iCloud backup, activation lock, update compatibility, or Apple account access.
• The downside clue mentions Apple-only hardware, limited customization, App Store restrictions, or the need for desktop-class applications.

Technician mindset:

• Identify the exact iPhone model, iOS version, storage capacity, battery health, carrier status, Apple ID state, iCloud backup status, and MDM enrollment before troubleshooting.
• Check app permissions for camera, microphone, location, contacts, photos, Bluetooth, local network, notifications, and background activity when app behavior seems broken.
• For connectivity issues, separate Wi-Fi, cellular data, carrier plan, VPN, Bluetooth, AirDrop, and profile restrictions instead of treating all network problems the same.
• For app problems, verify iOS compatibility, App Store availability, storage space, updates, Screen Time restrictions, and whether the app is managed by an organization.
• For lost, stolen, or replaced phones, check Find My, activation lock, iCloud backup, device passcode, MFA access, and organizational remote-wipe policies.
• Do not recommend iOS when the scenario requires non-Apple hardware, heavy customization, desktop-only applications, or traditional driver support.

Android is Google's mobile operating system platform, built on the Linux kernel and designed for choice across many phones, tablets, wearables, TVs, and other smart devices.

Android is the most widely used mobile operating system in the world because it is not limited to one hardware manufacturer. Samsung, Google, Motorola, OnePlus, Lenovo, and many other vendors can build Android-based devices at different sizes, prices, performance levels, and feature sets. That variety is Android's biggest strength: users and organizations can choose budget phones, rugged field devices, foldables, tablets, barcode scanners, point-of-sale devices, TVs, wearables, and premium smartphones while staying inside the Android ecosystem.

Built for choice. Built for everyone.

• Open ecosystem: Android is developed through the Open Handset Alliance and a broad industry ecosystem instead of being tied to one device maker.
• Open-source foundation: Android is based on the Android Open Source Project and uses the Linux kernel for core hardware, process, memory, and security functions.
• Many device types: Android can run on smartphones, tablets, TVs, wearables, vehicle systems, kiosks, enterprise handhelds, and specialty devices.
• Many price points: Android devices range from low-cost entry models to high-end flagship phones, which gives buyers more hardware and budget options.
• Manufacturer customization: Device makers can add custom launchers, settings, management tools, apps, hardware features, and update schedules.

Android apps are commonly installed through the Google Play Store, but Android is more flexible than iOS about app sources. Depending on device policy and user settings, apps may also come from other trusted stores, enterprise app catalogs, manufacturer stores, or carefully controlled sideloading. That flexibility helps developers, businesses, and specialized environments, but it also increases the need for security awareness. Installing apps from untrusted sources can introduce malware, privacy risk, data theft, or unstable behavior.

Android development is also flexible. Developers can build Android apps using Android SDK tools on Windows, macOS, or Linux. This cross-platform development model supports a large app ecosystem and makes Android attractive to businesses, independent developers, education programs, and hardware vendors. For technicians, the important idea is that Android has a huge app library, but app quality, update support, device compatibility, and permission behavior still need to be checked.

Security on Android depends on the OS version, patch level, device manufacturer, carrier involvement, app source, user behavior, and management policy. Modern Android includes app sandboxing, permissions, encryption, screen locks, biometrics, Google Play Protect, Find My Device, secure boot features, and work profiles on managed devices. However, because Android runs on many devices from many vendors, update timing and support lifecycle can vary widely. Two Android phones may both say "Android," but they may have very different patch levels, hardware capabilities, preinstalled apps, and enterprise support.

Common Android scenario clues:

• The scenario mentions Google Play, APK files, sideloading, Android SDK, Google account, Play Protect, Find My Device, work profile, or a non-Apple smartphone.
• The user needs more hardware choice, lower device cost, larger screen options, rugged devices, expandable storage on supported models, or specialized vendor hardware.
• An organization needs managed Android devices for field service, delivery, inventory, healthcare, point-of-sale, scanning, inspections, or frontline work.
• The problem involves app permissions, unknown sources, manufacturer update delays, carrier settings, Google account sync, storage, battery optimization, or mobile data.
• The risk clue mentions open app sources, inconsistent patching, malware from untrusted apps, device fragmentation, or unsupported older Android versions.

Technician mindset:

• Identify the exact device manufacturer, model, Android version, security patch level, carrier, storage capacity, Google account status, and management enrollment before troubleshooting.
• Check app permissions for camera, microphone, contacts, SMS, location, files, nearby devices, notifications, background activity, and battery optimization when an app behaves unexpectedly.
• Verify whether an app came from Google Play, a trusted enterprise catalog, a manufacturer store, or an unknown APK source before assuming it is safe.
• For update questions, check both Android version support and monthly security patch level because manufacturer and carrier update schedules can differ.
• For business devices, look for MDM, Android Enterprise, work profiles, kiosk mode, remote wipe, app allowlists, and policy restrictions.
• Do not treat all Android devices as identical. Hardware features, menus, update paths, preloaded software, and management options can vary by vendor and model.

A file system is the structure an operating system uses to organize, store, secure, find, and recover data on a storage device.

Before a drive, USB flash drive, memory card, or storage volume can reliably hold files, it must be prepared with a file system. Formatting creates the rules the operating system uses to track file names, folders, metadata, free space, permissions, allocation units, timestamps, and recovery information. Without a file system, the device may be physically present, but the OS does not have a usable map for placing and retrieving data.

File systems are not just storage labels. They affect compatibility, maximum file size, security, reliability, recovery options, and performance.

• FAT/FAT32: Older and widely recognized. FAT32 is useful for compatibility, but it has important limits, including a 4 GB maximum individual file size and limited modern security features.
• exFAT: Designed for flash drives and removable media. It works across Windows, macOS, and many Linux systems and allows files larger than 4 GB, making it a strong choice for cross-platform removable storage.
• NTFS: The standard modern Windows file system for internal drives. It supports permissions, quotas, compression, encryption, large files, journaling, and better recovery than FAT-based formats.
• ReFS: Resilient File System, a Windows-focused file system built for reliability, integrity checking, very large volumes, storage arrays, and server-style workloads.
• ext4: A common Linux file system known for performance, stability, journaling, and support for large volumes and files. It is widely used on Linux distributions and many Android-based systems.
• XFS: A high-performance Linux file system designed for large data sets, high throughput, low overhead, server storage, databases, and enterprise workloads.
• APFS: Apple File System, used across modern macOS, iOS, and iPadOS. It is optimized for SSDs and supports encryption, snapshots, clone files, space sharing, and strong data integrity.

Choosing the wrong file system can create real support problems. A USB drive formatted as FAT32 may be readable almost everywhere, but it cannot store a single 8 GB video file. An NTFS external drive may work perfectly on Windows but may be read-only or limited on some non-Windows systems without extra support. An APFS drive is excellent for modern Apple devices but is not a universal exchange format. Linux systems may use ext4 or XFS internally, but Windows users usually cannot read and write those formats without additional tools.

Common file-system scenario clues:

• Cross-platform removable drive: Think exFAT when the user needs Windows and macOS compatibility and files larger than 4 GB.
• Basic legacy compatibility: FAT32 may appear when small removable drives, firmware tools, or older devices need broad recognition.
• Windows internal drive: NTFS is the normal choice because permissions, encryption, compression, quotas, and recovery features matter.
• Large Windows server storage: ReFS may appear when the question emphasizes resiliency, integrity checking, storage spaces, large volumes, or server workloads.
• Linux internal drive: ext4 is a common default, while XFS is common when performance and very large data sets matter.
• Modern Apple storage: APFS is expected for current macOS, iOS, and iPadOS environments, especially SSD-based systems.

Technician mindset:

• Before formatting, confirm whether the user needs compatibility with Windows, macOS, Linux, mobile devices, cameras, game consoles, firmware tools, or embedded systems.
• Ask about maximum file size. FAT32 is a poor choice for large video files, disk images, backups, and modern media libraries because of the 4 GB single-file limit.
• Use NTFS when Windows security features such as permissions, encryption, compression, quotas, and recovery support are required.
• Use exFAT when removable storage must move large files between Windows and macOS with minimal friction.
• Use APFS for modern Apple storage unless the device needs to be shared directly with non-Apple systems.
• For Linux servers and workloads, understand whether ext4 stability or XFS scalability/performance better fits the scenario.
• Warn users that formatting erases or replaces the current file structure unless data is backed up first.

Every operating system is shaped by the vendor that builds, supports, updates, licenses, and restricts it.

Objective 1.1 is not only asking you to name operating systems. It is asking you to understand the limits that come with each platform. Windows, macOS, Linux distributions, Chrome OS, iPadOS, iOS, and Android all have different update models, hardware rules, application ecosystems, support timelines, security controls, and compatibility expectations. A good technician does not just ask, "Can this device run an OS?" The better question is, "Will this vendor support this OS, hardware, app, file, and workflow long enough for the user to rely on it?"

Vendor-specific limitations are the hidden rules behind OS choice.

• Hardware limits: macOS requires Apple computers, iOS requires iPhone hardware, iPadOS requires iPad hardware, and Android support can vary by manufacturer and model.
• Update limits: Vendors decide how updates are delivered, how long devices receive updates, and which older models are no longer eligible.
• Application limits: Some apps are Windows-only, macOS-only, mobile-only, browser-based, store-restricted, or dependent on a specific OS version.
• Management limits: Enterprise tools differ across Windows, Apple platforms, Chrome OS, Linux, and Android.
• Support limits: End-of-life products may lose patches, vendor support, app support, driver updates, and compliance approval.

Lifespan is one of the most important limits. Each vendor decides when an operating system, device, browser, app, or hardware platform reaches end of life. After that point, the product may stop receiving security patches, feature updates, firmware fixes, app compatibility updates, or official support. In a business environment, an end-of-life OS can create compliance problems, cyber insurance issues, audit findings, and unacceptable risk.

Updates also behave differently. Windows commonly notifies users and administrators through Windows Update, organizational update policies, and enterprise management platforms. iOS, iPadOS, and macOS notify users when updates are available and can also be controlled through Apple management tools. Android updates depend on Google, the device manufacturer, carrier involvement, and the specific model. Chrome OS is designed to update automatically in the background, but Chrome devices still have an automatic update expiration or support lifecycle that must be checked before deployment.

Compatibility is not the same as transferability. Some content is easy to move between operating systems. Photos, PDFs, text files, MP3 audio, MP4 video, and many cloud documents often transfer well. Applications are different. A Windows executable does not simply become a macOS app. An iOS App Store app does not automatically run on Android. A Linux package built for one distribution may not install cleanly on another. The file may move, but the program that opens, edits, secures, or manages that file may not exist on the destination platform.

Web-based applications help bridge the gap. If a workflow lives in a browser, the user may be able to move between Windows, macOS, Chrome OS, Linux, iPadOS, iOS, and Android more easily. But even web apps can depend on browser version, extensions, camera permissions, local storage, offline mode, identity provider settings, multifactor authentication, device compliance, or a vendor-supported browser list.

Where vendor limitations show up in real support:

• Drivers: A printer, scanner, docking station, graphics adapter, smart card reader, or specialty device may support one OS but not another.
• File systems: NTFS, APFS, ext4, exFAT, FAT32, and other formats affect read/write support, permissions, encryption, file size limits, and cross-platform use.
• Stores and app sources: Apple platforms rely heavily on App Store rules, Android allows more app-source flexibility, Windows has multiple app paths, and Chrome OS centers on web apps and managed extensions.
• Licensing: OS editions, activation, subscription services, app licenses, and enterprise agreements can limit what is legal or supported.
• Cloud accounts: Apple ID, Google account, Microsoft account, domain accounts, and MDM enrollment can control what the device can access or install.

Technician mindset:

• Check the vendor lifecycle before deployment. A cheap device is not a bargain if updates end too soon.
• Confirm exact OS version, edition, architecture, hardware model, and support status before installing software or recommending an upgrade.
• Separate data compatibility from application compatibility. A file may transfer even when the original app does not.
• Verify driver and peripheral support for printers, scanners, cameras, docks, biometrics, storage devices, and specialty business hardware.
• Watch for account and management restrictions such as MDM, activation lock, Google Admin policies, domain policy, or enterprise app controls.
• Document vendor limitations clearly so the user understands whether the problem is technical, licensing-based, lifecycle-based, or policy-based.

Objective 1.1 is about matching the operating system and file system to the device, user, workload, security need, compatibility requirement, and vendor lifecycle.

The exam will not always ask, "What is Windows?" or "What is Linux?" More often, it gives you a scenario and expects you to recognize which operating system type fits best. Read for clues: device type, user role, required applications, hardware support, file size, storage format, account ecosystem, management tools, update support, security expectations, and whether the platform is desktop, mobile, tablet, cloud-first, or server-oriented.

Know the purpose of each OS type:

• Windows: Best known for broad desktop hardware support, business software compatibility, domain integration, centralized management, Remote Desktop, BitLocker, and a large enterprise ecosystem.
• Linux: Strong for open-source flexibility, servers, scripting, development, security tools, older hardware, customization, and cost-sensitive deployments.
• macOS: Apple's desktop OS for Mac computers, valued for polished usability, creative workflows, Apple hardware integration, built-in security, and Apple ecosystem features.
• Chrome OS: Google's web-first OS for Chromebooks and Chrome devices, built around the browser, cloud services, automatic updates, affordability, and simple management.
• iPadOS: Apple's tablet OS for iPad, optimized for touch, Apple Pencil, keyboard accessories, multitasking, Sidecar, managed tablets, and portable productivity.
• iOS: Apple's mobile OS for iPhone, focused on secure communication, cellular mobility, App Store apps, camera workflows, Apple services, and managed phones.
• Android: Google's mobile OS platform with broad device choice, many manufacturers, Google Play, flexible app sources, and wide use across phones, tablets, TVs, wearables, and specialty devices.
• File systems: FAT32 is broadly recognized but limited to 4 GB individual files; exFAT is strong for cross-platform removable storage; NTFS is the normal Windows internal-drive format; ReFS targets resilient Windows server storage; ext4 and XFS are Linux-focused formats; APFS is Apple's modern file system for macOS, iOS, and iPadOS.

Scenario clues matter more than brand preference.

• If the scenario says domain join, Group Policy, Windows-only app, or broad PC hardware support, think Windows.
• If it says open source, server workload, shell scripting, package manager, or older hardware, think Linux.
• If it says Mac hardware, Apple creative workflow, FileVault, Gatekeeper, or Apple ecosystem integration, think macOS.
• If it says Chromebook, browser-based apps, Google Admin, automatic updates, or budget school devices, think Chrome OS.
• If it says iPad, Apple Pencil, Sidecar, Split View, or managed tablets, think iPadOS.
• If it says iPhone, Face ID, App Store, Apple Pay, cellular, or Find My, think iOS.
• If it says Google Play, APK, many device vendors, work profile, or sideloading, think Android.
• If it says 4 GB file limit, removable media, NTFS permissions, APFS snapshots, Linux ext4/XFS, ReFS resiliency, or cross-platform drive sharing, think file system selection.

Do not stop at the OS name. Verify the version, edition, architecture, hardware model, file system, file size limit, read/write support, account state, app requirements, driver support, update status, and vendor lifecycle. A technically possible installation can still be the wrong recommendation if the vendor no longer supports it, the required app does not run, the security policy cannot be enforced, or the device will fall out of support too soon.

High-value reminders:

• Lifecycle matters: End-of-life operating systems and devices are security risks because patches and vendor support may stop.
• Compatibility has layers: Hardware compatibility, driver compatibility, app compatibility, file compatibility, file-system read/write compatibility, account compatibility, and management compatibility are separate checks.
• File systems change the answer: FAT32, exFAT, NTFS, ReFS, ext4, XFS, and APFS differ in platform support, file size limits, permissions, encryption, snapshots, reliability, and recovery options.
• Mobile OSs are not desktop OSs: iOS, iPadOS, and Android are built around app stores, touch interfaces, mobile management, permissions, and cloud accounts.
• Cloud-first does not mean offline-proof: Chrome OS and web apps can be excellent, but the network, account, browser, extension, and offline requirements still matter.
• Vendor rules shape support: Apple, Microsoft, Google, Linux distribution maintainers, hardware OEMs, and carriers all affect updates and compatibility.
• Security is platform-specific: Know the common controls for each ecosystem, but never assume any OS is automatically safe without updates, least privilege, backups, and user awareness.

Technician mindset:

• Ask what the user needs to do before choosing what OS sounds familiar.
• Check the supported path first: vendor documentation, system requirements, update lifecycle, app support matrix, and device management policy.
• Separate "the data can transfer" from "the application can run." Those are different questions.
• Before formatting a drive, confirm the required OS compatibility, maximum file size, security features, reliability needs, and backup status.
• Document why a platform was chosen or rejected so the user understands the technical, security, lifecycle, and business reasons.