Study CompTIA 220-1202 Safety, Privacy, and Scripting: key concepts, common traps, and exam decision cues.
Operational procedures on Core 2 also cover the edges that technicians often treat as “not really technical”: safety, privacy, evidence handling, remote access, scripting risk, and acceptable use. CompTIA still scores those boundaries like core support skills.
Order of volatility: The principle of collecting the most fragile evidence first when incident handling matters.
AUP: Acceptable use policy, the rules that define what users and staff may do with systems, data, and network resources.
The exam usually wants you to:
| Scenario cue | Strongest first reading |
|---|---|
| internal hardware work | power disconnect, ESD protection, correct component handling |
| dusty or poorly ventilated environment | cleanup, placement, airflow, and temperature or humidity awareness |
| power instability | UPS or surge protection decision, not just “replace the PC” |
| toner, battery, or disposal concern | read the material-safety and disposal boundary first |
| If the prompt mentions… | Better first reading |
|---|---|
| copied drive, evidence, or law enforcement | incident handling, chain of custody, and evidence integrity |
| credit card, healthcare, PII, or government ID data | regulated data boundary and retention or privacy obligations |
| user agreement or software rights | licensing, DRM, EULA, or NDA boundary |
| acceptable or prohibited activity | policy, not just technical capability |
| Need | Strongest first lane |
|---|---|
| graphical Windows administration | RDP or approved remote-support tooling |
| secure command-line administration | SSH or WinRM depending on platform and environment |
| full remote support workflow at scale | RMM or approved third-party remote tool |
| remote access over untrusted networks | VPN-aware path and stronger security posture |
| Topic | Strong answer usually does |
|---|---|
| repeated routine task | use a script if it reduces error and is tested, scoped, and logged |
| script file choice | recognize the common support script types without treating file extension memorization as the goal |
| script risk | avoid unintended settings changes, malware introduction, and crashes from careless use |
| AI assistance | respect policy, privacy, accuracy limits, hallucination risk, and plagiarism or misuse boundaries |
| Trap | Better reading |
|---|---|
| remote into anything with any tool because it works | the security model of the remote method still matters |
| run a script without testing because the task is repetitive | repetition is exactly why scope and validation matter |
| treat sensitive printed or onscreen information as routine clutter | user privacy and regulated-data handling are part of the job |
| ignore power, dust, or ventilation clues | environment can be the real operational problem |
A technician needs to help a remote user on a public network and also wants to run a script that remaps drives. Which answer best fits Core 2 operational logic?
Correct answer: B. Core 2 expects security-aware remote access and controlled scripting, even for routine support work.