4.2 - CompTIA A+ Core 2

Rollback plan

A document that outlines how to revert system changes in case of failure or error.

Backup plan

A plan to accomplish an objective in case of a problem encountered during a procedure.

Sandbox testing

Testing software in an isolated environment, with no connection to the real world or real production systems.

Responsible staff members

Valuable team members who assist in the change management process.

Change management

A formal process for managing change that avoids downtime, confusion, and mistakes.

Change management request form

A document that requests permission to make a change, including change purpose, scope, and type.

Purpose (changes)

Determines the reasoning behind the change - why is it being done?

Scope (changes)

Determines a change’s effects; may be limited to a single server or an entire site.

Standard change

A low-risk, pre-approved change that is well documented (e.g., replacing a monitor for a user).

Normal change

A medium-risk change that follows the full change management process (e.g., replacing a switch or updating a DBMS system).

Emergency change

A high-risk change that must be implemented immediately (e.g., patching a zero-day vulnerability).

Change freeze

Scheduled periods where no changes can occur.

Maintenance windows

Scheduled downtime periods to implement changes.

Risk analysis

Quantitative/qualitative determination of a risk regarding making a change.

Risk levels

Values/labels that determine the potential impact of a risk (e.g., low, medium, high).

Change board

A formal advisory group that reviews, accepts, or rejects proposed changes.

Implementation/peer review

The process of assessing proposed changes with team members to ensure quality before full deployment.

End-user acceptance

Gathering feedback from end-users to confirm changes meet their needs and expectations.