Chapter 4
Operational Procedures
It's 8:47 on a Monday morning. Your ticketing queue already has fourteen open tickets, a manager is hovering because the finance server "felt slow" on Friday, and a user just called to report that her computer is "making a smell." Welcome to operational procedures — the part of the A+ exam that tests whether you can do the job like a professional, not just like a hobbyist who knows what RAM is.
Domain 4.0 is worth 23% of the Core 2 exam, making it one of the heaviest domains on the test. And it's the domain most people underestimate, because it doesn't feel "technical." There are no command-line switches to memorize here, no port numbers. Instead, CompTIA tests judgment: what do you do first when a customer is angry? What do you do before you open a case? Which backup type restores fastest? These are scenario questions, and they reward technicians who think in terms of process, safety, and professionalism.
The good news: this domain is extremely learnable. Every topic here maps to a real workplace situation you've either lived through or can easily imagine. Let's walk through them the way they'd actually happen.
4.1 Communication and Professionalism: The Human Operating System
Here's an uncomfortable truth the exam wants you to accept: the most technically skilled technician in the building is useless if customers dread calling them. CompTIA devotes significant exam weight to "soft skills" because in the real world, how you communicate determines whether problems get solved or get worse.
Active Listening: The Most Underrated Diagnostic Tool
A user calls the help desk: "My computer is broken. It won't do anything. This always happens. I have a deadline in an hour."
The rookie technician hears "computer broken" and starts troubleshooting hardware. The professional hears a stressed human being and starts by listening. Active listening means giving the speaker your full attention, letting them finish, and then reflecting back what you heard: "So the computer powers on but nothing loads, and this has happened before — is that right?"
CompTIA loves "FIRST" questions about communication. When a user reports a problem, the FIRST step is to clarify and confirm the issue — not to start fixing. "Ask clarifying questions" beats "reboot the computer" as a first step almost every time.
Why does this matter technically? Because users are terrible at describing problems accurately, and they know it. "It won't do anything" could mean the monitor is off, the application crashed, or the network share disconnected. If you start "fixing" before you understand, you'll waste time solving the wrong problem — and the user's deadline still passes. Clarifying questions are diagnostics for humans.
Scenario: A teacher calls, voice shaking: "The projector died in the middle of my lecture, forty students are staring at me, and IT never helps." What's the technician's FIRST move?
A technician who jumps to "Have you tried turning it off and on again?" has failed the exam and the teacher. The right first move is empathy plus clarification: "I understand — that's stressful with a full class waiting. Let me help you right now. When you say it died, is the projector completely dark, or is there a message on screen?" You've acknowledged the stress, established urgency, and started gathering the one detail that determines the fix. That's professionalism under pressure, and it's exactly what the exam tests.
Speaking Human: Jargon Is a Foreign Language
"Your DHCP lease expired so the APIPA address couldn't resolve the gateway" is a true statement that helps nobody. The professional version: "Your computer lost its network address, so it couldn't reach the internet. I've fixed it."
Rules CompTIA expects you to follow:
- Avoid jargon and acronyms with non-technical users. If you must use a technical term, explain it simply.
- Avoid being judgmental or condescending. Never blame the user. "You clicked the wrong thing" is forbidden; "Let's see what happened here" is the move.
- Don't argue with customers. Even when they're wrong. Especially when they're wrong.
- Set expectations honestly. "This will take about twenty minutes" beats "I'll get to it soon." If you can't meet a deadline, say so early and offer alternatives.
A classic exam trap: a user is frustrated and the technician responds with technical jargon to "prove" competence. CompTIA considers this unprofessional. The correct answer in communication scenarios is almost always the choice involving plain language, empathy, and clarifying questions — never the one where the technician shows off, argues, or blames.
Cultural Sensitivity and Professional Presence
IT support serves everyone: different cultures, ages, abilities, and levels of technical comfort. Cultural sensitivity means respecting differences in communication style, personal space, and expectations without stereotyping. Practical exam-relevant points:
- Maintain a professional appearance and demeanor — you represent the IT department.
- Be mindful of personal space and physical contact; ask before touching someone's equipment ("May I take a look at your laptop?").
- Respect privacy: don't read what's on a user's screen beyond what's needed for the task, and never comment on personal files, photos, or messages you happen to see.
- If there's a language barrier, speak slowly and clearly, avoid slang and idioms ("let's reboot this bad boy" confuses non-native speakers), and confirm understanding.
The Difficult Customer Playbook
Sooner or later you'll get the caller who is already furious before you say hello. The exam tests a specific de-escalation sequence:
- Stay calm. Your emotional state sets the ceiling. If you get defensive, the situation escalates.
- Listen without interrupting. Let them vent. Most anger deflates once someone feels heard.
- Empathize explicitly. "I understand this is frustrating" isn't empty — it signals you're on their side.
- Don't take it personally. They're angry at the situation, not at you.
- Focus on the solution. Shift from the problem to the fix: "Here's what I'm going to do right now."
- Know when to escalate. If a customer is abusive or threatening, or the issue is beyond your authority, escalate to a supervisor. That's professionalism, not surrender.
The golden rule of exam communication questions: the technician's job is to solve the problem while preserving the relationship. Any answer choice involving arguing, blaming, jargon-dumping, or rushing the user is wrong. The right answer involves listening, clarifying, empathizing, and setting clear expectations.
Follow-Up: The Step Everyone Skips
After resolving an issue, the professional follows up: "Is everything still working well since yesterday's fix?" and documents the resolution. Follow-up catches recurring problems early and builds trust. CompTIA's troubleshooting methodology for Core 2 explicitly includes verifying functionality and documenting findings — communication doesn't end when the ticket closes.
4.2 Safety First: Protecting People and Equipment
Before you touch a single component, the exam wants you to think about safety — yours, the user's, and the equipment's. Safety questions are heavily tested and almost always have a clear right answer once you know the principles.
ESD: The Invisible Killer
Electrostatic discharge is the silent destroyer of computer components. Here's the scary part: you can feel a static shock at around 3,000 volts, but it takes as little as 30 volts to damage sensitive electronics. That means you can destroy a component with a discharge you never felt.
How it happens: walking across carpet, sliding in a chair, or wearing certain fabrics builds static charge on your body. Touch a motherboard trace or RAM contact, and the charge equalizes through the component — frying microscopic circuits.
Prevention (know all of these):
- Antistatic wrist strap: worn snugly on bare skin, clipped to an unpainted metal part of the case or a grounding point. This keeps you and the equipment at the same electrical potential.
- Antistatic mat: work on a grounded ESD mat, not carpet or a plastic table.
- Equalize potential: before handling components, touch the metal chassis to discharge yourself.
- Proper handling: hold boards by the edges, never touch gold contacts, traces, or chips. Store components in antistatic bags.
- Environmental: maintain proper humidity (more on this in 4.3) — dry air increases ESD risk.
The single most-tested ESD fact: use an antistatic wrist strap (or mat) BEFORE handling internal components. If a scenario asks what the technician should do FIRST before opening a case or touching RAM, the answer is ESD protection — not "power off the system." (Though you should do that too. ESD protection is the safety-specific answer CompTIA wants.)
EMI and RFI: Invisible Noise
Electromagnetic interference (EMI) and radio frequency interference (RFI) are disruptions caused by electromagnetic fields from nearby equipment — motors, microwaves, fluorescent lighting, radios, even poorly shielded cables. Symptoms look like flaky hardware: intermittent network drops, display distortion, data corruption.
Mitigation:
- Keep sensitive equipment away from interference sources.
- Use shielded cabling (STP instead of UTP in noisy environments).
- Ensure proper grounding.
- Don't run data cables parallel to power cables over long distances.
Power Safety: Respect the Juice
Inside a power supply unit, capacitors can hold a dangerous charge long after the system is unplugged. Rules:
- Never open a PSU. No user-serviceable parts inside — replace, don't repair.
- Unplug the system before working inside it (and use the PSU's power switch too, for good measure).
- Don't wear jewelry (rings, watches, necklaces) when working inside systems — metal conducts, and a ring across a live circuit causes burns.
- In data centers, know where emergency power-off switches are.
Handling Equipment and Personal Safety Basics
- Lift properly: servers and UPS units are heavy. Bend at the knees, keep the load close, get help for anything over ~50 lbs (23 kg).
- Cable management: route cables so nobody trips. A tangled floor cable is a workplace injury waiting to happen — and a disconnected server.
- Fire safety: know your extinguisher types. Electrical fires need a Class C extinguisher (or multipurpose ABC). Never use water on an electrical fire.
- Air filtration/masks: when cleaning dusty systems with compressed air, dust goes everywhere — work in ventilated areas.
- Sharp edges: case panels and rack rails can cut. Handle with care.
Scenario: A technician arrives to replace a failed hard drive in a user's desktop. The user is standing nearby, eager to help. What's the correct sequence?
First, the technician puts on the antistatic wrist strap and powers down/unplugs the system — safety before service. Politely ask the user to step back (their static-prone sweater is a threat to the new drive). Replace the drive holding it by the edges, avoiding the circuit board. Before closing up, verify the drive is detected. The exam loves this kind of ordered-thinking question: safety gear first, then power down, then handle components correctly.
4.3 Environmental Controls: The Room Has Opinions Too
Computers are picky about their environment. Server rooms and data centers have strict environmental controls, and even office desktops suffer when conditions are wrong. CompTIA tests the ideal ranges and the consequences of getting them wrong.
Temperature and Humidity: The Goldilocks Zone
- Temperature: recommended server room range is roughly 64–81°F (18–27°C), with many guidelines targeting 68–77°F (20–25°C). Too hot → components overheat, thermal throttling, shortened lifespan. Too cold → condensation risk when equipment warms up.
- Humidity: target 40–60% relative humidity. Too low → ESD risk skyrockets (dry air can't dissipate static charge). Too high → condensation and corrosion on contacts and boards.
Humidity questions are a favorite trap. Low humidity causes electrostatic discharge problems; high humidity causes condensation and corrosion. If a scenario describes frequent ESD damage in a server room, the environmental fix is to RAISE humidity (add a humidifier) — not lower it.
Dust, Airflow, and Cleanliness
Dust is an insulator — it blankets heat sinks and fans, raising temperatures and causing overheating. It also carries static charge. Controls:
- Positive-pressure airflow with filtered intakes keeps dust out of server rooms.
- Hot-aisle/cold-aisle arrangement in data centers separates intake and exhaust air.
- Regular cleaning with antistatic vacuums or compressed air (never a household vacuum — they generate massive static).
- Keep food and drinks away from equipment. (Yes, this is exam-relevant. Coffee and keyboards are ancient enemies.)
Power Protection: Surge Suppressor vs. UPS
This distinction is heavily tested, so learn it cold.
| Device | What it does | What it does NOT do |
|---|---|---|
| Surge suppressor | Clamps voltage spikes, protecting against surges. Rated in joules — higher is better. | Provide power during an outage. Once the power's out, it's out. |
| UPS (uninterruptible power supply) | Battery backup that keeps systems running during outages, plus surge protection and power conditioning. | Run forever — it buys minutes, not hours, so you can save work and shut down gracefully. |
Power problems to know:
- Surge/spike: brief voltage increase (lightning, grid switching). Damages electronics.
- Sag/brownout: brief voltage drop. Causes reboots and data corruption.
- Blackout: complete power loss.
- Noise: small fluctuations that degrade power quality over time.
UPS types (good to recognize):
- Standby (offline): switches to battery when power fails. Cheapest, brief switchover gap.
- Line-interactive: handles minor sags/surges without switching to battery. The sweet spot for most offices.
- Online (double-conversion): power always flows through the battery/inverter — zero transfer time, cleanest power. Used for critical systems.
The classic scenario: "A technician wants to protect a server from data loss during brief power outages." A surge suppressor is WRONG — it offers zero outage protection. The answer is a UPS, because it provides battery runtime to save work and shut down gracefully. If the question only mentions lightning/surge damage with no outage concern, the surge suppressor is the economical right answer.
Scenario: A small office loses power for ten seconds. When it returns, three workstations have corrupted files and one won't boot. The office manager asks what to buy. The diagnosis: the brief outage (with the accompanying surge when power returned) caused the damage. Recommendation: a UPS for each workstation — or at minimum for critical systems — sized for the load, plus surge suppressors where UPS units aren't justified. And this is the moment to ask about backups (see 4.6), because power protection reduces risk but never eliminates it.
4.4 Documentation: If It Isn't Written Down, It Didn't Happen
Experienced technicians document everything. Documentation is how a one-person fix becomes organizational knowledge, how you prove what was done, and how the next technician picks up where you left off. CompTIA treats documentation as a core professional competency.
Ticketing Systems: The System of Record
Every support interaction should generate or update a ticket. A proper ticket captures:
- Who: user contact info and location
- What: problem description in the user's words plus the technician's technical translation
- When: timestamps for opened, updated, resolved
- Priority/urgency: how critical is this? (A CEO's dead laptop before a board meeting outranks a sticky spacebar.)
- Actions taken: every troubleshooting step, so nobody repeats work
- Resolution: what fixed it, for the knowledge base
Ticket hygiene matters: update tickets as you work, don't let them go stale, and close them with a real resolution note — not "fixed." Future-you (or your replacement) will thank present-you.
Asset Management, Knowledge Bases, and Other Documentation
- Asset management: track what equipment the organization owns — serial numbers, locations, assigned users, warranty status, lifecycle stage. When a laptop dies, asset records tell you if it's under warranty before you pay for a repair.
- Knowledge base: a searchable collection of known issues and solutions. "Printer X jams when using tray 2 — clean roller R4" documented once saves hours forever. Technicians should both consult and contribute to it.
- Network diagrams and floor plans: logical and physical maps of the infrastructure. Trying to troubleshoot without them is navigating without a map.
- Acceptable use policies (AUP): the rules users agree to — what's allowed on company systems. Technicians enforce and reference them.
- Incident documentation: for security events, document timeline, actions, and evidence handling carefully — it may matter legally.
Documentation isn't bureaucracy — it's how IT scales. The exam frames it as professionalism: update the ticket, contribute to the knowledge base, keep asset records current. In scenario questions, the "most professional" answer often involves documenting the issue and resolution, not just fixing and moving on.
4.5 Change Management: No Surprises
Change management is the formal process for making modifications to IT systems — and its entire purpose is preventing the 2 AM disaster caused by someone's "quick fix." CompTIA tests both the purpose and the process.
Why Change Management Exists
Every change carries risk. Updating a driver can break an application. Patching a server can take down a service. Change management doesn't prevent changes — it makes them predictable, approved, and reversible.
The Change Control Process
- Request: document what change is proposed, why, and what systems it affects.
- Assessment and approval: evaluate risk, impact, and rollback options. Get approval from the change advisory board or designated approver — the bigger the change, the higher the approval needed.
- Plan: schedule the change (often in a maintenance window — off-hours when impact is minimal), notify affected users in advance, and prepare the rollback plan.
- Implement: make the change, monitoring for problems.
- Review and document: verify the change worked, document what was done, update system documentation and the knowledge base.
The rollback plan is sacred. Before implementing any change, you must know how to undo it. "We'll figure it out if something breaks" is not a rollback plan.
Change management questions almost always hinge on two things: getting APPROVAL before the change, and having a ROLLBACK plan. If a scenario describes a technician making an unapproved change that caused an outage, the failure was skipping the process. If it asks what should have been prepared beforehand, the answer is the rollback/backout plan. Also know: changes go in maintenance windows, and users get advance notice.
Scenario: A technician wants to update the firmware on the office's core switch Friday at 2 PM because "it's just a quick update." What's wrong? Everything about the timing and process. Firmware updates on core infrastructure need a change request, risk assessment, approval, a maintenance window (not Friday afternoon when everyone is working), user notification, a verified backup of the switch configuration, and a rollback plan. The "quick update" mindset is exactly what change management exists to prevent.
4.6 Backup and Recovery: Your Parachute
Backups are the difference between "bad day" and "career-ending catastrophe." CompTIA tests backup types heavily — this is one of the most question-dense topics in the domain.
Backup Types: Know the Trade-Offs
| Backup type | What it copies | Backup speed | Restore speed | Storage used |
|---|---|---|---|---|
| Full | Everything selected | Slowest | Fastest (one set) | Most |
| Incremental | Changes since the LAST backup of ANY type | Fastest | Slowest (full + every incremental in order) | Least |
| Differential | Changes since the LAST FULL backup | Medium | Medium (full + latest differential) | Medium |
| Synthetic full | Combines a full backup with subsequent incrementals into a new "full" without touching the source system | N/A (built from existing backups) | Fast (like a full) | Like a full |
Let's make this concrete. Full backup runs Sunday night. Data changes a little each day.
- Incremental week: Mon copies Mon's changes, Tue copies Tue's changes, Wed copies Wed's changes. Each backup is tiny and fast. But if the server dies Thursday, you restore Sunday's full + Monday + Tuesday + Wednesday incrementals — in order. Lose any single incremental in the chain and everything after it is unrestorable.
- Differential week: Mon copies Mon's changes, Tue copies Mon+Tue's changes, Wed copies Mon+Tue+Wed's changes. Backups grow through the week. But restore needs only Sunday's full + Wednesday's differential. Simpler, more resilient.
The two most-tested backup facts: (1) Incremental = fastest to BACK UP, slowest to RESTORE. (2) Differential = changes since the last FULL backup (not since the last backup of any type — that's incremental). Exam questions love asking which type to choose given a priority: "fastest backup time" → incremental; "fastest restore time" → full; "balance of both" → differential.
The 3-2-1 Rule and Rotation Schemes
- 3-2-1 rule: keep 3 copies of important data, on 2 different media types, with 1 copy offsite. Ransomware can't encrypt the backup it can't reach.
- Grandfather-father-son: a rotation scheme — daily backups (sons), weekly backups (fathers), monthly backups (grandfathers). Gives you multiple restore points going back in time.
- Onsite vs. offsite: onsite is fast to restore; offsite (or cloud) survives site disasters like fire or flood. You need both.
Testing Backups and Disaster Recovery
An untested backup is not a backup — it's a hope. Backup testing means periodically performing test restores to verify the data is actually recoverable. CompTIA wants you to know this cold: the scenario where "backups ran successfully for a year but the restore failed" is a testing failure.
Disaster recovery extends backup thinking to the whole organization:
- RPO (Recovery Point Objective): the maximum acceptable data loss, measured in time. "We can afford to lose 4 hours of data" means backups at least every 4 hours.
- RTO (Recovery Time Objective): the maximum acceptable downtime. "Systems must be back within 8 hours" drives your restore strategy and spare hardware planning.
- A disaster recovery plan documents who does what, in what order, when disaster strikes — alternate sites, communication plans, and critical system priorities.
RPO = how much DATA you can afford to lose (drives backup frequency). RTO = how much TIME you can afford to be down (drives restore speed planning). Mnemonic: RPO has a "P" for "Point" — the point in time you can roll back to. RTO has a "T" for "Time" — the time until you're operational.
Scenario: A small business backs up its file server with a full backup every Sunday and incrementals nightly. The server's RAID array fails Thursday morning. Walk through the restore: you need Sunday's full backup plus Monday, Tuesday, and Wednesday's incrementals — applied in exact order. Miss Wednesday's tape and Thursday's data state is unreachable. This is why the exam stresses understanding the restore chain, not just the backup schedule. And afterward? The lesson learned goes in the knowledge base, and somebody finally tests the restores monthly.
4.7 Privacy, Compliance, and Data Handling
Technicians handle other people's data constantly — and mishandling it can end careers and trigger lawsuits. This section is about knowing what's sensitive, what the rules are, and what to do when something looks wrong.
PII, PHI, and the Alphabet Soup of Privacy
- PII (personally identifiable information): any data that identifies a person — name, address, Social Security number, date of birth, financial account numbers, even the combination of details that together identify someone.
- PHI (protected health information): health data covered by HIPAA in the US — medical records, insurance details. Stricter handling rules than general PII.
- GDPR (General Data Protection Regulation): EU privacy law with global reach — it applies to EU residents' data wherever it's processed. Key principles: data minimization (collect only what you need), purpose limitation, consent, and the right to erasure ("right to be forgotten"). Violations carry massive fines.
Practical rules for technicians:
- Access only the data you need for the task. Curiosity is not authorization.
- Never share, copy, or discuss user data outside the task.
- Follow organizational data classification and handling policies.
- When in doubt, ask — don't assume.
Data Disposal: Deleting Isn't Enough
Dragging files to the recycle bin doesn't destroy data — it just removes the pointer. Forensic tools recover "deleted" files easily. Proper disposal methods:
| Method | How it works | Notes |
|---|---|---|
| Wiping (overwriting) | Software overwrites every sector with patterns (zeros, ones, random data) | Effective for HDDs; time-consuming on large drives |
| Degaussing | Powerful magnet disrupts magnetic domains | Works on HDDs and tapes; USELESS on SSDs (no magnetic storage) — also destroys the drive |
| Physical destruction | Shredding, crushing, drilling, incineration | Most certain method; required for highly sensitive data |
| Crypto-erase | Destroying the encryption keys for an encrypted drive | Fast and effective for SSDs — without the key, the data is unrecoverable noise |
Two disposal traps to memorize: (1) Degaussing does NOT work on SSDs — they store data in flash chips, not magnetic platters. For SSDs, use crypto-erase or physical destruction. (2) Simple deletion/formatting is never sufficient for sensitive data. If a scenario asks how to dispose of drives containing PII, "delete the files" or "format the drive" is always wrong.
Acceptable Use, Prohibited Content, and Incident Response
- Acceptable use policy (AUP): defines allowed behavior on company systems. Technicians should know it and reference it when users violate it.
- Prohibited content: if you discover illegal material (or policy-violating content) on a system you're servicing — stop, don't snoop further, don't delete it, and report through proper channels (supervisor, security team). Document what you found factually.
- Incident response basics: for security incidents — identify, contain, eradicate, recover, and document. Don't power off a compromised machine before the security team says so (you might destroy volatile evidence); isolate it from the network instead.
Scenario: While migrating a user's files to a new laptop, a technician notices a folder of what appears to be another employee's payroll records on the old machine. The correct response: don't open the files out of curiosity, don't copy them, don't mention them to coworkers. Complete the migration task, and report the observation to a supervisor or the security team per company policy. The exam rewards discretion and proper reporting channels — never vigilante investigation.
4.8 Scripting Basics: Automate the Boring Parts
If you find yourself doing the same task for the tenth time, stop doing it manually and script it. Scripting is how technicians multiply their effectiveness, and CompTIA expects you to recognize the common scripting languages and what each is for.
The Languages: Who Does What
| Language | File extension | Used for |
|---|---|---|
| Batch | .bat, .cmd | Simple Windows command-line automation — running sequences of commands, basic logic |
| PowerShell | .ps1 | Windows administration and automation — manages systems, services, Active Directory, cloud resources |
| Python | .py | Cross-platform scripting — automation, data processing, utilities; readable and versatile |
| JavaScript | .js | Web scripting and automation (also Node.js for server-side) |
| Shell (Bash) | .sh | Linux/macOS automation |
| VBScript | .vbs | Legacy Windows scripting (largely replaced by PowerShell — recognize it, don't write it) |
PowerShell deserves special attention because it's the most-tested:
- Built on cmdlets (pronounced "command-lets") in Verb-Noun format:
Get-Process,Stop-Service,Set-ExecutionPolicy. - Works with objects, not plain text — output can be filtered, sorted, and piped precisely.
- Execution policy controls whether scripts can run (a security feature —
Restrictedblocks scripts by default).
Basic Script Constructs
Every scripting language shares the same building blocks:
- Variables: named storage for values (
$name = "server01"in PowerShell). - Conditionals: if/then/else logic — "if the service is stopped, start it."
- Loops: repeat actions — "for each computer in this list, check disk space."
- Comments: notes for humans, ignored by the computer (
#in PowerShell/Python,REMor::in batch). Comment your scripts — future-you will be grateful. - Scheduling: scripts become powerful when run automatically — Task Scheduler on Windows, cron on Linux.
Scripting questions are usually recognition-level: match the language to its use. PowerShell = Windows administration with Verb-Noun cmdlets. Python = cross-platform general scripting. Batch = simple Windows command sequences. JavaScript = web. If a scenario needs Windows system administration automation, the answer is PowerShell — not batch, not Python.
Scenario: A technician needs to check free disk space on forty workstations every Monday morning. Doing it manually takes all day. The professional solution: write a PowerShell script using Get-PSDrive or WMI queries, loop through a list of computer names, output the results to a file — then schedule it with Task Scheduler to run automatically every Monday at 6 AM. Forty workstations checked before the technician's coffee cools. That's the power CompTIA wants you to appreciate: scripting turns repetitive labor into reliable automation.
---
End-of-Chapter Test
---
ANSWERS: