CompTIA A+ Core 2 Course Notes

Core operating-system questions often ask for the least disruptive fix that still solves the problem. A clean Windows reinstall removes apps, settings, and personal files, so it fits severe corruption, repurposing, or reset scenarios. An in-place upgrade keeps existing data and applications, making it the better choice when the goal is to repair or upgrade Windows while preserving the user environment.

Advanced operating-system tasks usually involve storage expansion, platform updates, or startup recovery. Extending a basic Windows volume requires usable unallocated disk space in the correct location, so the exam may test why a volume cannot be extended even though free space exists somewhere on the drive.

Security basics questions test whether the candidate can choose the control that directly reduces the stated risk. Least privilege limits users and processes to only the access needed for authorized work. That idea applies broadly across accounts, file permissions, administrative tools, and shared systems.

Multifactor authentication reduces the risk of password-only compromise by requiring another proof of identity. The exam may describe a sign-in that must require something beyond a password, such as an authenticator prompt, hardware token, biometric factor, or one-time code. MFA is strongest when it is paired with sound account management and recovery procedures.

Software troubleshooting questions usually reward evidence gathering before reinstalling or replacing components. Event Viewer and Windows event logs help connect crashes, service failures, driver problems, and blue screen timing to recorded system events. Stop codes are clues, not final answers; they guide the next diagnostic step.

Startup and browser cleanup questions test whether the technician can remove the cause without overcorrecting. If Windows is slow after sign-in, inspect startup applications and disable unnecessary entries before reinstalling software. If Chrome shows redirects, pop-ups, or suspicious behavior, review extensions and remove unwanted or unsafe items.

Operational preparation questions focus on reducing risk before work starts. A change record should define the work, affected systems, risk, approvals, timing, and rollback plan. Without those details, a technician may make a technically correct change that is still unsafe because the organization cannot recover cleanly or communicate impact.

Operational workflow questions test whether a technician follows repeatable process instead of improvising. A reliable backup plan uses multiple copies, different storage types, and at least one offsite or offline copy. Restore testing proves that the backups are usable and that recovery objectives are realistic, not just written in a plan.