Explain the importance of change management processes and the impact to security

Objective 1.3 sits in General Security Concepts, which carries 12% of the Security+ 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.

1-3General Security ConceptsModerate

After a patch cycle completes, a change manager reviews the update platform's compliance dashboard to record which servers received the update and retains the report for a future audit. Which change management activity is this?

Approving the change through a change advisory board voteThe board's vote gates the work. Reading a compliance report afterward is a separate obligation.

Maintaining documentation of the change outcome for auditsCorrect · your answerCorrect: this is documentation of the change outcome kept for audit evidence.

Enforcing version control across configuration scriptsRight answer for tracking revisions to the deployment scripts themselves.

Preparing a backout plan in case the patches later failA backout plan is written in advance so a failed change can be reversed. It is a contingency, not a record of what happened.

Establishing a maintenance window before deployment beginsFixes when the work may happen. That decision is made and closed before the patches install.

Correct.

Checked against learn.microsoft.com, July 2026

Concept

Change management activities are ordered in time, and the question is usually which point in that order the described action sits at. Approval, scheduling and a reversal plan all belong before anything is executed. Once the work is done, one activity remains: capturing what actually happened, in a form that survives the people who did it. That record is what an assessor asks for months later, and it is worthless if assembled retrospectively.

Why B

Retaining compliance reports that show which systems were patched, for future audit purposes, is exactly the documentation function of change management.

Source

Custom reports and alerts: Build custom dashboards to report update status, and configure alerts to notify you of update statuses and any problems that arise.... Reports and alerts: Build custom reporting dashboards through Azure Workbooks to monitor the update compliance of your infrastructure.

Microsoft Learn: Azure Update Manager overview, checked July 2026

#change management#documentation#patch management

Now you: objective 1.3 questions

No account needed. The explanation opens when you answer.

Sample question 1 of 3

1-3General Security ConceptsEasy

Which group is responsible for reviewing and formally authorizing proposed changes before they are implemented?

Sample question 2 of 3

1-3General Security ConceptsEasy

Which element of a change request describes how to return a system to its prior state if the change fails?

Sample question 3 of 3

1-3General Security ConceptsModerate

An administrator schedules a database upgrade for 2 a.m. Sunday because it requires restarting the service while no users are connected. What is this planned period called?

That’s 3 of the full Security+ bank.

Keep going free: 10 questions per certification in bank practice, with no account.

Continue practicing

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.

A worked example

Now you: objective 1.3 questions

Read the sources

More objectives in General Security Concepts