8 Core 2: Operational Procedures and Practice
Learn how to document support work, communicate with users, control changes, protect and recover data, and follow safe, secure operational procedures.
Operational practice across A+
On the current CompTIA A+ V15 exams, operational procedures are part of Core 2, while Core 1 tests complementary hardware, networking, mobile-device, and troubleshooting knowledge. The exams are separate, so preparation must address both.
Operational work combines accurate records, clear communication, controlled changes, tested recovery, safe handling, and policy compliance. Before acting, assess impact and risk; during work, follow approved procedures and communicate; afterward, verify results and document them.
Documentation and asset records
A useful lets another technician understand what happened, what was tried, and what remains to be done. Record relevant user and device details, issue description, category, severity, progress notes, escalation, and resolution. Keep notes factual, concise, and professional; avoid guesses, blame, and unnecessary personal information.
For example: “User reports no network access in Office 214 beginning at 09:10. Confirmed link light; ipconfig showed an . Renewed DHCP lease; workstation received 10.20.4.38 and accessed the intranet. User confirmed service restored at 09:32.” This conveys more useful information than “Network fixed.” Never record a user’s password in a ticket.
Other operational records serve different purposes:
Incident reports document what occurred, the impact, timeline, response, and outcome.
Standard operating procedures (SOPs) provide approved, repeatable instructions, such as a custom software-installation procedure.
Knowledge-base articles provide reusable troubleshooting or how-to information for staff or users.
Onboarding and offboarding checklists cover account, device, access, and asset steps when a user joins or leaves.
Service-level agreements (SLAs) set agreed service targets and responsibilities, internally or with an external provider.
Asset management tracks equipment through its life cycle. Inventory lists and a can connect asset tags or IDs with device details, assigned users, warranty, licensing, procurement, and configuration. Keep records current when a device is reassigned, repaired, upgraded, or retired.
Professional communication
Listen without interrupting, confirm the user’s description, and explain next steps in language appropriate to the audience. Remain calm and respectful, set realistic expectations, protect confidential information, and do not promise an outcome or timeframe you cannot control.
A useful status update states what is known, what is being done, and when the next update is expected. For example: “The laptop connects to Wi-Fi, but the company VPN is rejecting sign-in. I’m checking the account and VPN logs with the network team. I’ll update you by 2 p.m.”
If escalation is needed, explain why and preserve the ticket history so the user does not have to repeat everything.
Change management
Changes can interrupt services or cause data loss. Use the organization’s documented process before changing production systems. A change request should describe its purpose, scope, affected systems and users, risk level, schedule, responsible staff, implementation steps, testing, backup, rollback plan, approvals, and acceptance criteria.
Common change types are:
: low-risk, repeatable, and preapproved under an established procedure.
: assessed and approved through the usual change process.
: needed urgently to address a serious incident or risk; follow the emergency approval and documentation process, then complete the required review.
Before implementation, consider dependencies and impact, obtain required change-board approval, test in a sandbox where practical, and arrange peer review. Schedule work within an approved maintenance window and avoid a change freeze unless an authorized exception applies. After implementation, verify service and user acceptance, document results, and use the rollback plan if success criteria are not met.
For a shared printer driver update, identify affected workstations, test the driver on a representative device, save the current configuration, notify users, schedule the rollout, define a restoration step, and verify printing after deployment.
Backup and recovery
Choose a backup method according to recovery needs, storage, and the time available for backup and restoration.
A full backup copies all selected data. It is simple to restore, but takes more time and storage.
An copies changes since the most recent backup of any type. Restoration generally requires the full backup and each required subsequent incremental set.
A copies changes since the most recent full backup. Restoration requires the full backup and the latest differential.
A synthetic full backup is assembled from an existing full backup and later backup data. It can provide a full restore point without rereading all source data.
A 3-2-1 approach keeps at least three copies of important data, on two types of media, with one copy offsite. Onsite backups can support quick recovery; offsite or otherwise isolated copies can help when local equipment is damaged or compromised. A retains backup sets at different intervals, such as daily, weekly, and monthly.
Test backups regularly by confirming that required data can actually be restored; a successful backup-job report alone does not prove recovery works. Set backup frequency according to how much recent work the organization can afford to lose. Recovery can restore data in place, overwriting the original location, or to an alternative location for verification or selective recovery. Check the target carefully to avoid overwriting newer data.
Safety and environmental procedures
Protect yourself and equipment before servicing a device. Disconnect power before working inside a PC and follow device-specific procedures. Remove jewelry and use appropriate lifting techniques.
Reduce electrostatic-discharge (ESD) risk with an ESD strap or mat, antistatic bags, and proper component handling and storage. Keep cables organized to reduce trip hazards and avoid obstructing ventilation. Respect equipment weight limits and use safe lifting practices.
Use safety goggles or an air-filter mask when the task requires them. Follow electrical and fire-safety procedures, including proper grounding and using suitable fire-response equipment. Follow applicable workplace and government rules for handling and disposing of batteries, toner, displays, and other regulated or hazardous materials. Consult product safety documentation and local procedures; do not put restricted waste in ordinary trash.
Security and authorized operations
Follow acceptable-use, security, privacy, licensing, and regulatory policies. Handle user data only as authorized, and use approved procedures for remote support. Before connecting remotely, verify the user and obtain consent; explain actions and end the session when work is complete.
Use scripts only when authorized, reviewed, and understood, especially if they modify files, settings, accounts, or systems. Treat AI-generated output as unverified: check its accuracy, security, and privacy implications, and confirm that relying on or sharing it complies with organizational policy.
For an unexpected attachment asking the user to enable macros, advise them to follow organizational reporting procedures and not enable macros unless the file is verified and authorized.
Applying procedures to technical problems
Operational judgment supports technical troubleshooting but does not replace it. A Windows workstation with a 169.254.x.x may not have obtained a DHCP lease; investigate network connectivity or lease acquisition before making destructive changes.
For a slow Windows PC, Task Manager is the built-in tool most directly useful for examining current CPU, memory, disk, and process activity. When a backup job reports success but no restore has been tested, the gap is that the organization has not verified that recovery works.
For a software rollout, reduce risk by testing in a sandbox, documenting scope and rollback, and obtaining required approval. For hardware service such as replacing a desktop motherboard, disconnect power and use appropriate ESD precautions. These examples bring operational procedures together with Core 1 hardware and networking and Core 2 operating-system, security, and troubleshooting skills.