CompTIA A+ Core 2 · 220-1202
Objective 4.2: Change management procedures
Try it now: 8 quick questions on this objective, no account needed.
Objective 4.2 · Change management
1 / 8Which document formally requests permission to make a specific change to an IT system and includes the scope, risk assessment, and implementation plan?
Practice questions for A+ Core 2 objective 4.2, “Change management procedures.” Every question is original, written to the 220-1202 exam objectives, and comes with a full explanation — answer them below to see instant grading.
This objective sits in Domain 4.0: Operational Procedures, which is about 21% of the exam — so mastering it moves your readiness score meaningfully.
More 4.2 practice questions
Objective 4.2 · practice questions
1 / 5A team plans to migrate the company's file server to a new storage system. The change isn't routine and carries moderate risk. How should it be handled?
All 5 questions, with answers
1.A team plans to migrate the company's file server to a new storage system. The change isn't routine and carries moderate risk. How should it be handled?
- A.As a standard change, because file servers count as standard equipment
- B.As an emergency change, so that the migration can start immediately
- C.As a normal change, with a request, risk analysis, rollback plan and board approval
- D.With no change request at all, because it's only an infrastructure upgrade, not an app change
Answer: C. As a normal change, with a request, risk analysis, rollback plan and board approval. A normal change is any change that is neither pre-approved nor urgent, and it goes through the full process: request form, risk analysis, rollback plan, change board approval and scheduling. Standard changes are pre-approved routine tasks, emergency changes are for urgent fixes only, and infrastructure work still needs change management.
2.A critical vulnerability in the company's VPN appliances is being actively exploited, and the vendor has released a patch. Which type of change should be used to apply it?
- A.Standard change
- B.Emergency change
- C.Normal change, scheduled for next quarter
- D.No change request, because security patches are exempt
Answer: B. Emergency change. An emergency change handles an urgent risk or outage that can't wait for the normal schedule: it gets fast-tracked approval, often from a smaller emergency change board, and is fully documented afterward. A standard change is only for pre-approved routine work, waiting a quarter leaves the exploit open, and security patches still go through change management.
3.Adding a user to an existing security group follows a documented, low-risk procedure that was approved in advance. Which type of change is this?
- A.Normal change
- B.Emergency change
- C.Change freeze
- D.Standard change
Answer: D. Standard change. A standard change is routine, low-risk and pre-approved, so it follows its documented procedure without going to the change board each time. A normal change needs assessment and approval before it's scheduled, an emergency change is an urgent fix with fast-tracked approval, and a change freeze is a period when changes aren't allowed.
4.A change management process requires that before any significant system change is approved, a specific group reviews and authorises it. What is this group called?
- A.Help desk team
- B.Change advisory board (CAB)
- C.Security operations centre
- D.Asset management committee
Answer: B. Change advisory board (CAB). A Change Advisory Board (CAB) is a cross-functional group responsible for evaluating, approving, or rejecting proposed changes to IT systems. The CAB assesses the risk, impact, and benefit of changes before authorisation. This formal review process reduces the likelihood of unplanned outages or disruptions.
5.Before deploying a new software update to all workstations, the IT team tests it in an isolated environment that mirrors production. What is this environment called?
- A.Production server
- B.Sandbox
- C.Backup server
- D.Domain controller
Answer: B. Sandbox. A sandbox is an isolated test environment that replicates production conditions but prevents any changes from affecting live systems. Testing in a sandbox allows the team to identify issues such as compatibility problems or performance impacts before wider deployment. This practice is a fundamental change management control.
Learn 4.2 and every other objective
Your A+ Core 2 path walks the whole exam in short stops, one objective at a time, and maps where you stand as you go.
Start my A+ Core 2 pathNo account needed to start.