Study CompTIA 220-1202 Documentation, Change, and Backup: key concepts, common traps, and exam decision cues.
Operational-procedures questions on Core 2 are where technically capable readers still lose points. The exam wants the answer that documents clearly, protects data, respects process, communicates professionally, and keeps changes reversible.
Rollback plan: The defined path for returning a system to its earlier state if a change causes problems.
Chain of custody: The documented handling record that protects evidence integrity during an incident-related investigation.
The exam usually wants you to:
| If the prompt is really about… | Strongest first reading |
|---|---|
| what belongs in a ticket | user, device, issue description, category, severity, progress notes, and final resolution |
| recurring support work | SOP, knowledge base, or repeatable documentation path |
| ownership and inventory | asset tags, assigned users, warranty, procurement, or CMDB details |
| incident evidence | incident report, documentation integrity, and possibly chain of custody |
flowchart LR
A["Request and scope the change"] --> B["Assess risk and impact"]
B --> C["Prepare backup and rollback plan"]
C --> D["Test in sandbox or peer review if appropriate"]
D --> E["Implement in approved window"]
E --> F["Verify and document outcome"]
CompTIA likes answer choices that sound fast but skip:
| Prompt cue | Strongest first reading |
|---|---|
| fastest full restore point exists | full backup or tested restore path matters more than theoretical efficiency |
| need smaller daily backup windows | incremental or differential trade-offs |
| business continuity and loss tolerance | onsite vs offsite, 3-2-1 logic, and tested restores |
| user requests recovery somewhere else | alternative-location recovery, not in-place overwrite |
| Situation | Strong answer usually does |
|---|---|
| frustrated user | listen actively, clarify, avoid arguing, and restate the issue |
| technical explanation needed | avoid jargon when plain language works better |
| delayed arrival or slow fix | set expectations early and communicate status |
| confidential material visible on desk, printer, or desktop | handle it as private data, not as casual office clutter |
| Topic | Better reading |
|---|---|
| script for repeated admin work | useful, but test first, log actions, and avoid broad unintended changes |
| remote-access tool choice | weigh security and fit: RDP, VPN, VNC, SSH, WinRM, RMM, or approved third-party tooling |
| public vs private AI or automation use | policy, privacy, accuracy, and data-source risk still matter |
| Trap | Better reading |
|---|---|
| treating documentation as optional after a successful fix | documentation is part of the successful fix |
| changing production without sandbox or rollback thinking | Core 2 rewards controlled change discipline |
| discussing user data casually during support | privacy handling is part of professionalism |
| writing a quick script and pushing it everywhere | test, scope, and log it first |
A technician has a script that fixes a recurring mapped-drive problem on one workstation. Management wants it run across many devices immediately. Which answer best matches Core 2 operational logic?
Correct answer: B. Core 2 treats scripting as useful but still governed by testing, documentation, scope control, and change discipline.