Study guide · Core 2 · Domain 9 · 21% of the Core 2 exam
Operational Procedures: the CompTIA A+ objectives in plain English
Domain 9 is the operational procedures domain for CompTIA A+ Core 2 (220-1202), where it appears as Core 2 Domain 4. It covers how technicians document work, manage change, back up and recover workstations, work safely, control the environment, handle policy and licensing issues, communicate professionally, use basic scripts, and support users remotely. At 21 percent of the Core 2 exam, it rewards steady process, because scenario questions often turn on doing the right step in the right order and recording what happened.
What the objectives cover
4.1 Documentation and support systems information management
Good documentation is the memory of the support team. A ticketing system records who reported an issue, the symptoms, the affected device or service, the business impact, the priority, the assigned technician, and every action taken until closure. Clear categories and status updates let managers spot repeat problems and balance workload. Asset management and inventory track what the organization owns, where it is, who uses it, and its warranty, age, and configuration. A knowledge base stores tested fixes, standard procedures, and answers to common questions so technicians solve repeat issues the same way. When you document findings, actions, and outcomes, write for the next technician: what you observed, what you tested, what changed, and what remains open, without passwords or private data in the ticket.
4.2 Basic change management concepts
Change management controls how planned changes to systems, networks, and applications are proposed, reviewed, and carried out so a fix in one place does not cause an outage in another. Every change starts with a purpose and a scope that state what will change, what will not change, who is affected, and when the work will happen. Risk analysis weighs the likelihood and impact of failure and the time needed to recover. Approvals come from the system owner and, for larger changes, a change advisory board that checks timing and conflicts. A tested rollback plan explains how to return to the prior state if the change fails. End user acceptance confirms the change works for the people who use it, and full documentation closes the record with results and follow up tasks.
4.3 Workstation backup and recovery methods
Backup questions test both the type of copy and the order needed to restore it. A full backup copies all selected data, so it is simple to restore but takes the most time and space. An incremental backup copies only data changed since the last backup of any type. To restore, you need the last full backup plus every incremental backup since that full, applied in order, so a missing incremental breaks the chain. A differential backup copies data changed since the last full backup and grows each time. To restore, you need only the last full backup plus the latest differential, which makes recovery simpler but each copy larger. A synthetic full backup builds a new full image from a prior full and later incrementals on the backup server. Rotation schemes reuse media in a planned cycle, restore points capture system state for quick rollback, recovery media boots a failed machine for repair, and regular test restores prove the backups actually work.
4.4 Common safety procedures
Safety procedures protect you, the equipment, and everyone nearby. Electrostatic discharge can damage components without a visible spark, so use an anti static wrist strap and mat, keep parts in anti static bags, and work at the same ground potential as the equipment. Air filtration and regular cleaning reduce dust that traps heat and clogs fans. Batteries, toner, cleaning chemicals, and electronic waste can be hazardous, so follow local rules and vendor guidance for recycling and disposal, and never place batteries or electronics in ordinary trash where rules prohibit it. Personal safety comes first: lift heavy equipment with help, remove jewelry and loose clothing, watch for sharp edges and hot surfaces, disconnect power before opening cases where required, and stop work if a condition feels unsafe.
4.5 Environmental impacts and local environmental controls
The work environment affects reliability as much as configuration does. Keep temperature and humidity within the ranges the equipment maker recommends: heat shortens component life and causes shutdowns, air that is too dry raises static risk, and air that is too humid can cause condensation and corrosion. Ventilation needs clear intake and exhaust paths and space around racks and workstations so hot air can leave. Power problems come in three forms the exam separates. A surge is a brief spike in voltage, a brownout is a temporary drop in voltage, and a blackout is a complete loss of power. A surge protector absorbs spikes but provides no battery power during an outage. A UPS, or uninterruptible power supply, adds battery backup so systems keep running briefly and can shut down cleanly. Material safety data sheets describe the hazards, handling, storage, and first aid for chemicals used in cleaning and maintenance.
4.6 Processes for prohibited content and activity, privacy, licensing, and policy concepts
When prohibited content or activity is suspected, follow policy and treat the first steps as incident response, not as cleanup. Identify and report the issue through the proper channel, preserve evidence, avoid deleting files or rebuilding the machine, and escalate to the team that handles incidents. Chain of custody documents who collected evidence, when they collected it, how it was stored, and every transfer, so the record stays trustworthy. Acceptable use policies state what company systems and networks may be used for and what is prohibited. Licensing turns on how software may be installed and used: personal, corporate, single user, concurrent use, and open source terms each set different limits. An end user license agreement is the contract the user accepts for that software. Digital rights management controls copying and use of protected media and software. Learn to recognize personally identifiable information and payment card information covered by PCI rules, and handle both only through approved systems.
4.7 Proper communication techniques and professionalism
Professional communication is a technical skill because it controls how quickly you learn the real problem and how much the user trusts the fix. Start with active listening: let the user finish, restate the issue in your own words, ask open questions, and avoid offering a solution before the symptoms are clear. Show cultural sensitivity and respect for differences in language, customs, and comfort with technology, and adjust your wording without changing the facts. With difficult customers, stay calm, avoid arguing, focus on the problem, and offer clear next steps within your authority. Set expectations early about what you can do, how long it may take, and how updates will arrive. Document the conversation in the ticket, meet promised timelines or explain changes promptly, and follow up after the fix to confirm the issue is resolved before you close the work.
4.8 Basics of scripting
Scripting automates repeat tasks such as mapping drives, copying files, checking services, installing software, and collecting system information. The exam expects you to recognize common file types by extension. A .bat file is a Windows batch script. A .ps1 file is a Windows PowerShell script with access to deep system management features. A .sh file is a shell script used on Linux and macOS systems. A .py file is a Python script used across platforms. Scripts save time and reduce manual errors when they are tested, documented, and run with the least rights needed. They also carry risk. An untrusted script can delete data, change security settings, install unwanted software, or expose credentials, quickly and across many machines. Test scripts from unknown sources in a safe environment first, verify the source, and never run code you do not understand with administrator rights.
4.9 Remote access technologies
Remote access lets a technician see and control a system without traveling to the desk, but each tool needs the right setup and safeguards. RDP, or Remote Desktop Protocol, is built into Windows for remote control of another Windows computer and should be limited to approved accounts and networks. SSH, or Secure Shell, gives encrypted command line access to Linux, macOS, and network devices. A VPN, or virtual private network, creates an encrypted connection into a private network so remote users can reach internal resources as if they were on site. Third party remote support tools can work across platforms for one time help sessions, often with a code the user provides. Security considerations apply to all of them: require strong sign in and multifactor authentication where available, grant access only for the time and systems needed, keep tools patched, confirm the identity of the person requesting help, end sessions when work is done, and record the session in the ticket.
Worked example
A department reports that its shared printer is offline during a busy morning. When a technician creates the support ticket, which set of details will be most useful for tracking and resolving the issue?
A ticketing system works as the shared record for an incident. Recording symptoms, the asset, impact, priority, ownership, and contact details lets the team track status, hand the work over cleanly, and update the requester.
Why the other options are wrong
- AOnly the name of the person who called, with the ticket left unassigned until someone is free: An unassigned ticket with almost no detail can be overlooked and gives the next technician nothing to work from.
- CA short note that a printer is broken, with all troubleshooting kept in a personal notebook: Private notes are not visible to the team and do not support tracking, reporting, or handover.
- DThe steps used to fix a similar printer last year, without recording the current symptoms: Past fixes may help later, but the current symptoms and impact must be recorded first so the right priority is set.
Acronyms and terms in this domain
| Term | What it means |
|---|---|
| ESD | Electrostatic Discharge, a sudden flow of static electricity that can damage sensitive components |
| UPS | Uninterruptible Power Supply, a battery backup device that keeps systems running briefly during a power loss |
| MSDS | Material Safety Data Sheet, a document that describes the hazards, handling, and first aid for a chemical product |
| EULA | End User License Agreement, the contract that states how a user may install and use a software product |
| DRM | Digital Rights Management, technology that controls copying, sharing, and use of protected media and software |
| PII | Personally Identifiable Information, data that can identify a person, such as a name paired with a government identifier |
| PCI | Payment Card Industry, the standards body and rules that govern how payment card data must be protected |
| RDP | Remote Desktop Protocol, the Microsoft protocol for connecting to and controlling another Windows computer remotely |
| SSH | Secure Shell, an encrypted protocol for remote command line access to systems and network devices |
| CAB | Change Advisory Board, the group that reviews, approves, and schedules significant changes |
Where the help desk meets this domain
You meet this domain in the habits that surround the fix itself. Every ticket you write well saves the next technician a phone call, because the symptoms, asset, impact, and steps are already in the record instead of in a private notebook. Asset records tell you the age, warranty, and history of a failing laptop before you order parts. Knowledge base articles turn a fix you worked out once into a standard answer the team can reuse. Change windows, approvals, and rollback plans are the reason a server update happens on a planned evening with a way back, rather than on a busy morning with no recovery option.
The same habits protect people and data. You put on a wrist strap before handling memory, check a safety data sheet before using a cleaner, and plug a critical workstation into a UPS so a brief outage does not corrupt work. You verify a backup by restoring a file, not by trusting a green check mark. When a user is frustrated, you listen, restate the problem, set an expectation, and follow up. When you connect remotely, you confirm who you are helping, use an approved tool, and note the session in the ticket.
Traps to watch for
Backup restore chains are the sharpest trap in this domain, because incremental and differential sound alike and work in opposite ways. An incremental restore needs the last full backup plus every incremental since that full, in order. If one incremental in the middle is missing or damaged, the restore cannot continue past that point, even if later incrementals are fine. A differential restore needs only the last full backup plus the latest differential, because each differential already contains everything changed since the full. A choice that asks for every differential in order, or that restores an incremental from the latest copy alone, reverses the rules. Name the backup type in the stem before you count the files the restore requires.
Power and process wording creates a second set of traps. A surge protector does not keep a computer running during a blackout, and a UPS does not replace a backup. For incidents involving prohibited content, the trap answer is usually to delete, clean, or rebuild right away. The correct first steps are to report, preserve evidence, maintain chain of custody, and escalate. If a choice skips documentation, approval, or evidence handling, read it as a warning sign.
Now try it. The 3 free sample questions for this domain are in practice mode, with full explanations.
Practice Domain 9 questions