Which of the following MUST be included in emergency change control procedures?
Click on the arrows to vote for the correct answer
A. B. C. D.A.
Emergency change control procedures are used to handle unplanned changes that need to be implemented quickly to resolve an urgent issue or to mitigate a potential risk. Such changes are often implemented outside of the normal change management process, and it is important to have a set of procedures in place to ensure that these changes are properly authorized, tested, and documented.
Out of the options provided, the only answer that must be included in emergency change control procedures is option A, which is obtaining user management approval before implementing the changes. This is because emergency changes can have a high impact on the systems and the organization, and it is important to ensure that the change is authorized by the appropriate management personnel before implementing it.
Option B, which is updating production source libraries to reflect the changes, is a good practice, but it is not a requirement for emergency change control procedures. However, it is important to document the changes made and to ensure that the documentation is accurate and up-to-date.
Option C, which is using an emergency ID to move production programs into development, is not a best practice for emergency change control procedures. It is generally not advisable to move production programs into development because this can lead to inconsistencies and errors. Instead, emergency changes should be tested and deployed directly to production, after obtaining the necessary approvals.
Option D, which is requesting that the help desk makes the changes, is not a best practice for emergency change control procedures. The help desk may not have the necessary authority or expertise to make changes, and it is important to ensure that the changes are properly authorized and tested before implementing them.
In summary, emergency change control procedures should include obtaining user management approval before implementing changes, documenting the changes made, testing the changes, and deploying the changes directly to production.