For an urgent or emergency change required to restore a critical service, the standard change management process is expedited. The most common activities to be exceptionally omitted or modified are the formal Change Advisory Board (CAB) meeting and the comprehensive testing phase. A full CAB meeting is impractical to assemble quickly and is typically replaced by an approval from an Emergency CAB (ECAB) or a pre-authorized manager. Similarly, while some minimal testing is highly advisable, the full, rigorous testing cycle is often bypassed to ensure a rapid resolution. However, creating a back-out plan and recording the change (even if retroactively) are fundamental risk management and configuration control activities that should not be omitted.

A. All of them: Incorrect. Recording the change and establishing a back-out plan are critical risk mitigation and documentation activities that are considered mandatory even in emergency situations.

B. 2 and 4: Incorrect. A back-out plan is a crucial safety net for reverting a failed change and its omission would introduce unacceptable risk.

D. 3 and 4: Incorrect. Omitting a back-out plan is considered a highly risky practice, as it removes the ability to recover from a change that causes further issues.

1. University Courseware/Documentation: The University of Chicago, IT Service Management, "Change Management Process Guide." In the section on "Emergency Change," the process explicitly states, "Emergency Changes do not require... CAB approval prior to implementation." It also notes that testing may be deferred or reduced, but a "backout plan must be documented" and the change must be submitted retroactively for documentation purposes. This supports omitting the CAB meeting (3) and modifying/omitting formal testing (2), while retaining the back-out plan (4) and recording (1).

Source: University of Chicago ITS, "Change Management Process Guide," Version 2.1, Page 10, Section 5.3 "Emergency Change."

2. Academic Publication/Framework Guide: In the widely adopted ITIL framework, which heavily influences quality management in IT services, the emergency change process is distinct. It bypasses the full CAB for an Emergency CAB (ECAB). The literature emphasizes speed, and while testing is recommended, it is understood that it will be less thorough than for a normal change.

Source: Steinberg, R. A. (2011). Implementing ITIL: A practical guide to executing ITIL. Trafford Publishing. Chapter 10, "Change Management," discusses the streamlined nature of emergency changes, where formal meetings and extensive testing are sacrificed for speed, but documentation and recovery planning remain essential.

3. Peer-Reviewed Publication: Marrone, M., & Kolbe, L. M. (2011). "Uncovering ITIL claims: IT executives’ perception on benefits and performance." Journal of Strategic Information Systems, 20(3), 300-312. The article discusses the implementation of ITIL processes, including change management. It implicitly supports the need for a separate, faster process for emergencies which, by definition, must omit time-consuming steps like formal board reviews and full regression testing to be effective.

DOI: https://doi.org/10.1016/j.jsis.2011.06.004 (The principles discussed align with the differentiation between standard and emergency procedures).