Operating systems

Two techs face the same broken PC and the exam still wants one answer, not a debate. That is the shape of nearly every question in this domain: it hands you a situation and rewards the single path or tool that owns it, chosen to disturb as little as possible. It helps to picture an operating system (OS) as having a lifecycle, where you install and set it up, then run and repair it, then keep its storage formatted and its patches current. Operating systems is one of the two largest domains on the 220-1202 exam at 28 percent, tied with Security, so this matching instinct repays knowing cold. The classic trap is reaching for the biggest hammer: running a clean install to fix a single corrupt file when a repair install or a Reset with Keep my files would have saved the data, or opening the wrong tool entirely, such as MSConfig to close a hung app. Scope the action to the fault, then match the fault to the one thing that owns the job.

The guide walks the operating system's life in order. OS Installation & Configuration is getting the system onto the machine and configured for first use: pick the install path by what must survive it (a clean install wipes the volume, an in-place upgrade keeps apps and files, image deployment clones one image onto many PCs, a repair install fixes corruption in place), match the firmware to the partition style (UEFI (Unified Extensible Firmware Interface) boots a GPT (GUID Partition Table) disk while legacy BIOS boots an MBR (Master Boot Record) disk), then finish the out-of-box experience (OOBE) with the right account type and the first round of updates. Windows Management Tools is the running system's toolbox: match a live symptom to the one console that owns it, such as Task Manager for a resource hog, Device Manager for a hardware fault, Disk Management for a volume, or Event Viewer for a logged failure, or to the one command that carries the repair, such as sfc and DISM for corrupted system files or ipconfig for a network glitch. File Systems & Updates is how storage is formatted and how the OS stays current: choose a file system by cross-platform reach and the largest single file it must hold (NTFS for a Windows drive, exFAT for large cross-platform media, FAT32 only where compatibility forces it), reason about share versus NTFS permissions, and patch on a cadence rather than never. Read the pages in that order and each one builds on the last.

A+ operating-system questions rarely turn on raw capability. When two options would both technically succeed, the credited answer is usually the one that preserves data and matches the exact standard, not the most drastic move or the biggest number. Preserve first: a repair install or Reset with Keep my files before a clean wipe, an in-place upgrade before a reinstall when the apps must stay, sfc then DISM before rebuilding Windows, and mbr2gpt to convert a disk in place rather than erasing it. Fit the standard second: UEFI pairs only with GPT, Windows 11 will not install without a TPM 2.0 (Trusted Platform Module) and Secure Boot, and FAT32 refuses any single file of 4 GB or larger. Speed and convenience are tie-breakers you reach for only after data safety and the documented requirement are settled.