This chapter covers Chrome OS as it appears on the CompTIA A+ 220-1102 exam, specifically under Objective 1.6: 'Given a scenario, configure Microsoft Windows, Chrome OS, and Linux settings.' Chrome OS is a lightweight, cloud-centric operating system primarily found on Chromebooks, and the exam expects you to know its key features, settings, and management tools. While Chrome OS questions are not the most numerous—roughly 5-8% of the Operating Systems domain—they are often straightforward if you understand the cloud-first architecture and common configuration tasks.
Jump to a section
Imagine a public library where patrons can use designated computer terminals. Each terminal is a stripped-down device: it has a screen, keyboard, and mouse, but no local storage for applications or user files. When a patron logs in, the terminal connects to the library's central server, which verifies their identity and loads a personalized session from the cloud. All applications run on the server, and the terminal only displays the interface and sends input back. If a terminal crashes, the patron simply moves to another terminal, logs in again, and resumes exactly where they left off because all data is stored centrally. The library's IT staff can manage all terminals from a single console, pushing updates and security policies simultaneously. This is exactly how Chrome OS works: the operating system is minimal, relying on cloud services for storage, applications, and user profiles. Each Chromebook is essentially a terminal for Google's ecosystem, with automatic updates and sandboxed security. The analogy breaks down only in that Chromebooks do have some local caching and can run Android apps locally, but the core model of a lightweight client connecting to cloud services holds true.
What is Chrome OS and Why It Exists
Chrome OS is a Linux-based operating system designed by Google, first released in 2011. It is built around the Google Chrome web browser as its primary interface and relies heavily on cloud computing. The core philosophy is simplicity, security, and speed. Unlike traditional operating systems like Windows or macOS, Chrome OS is not designed to run heavyweight local applications; instead, it runs web apps (via Chrome) and Android apps (via the Google Play Store). It also supports Linux applications through a containerized environment (Crostini) on newer models.
The exam focuses on Chrome OS because it represents a growing segment of the computing market, especially in education and enterprise settings. A+ technicians must be able to support Chromebooks, including enrolling devices, managing settings, and troubleshooting common issues.
How Chrome OS Works Internally
Chrome OS uses a layered architecture: - Kernel: Based on the Linux kernel, but heavily modified for security and performance. It uses a specific kernel configuration that supports verified boot and read-only root filesystem. - Browser: The Chrome browser is the window manager and the primary user interface. All system settings are accessed via Chrome's settings page (chrome://settings). - Security: Chrome OS implements a defense-in-depth strategy: - Verified Boot: Each time the device boots, it checks cryptographic signatures of the kernel and system partitions. If tampering is detected, it attempts to repair itself or prompts the user. - Sandboxing: Each tab, plugin, and app runs in its own sandbox, preventing one compromised component from affecting others. - Read-Only Root Filesystem: The system partition is mounted read-only, preventing malware from modifying system files. - Automatic Updates: The OS updates automatically in the background, and after a reboot, the device runs the latest version. Updates are applied to an inactive partition, so the device is never left in a partially updated state. - User Data: User files are stored in the cloud via Google Drive, with local caching for offline access. The local user data partition is encrypted using per-user encryption keys. - App Support: Three types of apps can run: - Web Apps: Accessed through Chrome, they run in the browser. - Android Apps: Supported through the Android subsystem (ARC++ or ARCVM), allowing apps from the Google Play Store. - Linux Apps: Available on devices that support Crostini, a Debian Linux container.
Key Components, Values, Defaults, and Timers
Chrome OS Versioning: Chrome OS uses a version number similar to Chrome browser (e.g., 90.0.4430.100). Stable, Beta, and Dev channels are available.
Powerwash: A factory reset that restores the system to its original state. It can be triggered by pressing Ctrl+Alt+Shift+R at the login screen or via Settings > Advanced > Reset settings > Powerwash.
Guest Mode: A temporary session that does not require a Google account. All data is deleted when the guest logs out.
Sign-In Restrictions: Administrators can restrict sign-in to specific users or domains via the Google Admin Console.
Enterprise Enrollment: Chromebooks can be enrolled in a Google Workspace domain for centralized management. This is typically done during initial setup (Out-of-Box Experience, OOBE) or via a forced re-enrollment after Powerwash.
Tethering: Chromebooks can share mobile data from a phone via Bluetooth or USB tethering.
Offline Access: Google Docs, Sheets, and Slides can be made available offline. Drive files can be marked as "Available offline."
Storage: Typically 16GB to 64GB of local SSD. Cloud storage is primary.
Memory (RAM): Usually 4GB to 8GB. More RAM is needed for Android/Linux apps.
Processor: ARM or x86 (Intel/AMD). ARM models are common in lower-end devices.
Configuration and Verification Commands
Chrome OS settings are primarily managed through the Chrome browser settings page (chrome://settings). Key configuration tasks include: - Network: Wi-Fi, Ethernet, VPN, and proxy settings are in Settings > Network. - Printing: Chrome OS supports Google Cloud Print (deprecated, replaced by native printing) and CUPS for local printers. Add printer via Settings > Advanced > Printing and scanning. - Display: Settings > Device > Displays for resolution, orientation, and multiple monitors. - Accessibility: Settings > Accessibility for magnification, high-contrast, screen reader (ChromeVox), and keyboard shortcuts. - Keyboard Shortcuts: Ctrl+Alt+? displays a list of shortcuts. - Developer Mode: Enables access to a root shell (crosh) and the ability to run unsigned code. Not recommended for production. Enable by pressing Esc+Refresh+Power at startup, then Ctrl+D.
For advanced troubleshooting, Chrome OS has a built-in command shell called crosh (Chrome OS Shell). Open it by pressing Ctrl+Alt+T. Useful commands include:
- ping, traceroute, ssh
- top (process viewer)
- memory (memory info)
- storage (storage info)
- network_diag (network diagnostics)
- battery_test (battery health)
- help (list of commands)
How Chrome OS Interacts with Related Technologies
Google Workspace: Integration with Gmail, Calendar, Drive, Docs, etc. Single sign-on (SSO) via Google accounts.
Active Directory: Chromebooks can be joined to an Active Directory domain for enterprise management, allowing Windows-based policies.
Third-Party MDM: Chrome OS supports Mobile Device Management (MDM) via Google Admin Console or third-party MDM solutions.
Virtual Private Networks (VPN): Built-in support for L2TP/IPsec, OpenVPN, and IKEv2.
Linux Apps (Crostini): Runs a Debian container with its own terminal, allowing developers to use Linux tools like VS Code, Git, etc.
Android Apps: Google Play Store integration, but not all Android apps are optimized for Chromebooks.
Chromecast: Built-in Cast functionality allows streaming to Chromecast devices.
Nearby Share: Share files with nearby Chromebooks or Android devices.
Chrome OS vs. Chromium OS
It is important not to confuse Chrome OS with Chromium OS. Chromium OS is the open-source project that Chrome OS is based on. Chrome OS adds proprietary components like the Google Chrome browser, media codecs, and automatic updates. The exam expects you to know that Chrome OS is the commercial product found on Chromebooks, while Chromium OS is used by developers and can be built from source.
Power On and Verified Boot
When the user presses the power button, the firmware (coreboot or UEFI) starts. It loads the bootloader, which checks the cryptographic signature of the kernel partition (KERN-A or KERN-B). If the signature is valid, the kernel is loaded; if not, the device attempts to boot from the other kernel partition. If both fail, the device enters recovery mode. This process ensures that only trusted code runs, preventing rootkits and system-level malware. The entire boot process takes about 8-15 seconds on modern hardware.
User Login and Authentication
The user is presented with a login screen. They enter their Google account credentials (username and password). The device contacts Google's authentication servers to verify the account. If the device is enterprise-enrolled, it also checks for device policies. The user may also use two-factor authentication (2FA) if enabled. Once authenticated, the user's profile is downloaded from the cloud, including bookmarks, extensions, and settings. For guest mode, no authentication is needed, and a temporary profile is created.
Cloud Sync of User Data
After login, Chrome OS syncs user data from Google servers. This includes browsing history, passwords, open tabs, apps, and settings. The sync is encrypted and happens over HTTPS. Files in Google Drive are synced based on offline settings. The user can choose which data to sync in Settings > Sync and Google services. If the network is slow or unavailable, the device uses locally cached data and syncs later.
Running Applications
The user can launch web apps from the Chrome browser, Android apps from the Play Store, or Linux apps from the Terminal. Web apps run in sandboxed tabs. Android apps run in a container (ARC++) that provides Android compatibility. Linux apps run in a Debian container (Crostini) with its own virtual machine. Each type has different performance and security characteristics. The user can pin apps to the shelf (taskbar) for quick access.
Automatic Update and Reboot
Chrome OS checks for updates periodically. When an update is available, it downloads in the background and applies it to the inactive partition (A or B). The user is notified to restart to activate the update. After restart, the device boots from the updated partition. If the update fails, the device can fall back to the previous partition. This A/B partition scheme ensures that the device always has a working OS. The update process does not affect user data.
Shutdown or Sleep
When the user closes the lid or presses the power button, the device enters sleep (suspend-to-RAM) to save power. After a period of inactivity (default 6 minutes on battery, 15 minutes on AC), it may enter deep sleep (suspend-to-idle). The user can also shut down via the power menu. On shutdown, the system unmounts partitions and powers off. The fast startup feature (similar to Windows fast startup) is not used; Chrome OS boots fresh each time.
Enterprise Deployment in Education
A large school district deploys 10,000 Chromebooks to students. The IT department uses the Google Admin Console to enroll devices, apply policies (e.g., block incognito mode, restrict sign-in to school domain), and push apps. They create organizational units (OUs) for different grades, each with specific settings. For example, elementary students have restricted access to certain websites, while high school students have access to Linux apps for coding classes. The devices are managed centrally; if a student's Chromebook is lost or stolen, IT can remotely wipe it. Common issues include students bypassing restrictions by using guest mode (which IT disables via policy) or using VPNs to access blocked content (IT blocks VPN apps). The scale means that automatic updates must be staggered to avoid bandwidth congestion; IT uses the Admin Console to schedule updates during off-hours.
Enterprise Deployment in Business
A mid-size company uses Chromebooks for frontline employees who need access to email, web apps, and a few Android apps for inventory management. The IT team integrates Chrome OS with Active Directory for single sign-on and uses third-party MDM to enforce compliance policies. They also set up secure printing via Google Cloud Print (now replaced with native printing) and use VPN for remote access. A common problem is users who run out of local storage because they download large files; IT educates users to use Google Drive and sets storage quotas. Another issue is that some legacy web apps require Internet Explorer; IT uses a remote desktop solution (e.g., Chrome Remote Desktop) to access a Windows VM.
Troubleshooting Common Issues
Boot loop: Often caused by corrupted firmware. Use recovery media (a USB drive with Chrome OS recovery image) created using the Chromebook Recovery Utility extension on another device.
Wi-Fi connectivity: Use the network diagnostics in crosh (network_diag) to check signal strength and DNS. Reset network settings via Settings > Network > Wi-Fi > Forget network.
Battery not charging: Check battery health with battery_test in crosh. If capacity is below 80%, consider replacement.
Android apps not working: Clear the Android app cache via Settings > Apps > Google Play Store > Clear cache. If that fails, reset the Android subsystem via Settings > Apps > Google Play Store > Manage Android preferences > Remove Android apps and data (this does not affect Chrome OS data).
What 220-1102 Tests on Chrome OS
Objective 1.6 requires you to configure Chrome OS settings, including network, printing, accessibility, and user accounts. The exam focuses on practical tasks a technician would perform. Specific areas tested: - Powerwash: When and how to perform it. The exam may ask: "A user wants to return a Chromebook to factory defaults. What should the technician do?" Answer: Powerwash via Ctrl+Alt+Shift+R at the login screen. - Guest Mode: Know that guest mode does not require a password and that data is deleted on logout. It can be disabled via policy. - Sign-In Restrictions: Administrators can restrict sign-in to specific users or domains. The exam may ask: "A school wants only students with @school.edu accounts to sign in. How is this configured?" Answer: Via the Google Admin Console under Device management > Chrome management > User settings. - Enterprise Enrollment: Know that enrollment is done during OOBE or via forced re-enrollment. The device must be in the domain's device list. - Developer Mode: Be aware that Developer Mode disables some security features and is not recommended for production. It allows running unsigned code but voids warranty. - Crostini (Linux Apps): The exam may ask about enabling Linux apps via Settings > Developers > Linux development environment. - Recovery Mode: How to enter (Esc+Refresh+Power) and use a recovery USB.
Common Wrong Answers and Why
Wrong: "To reset a Chromebook, reinstall Windows." — Chromebooks run Chrome OS, not Windows. The correct answer is Powerwash.
Wrong: "Guest mode saves data to the cloud." — Guest mode is temporary; all data is deleted when the guest logs out.
Wrong: "Chrome OS updates require user approval." — Updates are automatic; the user only needs to restart.
Wrong: "You need a Microsoft account to sign in." — Chrome OS uses Google accounts. For enterprise, it can integrate with Active Directory but still requires a Google account for the primary login.
Numbers and Terms That Appear on the Exam
Ctrl+Alt+Shift+R: Powerwash.
Esc+Refresh+Power: Enter recovery mode.
Ctrl+D: Skip recovery and boot (in Developer Mode).
Ctrl+Alt+T: Open crosh.
chrome://settings: Access settings.
Powerwash: Factory reset.
Guest Mode: Temporary session.
Verified Boot: Security feature.
Crostini: Linux app support.
ARC++: Android app runtime.
Edge Cases and Exceptions
Forced Re-enrollment: If a device is enrolled in enterprise, even after Powerwash, it will re-enroll automatically. This prevents users from removing management.
Offline Sign-In: If the device has never signed in before, an internet connection is required. After first sign-in, offline sign-in is possible for up to 30 days.
Multiple Users: Chrome OS supports multiple user accounts; each user has their own encrypted data partition.
Kiosk Mode: A single-app mode for public terminals. Configured via policies.
How to Eliminate Wrong Answers
Focus on the cloud-first nature. If an answer suggests storing files locally by default, it is likely wrong. If an answer suggests manual updates, it is wrong. If an answer mentions a Windows feature, it is probably wrong. Use the process of elimination: Chrome OS is simple, so the correct answers are usually the simplest and most cloud-centric.
Chrome OS is a lightweight, cloud-first OS designed for simplicity and security.
The default browser is Google Chrome; all settings are accessed via chrome://settings.
Powerwash (Ctrl+Alt+Shift+R) performs a factory reset, but does not delete cloud data.
Guest mode provides a temporary session with no saved data.
Enterprise enrollment allows centralized management via Google Admin Console.
Automatic updates use A/B partitions; the device always has a working OS.
Chrome OS supports Android apps (ARC++) and Linux apps (Crostini) on compatible hardware.
Recovery mode (Esc+Refresh+Power) is used to restore the OS from a USB drive.
Developer Mode disables some security features and is not recommended for typical users.
Offline sign-in is available for up to 30 days after last online sign-in.
These come up on the exam all the time. Here's how to tell them apart.
Chrome OS
Cloud-centric: primary storage is cloud (Google Drive).
Automatic updates with A/B partition scheme.
Minimal local storage (16-64 GB).
Apps are web, Android, or Linux containers.
Security features: verified boot, sandboxing, read-only root.
Windows 10/11
Local-centric: primary storage is local hard drive.
Updates are manual or scheduled; can be postponed.
Requires more local storage (32 GB minimum for 64-bit).
Apps are traditional Win32, UWP, or MSIX.
Security features: Windows Defender, BitLocker, UAC.
Mistake
Chrome OS is just a browser; you cannot run any real applications.
Correct
Chrome OS supports web apps, Android apps from Google Play, and Linux apps via Crostini. Many productivity and development tools are available.
Mistake
Chromebooks cannot work offline.
Correct
Chrome OS allows offline access to Google Docs, Sheets, Slides, and cached emails. Many Android apps also work offline. However, initial setup and app installation require internet.
Mistake
Powerwash deletes all user data from the cloud.
Correct
Powerwash only resets the local device. Cloud data (Google Drive, Gmail) remains intact. It removes local cached files and settings.
Mistake
Chrome OS is insecure because it is Linux-based.
Correct
Chrome OS is considered one of the most secure consumer OSes due to verified boot, sandboxing, read-only root filesystem, and automatic updates.
Mistake
You need a Google account to use a Chromebook at all.
Correct
Guest mode allows temporary use without a Google account. However, to save settings and files, a Google account is required.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Perform a Powerwash by pressing Ctrl+Alt+Shift+R at the login screen, then select 'Powerwash' and 'Continue.' Alternatively, go to Settings > Advanced > Reset settings > Powerwash. This resets the device to factory defaults but does not affect your cloud data.
Not natively. You can use remote desktop solutions (e.g., Chrome Remote Desktop) to access a Windows PC, or use Linux apps that may have compatibility layers (like Wine), but this is not officially supported and may not work well.
Go to Settings > Developers > Linux development environment and click 'Turn on.' Follow the prompts to set up the container. This installs a Debian Linux environment that can run Linux applications.
Chrome OS is the commercial product with proprietary components (Chrome browser, codecs, automatic updates). Chromium OS is the open-source project that lacks these proprietary parts and is intended for developers.
You can sign in offline if you have signed in at least once before with an internet connection. The device caches your credentials locally. Offline sign-in works for up to 30 days after the last online sign-in.
Try recovery mode: press Esc+Refresh+Power. If the device shows a recovery screen, insert a USB drive with a Chrome OS recovery image (created using the Chromebook Recovery Utility on another computer). Follow on-screen instructions to reinstall Chrome OS.
Open crosh by pressing Ctrl+Alt+T, then type `battery_test`. This shows battery health percentage and discharge rate. A healthy battery should be above 80% capacity.
You've just covered Chrome OS for A+ — now see how well it sticks with free 220-1102 practice questions. Full explanations included, no account needed.
Done with this chapter?