Technical Change Management 1.3

Question 1

The Change Management team is in charge of what needs to be changed while the technical team is in charge of […] it is changed

Answer 1

How

Question 2

A technician might be asked to make changes to the […] to allow or disallow an application through the firewall

Answer 2

Allow list / Deny List

Question 3

In an Allow list everything is […] unless it is approved.

Answer 3

Blocked

Question 4

In an deny list everything is […] unless it is explicitly blocked

Answer 4

Allowed

Question 5

Restricted Activities

Answer 5

Defines the scope of what you’re allowed to change while in the maintenance window

Question 6

You want to avoid this if you can during production hours. If not possible, notify people by email. Usually part of the backout plan.

Answer 6

Downtime

Question 7

This is very common to do after making a change, and can be done to:
An application
A switch
A service
The OS

Answer 7

Restart

Question 8

[…] applications are no longer supported by the developer, yet need to maintain uptime. If it ain’t broke don’t fix it

Answer 8

Legacy

Question 9

[…] is key to keeping up with changes you made and may include:
Updating policies/procedures
Updating diagrams

Answer 9

Documentation

Question 10

[…] is used to track what version you are using and makes it easy to revert back to a known working version
- Router configs
- OS patches
- Registry changes

Hint: VC

Answer 10

Version Control