Change Management for A+

This A+ topic covers technician-level change-management controls that reduce operational risk when making system or service changes. It focuses on prerequisite process controls (rollback, backup, sandbox, responsible staff), how to build and scope change requests, how to classify change types, how to evaluate timing/impact/risk, the role of approvals and peer review, and distinguishing implementation completion from end-user acceptance.

Start first lesson

6 lessons in this topic

Rollback, Backup, Sandbox, and Responsible Staff

Use prerequisite process controls that reduce risk before operational changes are made.

Change Requests, Purpose, and Scope

Build usable change requests with clear purpose and scope instead of vague operational guesses.

Standard, Normal, and Emergency Changes

Distinguish change types and apply the right handling posture to each one.

Timing, Affected Systems, and Risk Analysis

Evaluate timing, impact, and risk before implementing an operational change.

Approvals, Peer Review, and Governance Checks

Use approval and peer-review steps to reduce avoidable operational mistakes in the change process.

Implementation and End-User Acceptance

Carry changes through implementation and distinguish technical completion from true user acceptance.

Common mistakes to avoid

Technicians often treat a verbal backup as sufficient. The exam expects documented, verifiable controls. Also, "sandbox" is not an excuse to skip rollback planning; sandbox reduces but does not eliminate production risk.

Do not conflate 'scope' with 'detailed work steps'. Scope defines boundaries, not the implementation checklist. Ticket style is outside this lesson focus, but required fields are in-scope.

Learners mix 'normal' with 'low risk'. Emphasize that 'normal' means 'follows the normal approval path', not a risk rating.

Learners often underestimate indirect impacts (shared storage, authentication services). Teach to check dependencies beyond the immediate target.