FirstTry

Objective 4.2

220-1202

Given a scenario, apply change management procedures.

Objective 4.2 sits in Operational Procedures, which carries 21% of the A+ Core 2 exam. The questions below are original, written from the official objective title above, and each explanation cites the CompTIA page it rests on.

Objective title verbatim from the official objectives. CompTIA exam page ↗

A worked example

Shown solved, with the whole explanation open: this is what every question here carries.

4-2Operational Procedures

A DevOps administrator configures a branch policy that blocks any merge into the main branch until a minimum number of designated reviewers approve the pull request. Which change management concept does this policy implement?

A request form documenting the purpose and scope of the changeA request form captures details of the change, it does not itself block the merge.
A rollback plan that reverts the branch if the merge failsA rollback plan addresses recovery after a change fails, not gaining permission to proceed.
Formal approval from a change board before the change is mergedCorrect · your answerCorrect: gating implementation on reviewer approval is the mechanism of change board approval.
Sandbox testing of the branch changes in an isolated environmentSandbox testing verifies the change works in isolation, it does not gate approval to merge.
A documented business process describing how merges normally occurA documented business process describes the general procedure, but the specific reviewer gate is the approval step itself.

Correct.

Checked against learn.microsoft.com, July 2026

Concept

Change management requires that proposed changes receive sign off from designated approvers before they are implemented.

Why C

Blocking a merge until required reviewers approve the pull request is the technical equivalent of requiring a change board to approve a change before it goes live.

Source

Use branch policies to protect important branches by requiring pull requests, reviewers, builds, and other checks before changes merge.... 5 Minimum number of reviewers True True…

Microsoft Learn: Branch policies and change control, checked July 2026
#change management#change board approvals#branch policies

Now you: objective 4.2 questions

No account needed. The explanation opens when you answer.

Sample question 1 of 3

4-2Operational ProceduresChoose 2

A team requires every change to the main branch to go through a pull request that can't be bypassed, and keeps a saved prior configuration so a failed deployment can be automatically reverted. Which two change management concepts does this scenario combine?

Sample question 2 of 3

4-2Operational Procedures

You are recruiting a pilot group for a Windows feature update. Twenty volunteers all run the same standard laptop image and the same two applications. What is wrong with that group?

Sample question 3 of 3

4-2Operational Procedures

Your team is about to send a feature update to the targeted feedback groups. The change record lists the rings, the schedule and the feedback channel. What is still missing?

Full A+ Core 2 question bank coming

We’re writing the complete bank from the official objectives right now. Leave your email and we’ll tell you when it ships, nothing else, ever.

Read the sources

These are the official pages the questions above cite. Reading them is studying the objective from the primary source, which is what the explanations point you toward anyway.

More objectives in Operational Procedures