1.3 Flashcards
Change management Technical change management
The importance of change approval process
Standardizes necessary information so the committee can make a decision
Determines scope, purpose, schedule, affected systems, impact, and risks associated with the change
What role does the owner of the application/data have in change management?
The owner is kept informed as the change happens and verifies that the finished product is acceptable
Why is it important to determine stakeholders in the change management process?
It might not be as obvious as you might think
Any change could have enterprise-wide changes that can even bring down the entire business
Why is an impact analysis important during change management?
Both doing the change and not doing the change have risks
Your fix might not fix anything
The fix might break something else
OS failures and data corruption might happen
The lack of a change can cause security vulnerabilities or application unavailability
An environment with no connection to the real world or production system. Used to test network changes and backout plans.
Sandbox
Why is using a sandbox important in change management?
Allows the devs to work out any kinks in the change. Also allows devs to test the finished product as well as the backout plan.
Why is having a backout plan important in change management?
If the change does not work as intended, the devs can roll back the network to a known-good state.
Nothing will ever work perfectly all the time.
Some changes are difficult to revert, so be sure you have a full and complete backup of the system in case the backout plan fails.
Why is considering maintenance windows important during change management?
It is important to know when a change will least impact a business. For example, during the night or during holidays.
Downtime can affect production.
SOP stands for
Standard operating procedure
Why are SOPs important during change management?
SOPs help to standardize change control processes
Helps the company be efficient and well-informed
What is the difference between change management and technical change management?
Change management is concerned with “what” needs to change
Technical change management is concerned with “how” to change it
Lists used to allow or prevent certain applications from working in your environment
Allow lists / deny lists
A list of applications that can run in an environment; everything else is blocked
This method is very restrictive
Allow list
A list of applications that are blocked from running in an environment; everything else is allowed
This method is very lenient
Deny list
What is the importance of restricted activities during change management?
This prevents the people doing the changes from widening the scope of the process
Unauthorized scope changes can cause many issues
It could cause serious networking problems that are difficult to solve, or communication issues due to confusion
Why is downtime important to consider in change management?
It is disruptive and can affect the company’s bottom line.
People need time to prepare. Send out emails/calendars to warn them.
A method commonly used to prevent downtime during network changes
Switch to a temporary secondary system, update the primary system, and then switch back to the updated primary system
Also provides a great backout plan
The change process should be as ______ as possible.
Automated
Why is it important to consider restarting after a change has been implemented? (3 reasons)
It can test if the change can withstand a power outage
A restart may be necessary to implement a change
This contributes to downtime; users may need to logout
Why is it important to consider legacy applications during change management? (3 reasons)
They are often no longer supported by the dev; you’re now the support team
No one may understand how to work with the system, so they are afraid to change it. You may need to document the application so that in the future, it is easier to support it.
It might have quirks that are unique to it.
Why are dependencies important to consider during change management?
Some applications may not work until another application is installed/updated
This widens the scope of the change
Dependent applications might not even be on the same system
Why is documentation important during change management?
Documentation can become outdated very quickly, so it’s important to be required alongside the change management
Update diagrams to reflect new configurations/layouts
Update policies/procedures to reflect new applications
Why is version control important to consider during change management?
Helps revert to a previous setting if one version does not work properly with the rest of the network
Affects configurations, patches, and registry entries