According to the web search results, IT change management is the process of tracking and managing a change throughout its entire life cycle, from start to closure, with the aim to minimize risk1. One of the steps in the IT change management process is to collect and analyze data, quantify gaps and understand resistance, and modify the plan as needed2. The final step in completing the changes to IT processes is to ensure a return to stabilized business operations, which means that the change has been successfully implemented and the expected benefits have been realized3. This step also involves closing the change request, documenting the lessons learned, and celebrating the achievements4.
The other options are not the final step in completing the changes to IT processes, but rather intermediate steps that occur before or during the change implementation. Updating the configuration management database (CMDB) is a step that occurs during the change implementation, as it involves recording and tracking the changes made to the IT assets and services. Empowering the business to embrace the changes is a step that occurs before and during the change implementation, as it involves providing communication, training, and support to help the stakeholders adopt and adapt to the changes. Updating the enterprise architecture (EA) is a step that occurs before or during the change implementation, as it involves aligning the IT strategy, processes, and systems with the business goals and requirements.
References: 1: IT change management: A comprehensive guide - ManageEngine1 2: What is Change Management? Organizational, Process, Definition ... - ASQ3 3: The Evolution of IT Change Management | Atlassian2 4: What is IT Change Management? - ServiceNow4 : What is Configuration Management Database (CMDB)? | ServiceNow : What is Organizational Change Management? | Prosci : What is Enterprise Architecture? | Gartner