Documentation & Change Management

Why This Objective Carries Weight

Domain 4, Operational Procedures, is the single largest objective on the CompTIA A+ Core 2 (220-1202) exam at 25% of scored content. The current V15 series (Core 1 220-1201 and Core 2 220-1202) launched March 25, 2025; each exam delivers a maximum of 90 questions in 90 minutes, and Core 2 passes at 700 on a 900-point scale. Objectives 4.1 (documentation/change management) and 4.2 (asset management) are heavily process-based, so questions reward you for knowing the order and purpose of steps, not for memorizing a product name.

Documentation Types CompTIA Names

CompTIA lists specific documents by name in objective 4.1. Learn the document and what it answers.

Trap: A topology diagram shows the network; an asset inventory lists the devices. The exam pairs each scenario with exactly one correct artifact.

The Change-Management Flow (Memorize the Order)

Objective 4.2 spells out change management as a documented business process. The defensible exam order is:

1. Document the business process the change affects.
2. Submit a change request (request form) describing purpose and scope of the change.
3. Risk analysis — assign a risk level (low/medium/high).
4. Change board approval — leadership/CAB approves, denies, or defers.
5. Plan the change with date and time and affected systems/impact.
6. Schedule a maintenance window to minimize user disruption.
7. Get end-user acceptance and notify stakeholders.
8. Implement, test, and document the result.

Backout (Rollback) Plan

Every approved change must include a backout plan — the predefined steps to return the system to its prior working state if the change fails. CompTIA treats "What do you create before implementing?" as a rollback question almost every time. Changes are validated in a sandbox/test environment first, never directly in production.

Ticketing Systems and Asset Management

A ticketing system records the problem description, progress notes, and problem resolution; closed tickets become knowledge base entries. Asset management tracks hardware/software via an inventory list, asset tags/IDs, assigned users, warranty and license status, and a procurement life cycle (procure → deploy → maintain → retire/decommission with secure data destruction).

• Database/asset tags — barcodes or RFID tied to a central record.
• Warranty tracking — avoids paying for repairs still under coverage.
• Licensing — keeps the org compliant and audit-ready.

Worked example: A help-desk tech resolves a recurring printer spooler crash. Correct A+ behavior: update the ticket with detailed progress notes and the resolution, then publish a KB article so the next technician resolves it in minutes — turning one fix into reusable documentation.

How Domain 4.1 and 4.2 Are Tested

The exam rarely asks for a raw definition. Instead it gives a short workplace scenario and asks which document, which step, or which artifact is correct. Read each stem for the outcome the scenario wants. If the scenario wants consistency for a repeated task, the answer is a standard operating procedure. If it wants a way to look up a known fix quickly, the answer is a knowledge base article. If it asks what to capture after a security event, the answer is an incident report. If it asks how the network is wired, the answer is a topology diagram.

Training yourself to translate the scenario into the single artifact CompTIA expects is the highest-value skill for this objective.

Change-management questions almost always probe one of three things: the existence of an approval body before work begins, the requirement to document scope and risk, and the presence of a backout plan before production. A common distractor is an answer that implements the change immediately because it is urgent. Even an emergency change still requires a documented request and a post-implementation review under CompTIA's model, so "just make the change" is never the best answer.

Another frequent distractor skips the maintenance window and applies the change during business hours; the correct response schedules the work for a low-impact window and notifies affected users first.

Asset Management in Practice

For asset management, expect questions that test the difference between simply owning hardware and tracking it through its full life cycle. A device that is purchased but never tagged or entered into the inventory database is effectively invisible to the organization, which creates security, warranty, and licensing gaps. The procurement life cycle moves an asset from acquisition, through deployment to an assigned user, into a maintenance phase, and finally to retirement and decommissioning, where data destruction and certified disposal close the loop.

CompTIA expects you to connect each phase to the record-keeping that supports it: a purchase order at acquisition, an asset tag and assigned user at deployment, warranty and license data during maintenance, and a documented wipe-and-recycle action at retirement. Knowing that the asset database, not a spreadsheet on one technician's laptop, is the authoritative source of truth is the recurring theme.