1.3 Flashcards

1
Q

Change Management

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

CAB

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Change Owner

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Stakeholder

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Impact analysis

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Five main steps in change management are

A
  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)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Scheduled maintenance window

A

When you can implement changes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Backout plan

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Testing the Results

A

validates success of the change

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

SOPs

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

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

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Restricted Activities

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Downtime

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

App restarts

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Legacy apps

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

dependencies

A

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

17
Q

Importance of documentation and key elements?

A

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

18
Q

version control

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