Make support changes recoverable

A+ Core 2: Operational Procedures
Original starter lesson / sources checked 2026-09-30

Obtain authorization and define scope before changing a user system. Protect private data and collect only what the ticket needs.

Record the current configuration, expected impact, and recovery steps before a risky change. Follow the organization's change process.

Backups and restore verification are separate tasks. Keep recovery tests separate from the original production data.

Hands-on lab

Draft a change note for a driver update: scope, evidence, expected impact, recovery, and verification.
Use invented user data; do not copy credentials into a support ticket.

Put the lesson to work

Original exam-style practice. Choose the best answer for the stated scenario.

1. Before a potentially disruptive configuration change, which action best reduces recovery risk?

Record the current state and a tested recovery procedureAssume every change is reversiblePost user credentials in the ticketDelete existing backups

2. A backup job succeeded. What is the strongest evidence it supports recovery?

The filename is longIt uses a familiar extensionThe job ran at midnightA separate test restore passes representative data and application checks

Go deeper

Official CompTIA scope and exam information WWADD Move: Prove a backup can restore

Independent practice aligned to selected topics. No endorsement, actual exam items, or pass guarantee. Verify your exam version and use the full official objectives for complete preparation.