Chapters0/35 ▾
Chapter 7 · Lesson 1 of 5
Change types and change freezes
1 min read
Objective 4.2 adds three change types to the change request process. The type decides how much review a change needs, so the exam describes a change and asks how it should be handled. Pre-approved never means undocumented: every type is still recorded in the ticket.
| Type | Risk and review | Example |
|---|---|---|
| Standard | Low risk, routine, well documented, pre-approved | Swapping a failed keyboard for the same model |
| Normal | Medium risk, full process with change board approval | A new firewall rule |
| Emergency | Urgent fix, still reviewed but on an expedited track | Patching a zero-day vulnerability |
A change freeze is a set period, such as a retailer's busiest season, when no changes are allowed except emergency changes. A maintenance window is the opposite idea: a scheduled time set aside for approved work.
For example, if a team got board approval last month for a database upgrade and a freeze starts this week, the upgrade waits until the freeze ends. A security patch for a flaw being exploited right now can still go ahead, because it is an emergency change.
Check yourself
1. A retailer has declared a change freeze for its busiest season. Which of the following changes may still proceed during the freeze?
2. A technician must replace a failed monitor on one user's desk. Company policy describes this as a routine, well-documented, low-risk change. How should the change be handled?
Facts checked 2026-11-16 · Sources: CompTIA A+ Core 2 (220-1202) V15 Exam Objectives
CompTIA A+ cheat sheet: every key fact on one page →