1.3

Question 1

Change Management

Answer 1

Orchestrated strategy to transition teams, departments, and orgs from existing state to a more desirable future state
It is necessary in modern environments due to constant changes

Question 2

CAB

Answer 2

Change advisory board, representatives from various parts of the business that are responsible for evaluation of any proposed changes

Question 3

Change Owner

Answer 3

Individual or team responsible for initiating change request. They present case for change

Question 4

Stakeholder

Answer 4

individuals with a vested interest in the change, can include business, end users or technical stakeholders

Question 5

Impact analysis

Answer 5

integral part of change management process, essential before implementation of changes. Assess potential fallout, effects and long term impacts

Question 6

Five main steps in change management are

Answer 6

1. Prepare for change
   - assess existing processes, and need for change, gather resources, engage stakeholders and ensure readiness
2. Create a vision for change (get buy-in)
3. Implement Change
4. Verifying Change (stakeholder interviews, surveys, metric analysis)
   5.Document Change (maintain record of it, lessons learned)

Question 7

Scheduled maintenance window

Answer 7

When you can implement changes

Question 8

Backout plan

Answer 8

Pre determined strategy to revert systems to their original state in case there are issues during implementation

Question 9

Testing the Results

Answer 9

validates success of the change

Question 10

SOPs

Answer 10

Standard operating procedures are
detailed step by step instructions for implementating changes

Question 11

What are allow and deny lists and why should these be reviewed before implementing a change?

Answer 11

allow- specifies entities permitted to access a resource, and deny is to stop them from accessing a resource (used by firewalls)
- review both lists when proposing changes to prevent unintended access restrictions or grants

Question 12

Restricted Activities

Answer 12

Certain tasks are labeled as restricted due to their impact on system health and security. For ex. you may not be able to change something that impacts a protected database

Question 13

Downtime

Answer 13

Any change carries the risk of downtime, that is why you should only schedule changes during maintenance windows

Question 14

App restarts

Answer 14

some changes like installing security patches may require restarts which can cause potential data loss in transit.

Question 15

Legacy apps

Answer 15

they are more sensitive to changes and can cause system malfunctions or crashes

Question 16

dependencies

Answer 16

changes on one system may effect another, need to map this out before a change

Question 17

Importance of documentation and key elements?

Answer 17

documentating changes provides a history of what, why when and it serves as a way to keep people accountable
- diagrams
- revising policies and procedures to address issues or imporvements

Question 18

version control

Answer 18

• tracks changes to documents, software and other files
• allows multiple users to collaborate and revert to previous versions when needed