Change management for SY0-701

Exam objectiveExplain the importance of change management processes and the impact to security

The short answer

What objective 1.3 asks you to know

Objective 1.3 covers change management as a security control: unplanned or unreviewed changes cause outages and open vulnerabilities, so organizations route changes through a defined process.

Business processes. A change has an owner, goes through an approval process, and involves the stakeholders it affects. An impact analysis predicts its effects, including security implications, before approval, and test results show how it actually behaves in a non-production copy. A backout plan gives the steps and criteria for reversing it, a maintenance window schedules it to limit disruption, and standard operating procedures describe the routine steps. A standard change is low risk and approved in advance. An emergency change bypasses normal timing with a smaller approval group, but it is still reviewed afterward.

Technical implications. Every change has side effects, and restricted activities keep the work inside the approved scope: approval for one change is not permission to make others. Allow lists and deny lists can block needed traffic, and a change can cause downtime, require a service or application restart, or break a dependency. Legacy applications add risk because they are often poorly documented and fragile to change, and unsupported ones no longer get vendor patches.

Documentation and version control. After a change, diagrams, policies, and procedures must be updated to match reality. Version control keeps a line-by-line history of who changed what, when, and why, so a team can compare, review, and roll back to a known-good version.

Exam scenarios describe a failed or risky change and ask which step was skipped, or which document or plan would have helped.

Written by Knotch · reviewed Nov 15, 2026 · 3 study articles behind this page

Practice the rest

This page is the map. Knotch is where you drill it until it sticks.

  • 3step-by-step lessons with predict-and-reveal and look-alike duels
  • 44exam-style questions with a rationale for every wrong answer
  • 1review queue that brings back what you missed
Start practicing freeFree to start. No card needed.
Tell them apart

Pairs people mix up

  • Standard change vs. Emergency change

    A standard change follows a procedure approved ahead of time, so it needs no new review. An emergency change skips the normal wait with a smaller approval group, but it is still recorded and reviewed afterward.

  • Policy vs. Procedure

    A policy says what must happen and why, and changes rarely. A procedure lists the steps for carrying it out, and changes whenever the tools or the work change.

  • Allow list vs. Deny list

    An allow list permits only what is named and blocks the rest. A deny list blocks only what is named and permits the rest, so it misses anything new.

  • Impact analysis vs. Test results

    Impact analysis assesses how a change could affect systems, users and security. Test results show actual behavior in a non-production copy and can feed that analysis.

The full set of look-alike pairs for this objective is inside Knotch.

Know these cold

Key terms

Backout plan
Steps and criteria for reversing a change, written and tested before starting, so a failed change can be undone within the window.
Impact analysis
A review of what depends on a system and what could go wrong with a change, including security implications, that predicts effects before approval.
Maintenance window
An agreed low-impact period in which an approved change is scheduled, to limit disruption to the business.
Emergency change
A change that cannot wait, such as a fix for a flaw under active exploitation, which takes an expedited path with a smaller approval group and after-the-fact review.
Version control
A line-by-line history of files that records who changed what, when, and why, so changes can be compared, reviewed, and rolled back.
Try one

Sample question

Question 1.3-002 · medium

A security patch for an order-processing service requires a 15-minute restart. The service is critical during business hours.

Which approach best fits change-management practice?

  1. A. Apply it immediately because security patches bypass change control
  2. B. Schedule it in an approved maintenance window with rollback ready
  3. C. Apply it at peak hours so more staff are available to monitor
  4. D. Skip internal testing because the vendor already tested the patch
Show the answer and why
Answer: B, Schedule it in an approved maintenance window with rollback ready

This limits business disruption while preserving approval and recovery steps.

Maintenance windows, communication, and tested rollback are central to controlling the business impact of technical changes.

Why not A: Patching urgency does not remove the need for approval, scheduling, and a backout plan; true emergencies use an expedited process.

Why not C: Maximizing disruption to the business is the opposite of the goal.

Why not D: Vendors test generically; the organization must verify against its own environment.

Quick answers

Common questions on this objective

What is a backout plan in change management?

A backout plan is the written, tested procedure for reversing a change if it fails. Backups are one input it may use, but the plan itself is the procedure.

What is the difference between a standard change and an emergency change?

A standard change is low risk and approved in advance. An emergency change cannot wait, so it uses an expedited path with a smaller approval group and is reviewed after the fact.

Why does change management matter for security?

Unplanned or unreviewed changes cause outages and open vulnerabilities. Routing changes through approval, testing, scheduling, and a backout plan keeps them reversible and reviewed.

Know it. Now spot it in a scenario.

Start practicing free