CompTIA 220-1202 procedures guide covering documentation, change control, privacy, licensing, and support workflow decisions.
Operational-procedure questions are where otherwise technical candidates give away points. Core 2 still expects the answer that documents, communicates, protects data, respects process, and reduces follow-on risk.
| The prompt is usually checking whether you can… | Without making this common miss |
|---|---|
| treat documentation as part of the fix | acting like the technical change alone is the whole answer |
| apply change discipline | making production changes with no approval, no backout path, or no communication |
| recognize safe scripting behavior | automating carelessly with broad privileges and no testing |
| protect privacy and disposal boundaries | ignoring data handling, secure erase, or need-to-know behavior |
| Topic | What strong answers usually do |
|---|---|
| documentation | record root cause, action taken, verification, and next-step prevention |
| communication | use clear user-facing language, expectations, and status updates |
| change management | include request, risk check, approval, maintenance window, and backout plan |
| safety and environment | protect the technician, the device, and the data during repair work |
| backup and recovery operations | know when backup, restore, reset, and secure disposal each fit |
| scripting | test first, log output, parameterize, and use the least required privilege |
Start with 4.1 Docs, Change & Backup. It covers the operational habits that separate disciplined support from risky improvisation.
Then continue with 4.2 Safety, Privacy & Scripting for the policy, evidence, safety, and automation boundaries that still carry real exam weight.
Then use 4.3 Disposal, Licensing & Incidents for the questions where environment, recycling, policy, or evidence discipline drives the right answer.
Finally use 4.4 Remote Support & AI for the modern support-work behaviors that still carry direct exam weight.
| If the question says… | Strongest first reading |
|---|---|
| change must happen during business hours with risk to users | change control, communication, and rollback plan |
| repeated manual task on many machines | safe scripting or approved automation path |
| device is being reassigned, retired, or disposed | secure erase, privacy, chain of custody, and e-waste handling |
| user is frustrated or non-technical | communication and expectation-setting are part of the correct answer |
| issue is fixed but audit or root cause still matters | documentation closes the loop |
| Trap | Better reading |
|---|---|
| treating ticket notes as optional | they are part of professional support practice |
| running a script everywhere because it worked once | test, log, and scope it first |
| focusing only on technical completion | verify outcome, communicate clearly, and capture what changed |
| forgetting privacy and disposal rules | retired hardware and exported data still need controlled handling |