Which Change Management Factors Reduce System Failure Impact?

Explain concepts related to vulnerability response, handling, and management

An organization has establish a formal change management process after experiencing several critical system failures over the past year. Which of the following are key factors that the change management process will include in order to reduce the impact of system failures? (Choose two.)

Ensure users the document system recovery plan prior to deployment. Correct Answer
Perform a full system-level backup following the change.
Leverage an audit tool to identify changes that are being made.
Identify assets with dependence that could be impacted by the change. Correct Answer
Require diagrams to be completed for all critical systems.
Ensure that all assets are properly listed in the inventory management system.

Answer Correct answer: A, D — Before deployment, document a system recovery plan and identify dependent assets the change could impact to reduce the blast radius of a failed change.

Community Insight

The exam tests whether you can separate proactive change-risk controls, such as rollback plans and dependency mapping, from detective or documentation controls that only record what already happened.

A formal change management process reduces system-failure impact through pre-deployment rollback and recovery planning plus dependency impact analysis, making A and D the correct two factors.

Many learners pick C because change auditing sounds like change management, but an audit tool detects changes after the fact and does not provide a recovery path or dependency impact analysis.

Community Discussion (9 comments)

agfencer 👍 1 Selected: AD

How does C help when you're auditing for a change and it gets reported once the change has been made and it's borken. At that point you already know it's broken because users will report they cant use it. AD is better because A ensures users have a rollback plan ready which lowers downtime, documented rollback plan is ready and available and D is a no-brainer because you want to prioritize scope (impact assessment), before approving a change you must map out dependencies to know what will be affected.

Pochex 👍 1 Selected: CD

Audit tools help track and verify changes, making troubleshooting and accountability easier and understanding dependencies helps prevent unexpected service disruptions

kaka321 👍 1 Selected: AD

In really world for every CR a rollback plan is always in place which is A. Then D is also important

1574aa7 👍 3 Selected: A

I have pick A D , as whenever changes are being made, you would need a rollback plan , thats why ensure a document for system recovery is included , is necessary , in case the change ends up in failure, and , identify assets with dependency , to ensure any changes made , as per the question do not impact changes, or per say , in this option , to identify which would be impacted, and deal wit them accordingly

IT_guru_in_training 👍 2 Selected: CD

CD - Chat GPT

kmicic77 👍 1

A, D - Gemini 2.5 Pro and ChatGPT model o3 ;-)

An381038 👍 7 Selected: CD

C. Leverage an audit tool to identify changes that are being made. This ensures that any changes made to the system are tracked, helping to identify what went wrong if something fails. It improves accountability and allows the team to trace back issues caused by recent changes. D. Identify assets with dependence that could be impacted by the change. This ensures that any changes made to one system don’t negatively affect other systems or components. By understanding dependencies, the organization can better plan and minimize the risk of cascading failures.

ChopSNap 👍 2 Selected: AD

Ensure recovery options for a botched upgrade, and get multiple eyes on systems downstream that could be impacted. Source - facilitated Change Management at several organizations

Aziz132 👍 4 Selected: AD

A) Ensure a document for system recovery is included. (This is already done in my organization, it is part of any CRQ we submit.) Back up has to be available incase the change fails, glitches, or have unexpected impacts. D) Dependencies also has to be identified prior to performing the change. This needs to be completed so that system owners that might be impacted are informed, and they inform their users. We also do that. C is compliance item like tripwire. It is not related to Change Requests. I will vote A and D

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Expert Analysis

Why the Answer Is Correct

A formal change management process is designed to control risk before a change goes live, and option A supplies the rollback or recovery path that lets the team restore service when a deployment fails. Option D supplies the impact analysis step: identifying assets and downstream dependencies that the change could affect so owners are notified and the blast radius is understood. These two factors directly limit downtime and collateral damage, which is exactly what the question asks about reducing system failure impact. As ChopSNap put it, "Ensure recovery options for a botched upgrade" and get visibility into downstream systems. Both A and D are proactive, change-specific controls rather than generic documentation or after-the-fact monitoring.

Why the Other Options Are Wrong

B is backwards: a full system-level backup performed after the change cannot restore the pre-change state and may not even capture the right scope for rollback. C is a detective or audit control; An381038 notes it helps show that "any changes made to the system are tracked," but knowing a change happened after users report an outage does not reduce the failure's impact, which is why agfencer asks "How does C help when you're auditing for a change" once the change is already broken. E and F are useful hygiene: diagrams and accurate inventory support change planning, but they are not the two key factors that directly mitigate failure impact in this scenario. F in particular is too broad; D is the sharper requirement because it links a specific change to the dependent assets it can break.

Community Comment Notes

The commenters split mainly between A, D and C, D. Aziz132 and kaka321 both emphasize the rollback or recovery document, with Aziz132 noting that "it is part of any CRQ we submit" and kaka321 saying "for every CR a rollback plan is always in place." Pochex defends C by saying "Audit tools help track and verify changes" and also concedes that "understanding dependencies helps prevent unexpected service disruptions," which supports D but not C as a primary impact-reduction factor. An381038's argument for C is essentially post-incident traceability, while the question asks what reduces the impact of failures, so the AD reasoning from Aziz132, agfencer, and ChopSNap is the stronger fit.

Official Reference

https://csrc.nist.gov/pubs/sp/800/128/final

Exam Strategy

For "Choose two" change-management questions, first look for controls that act before or during the change, such as rollback and recovery documentation and dependency impact analysis, then eliminate options that are purely detective or generic documentation. Ask whether the option would actually shorten an outage or prevent downstream damage when the change fails.

Frequently Asked Questions

Why is an audit tool not one of the two key change management factors?

An audit tool is a detective control: it records or verifies changes after they occur, but it does not provide a rollback path or identify dependent assets that will be impacted.

Does a full backup after the change satisfy rollback planning?

No. A post-change backup captures the already-modified state; rollback needs a documented recovery plan and a restorable pre-change state.

More CS0-003 FAQ →

Related Analysis

← Back to CS0-003 Study Guide