Exam CISSP topic 1 question 13 discussion

A. Technical review by business owner - This is not a Change management B. User Acceptance Testing (UAT) before implementation - UAT is only testing before implement C. Cost-benefit analysis (CBA) after implementation - This is not a CM D. Business continuity testing - This could be after implementing something

Testing should be done before implementation to ensure no problems will arise after the change.

Business Continuity Testing is part of the BCP (Business Continuity Planning) and disaster recovery. It is not directly related to CM process. Therefore B is the best answer here.

I've been implementing changes in ITIL environments for over a decade. A change to the lower environment and the subsequent change to production are two separate changes, not parts of one change. You can't do user testing without first deploying so the user has something to test.

D is the answer because you continuously test processes and implement changes where necessary

UAT is always involved in any change management. You have to ensure before implementing, the changes are doing what they are built to do. Why would you do a Business continuity for every change you are carrying out? That option is to catch you out. Unless it is abig change that could cause a big downtime, you would almost never always do Business Continuity testing but UAT is a MUST.

Not sure if the question was changed or what. But it says " Included in the change management process. " This is straight from the book. Test then Implement. I'm going with UAT Testing. 4. Test the change. Once the change is approved, it should be tested, preferably on a nonproduction server. Testing helps verify that the change doesn’t cause an unanticipated problem. 5. Schedule and implement the change. The change is scheduled so that it can be implemented with the least impact on the system and the system’s customer. This may require scheduling the change during off-duty or nonpeak hours. Testing should discover any problems, but it’s still possible that the change causes unforeseen problems. Because of this, it’s important to have a rollback plan. This allows personnel to undo the change and return the system to its previous state if necessary.

B is the answer. B Change management is a process that involves planning, controlling, and implementing changes to a system or process in a structured and controlled manner. User Acceptance Testing (UAT) is a critical component of change management because it ensures that proposed changes have been thoroughly tested and approved by end-users or stakeholders before they are implemented. UAT helps ensure that the changes will meet the business requirements and expectations. While the other options (A, C, and D) may also be important in various aspects of IT and project management, they are not specific to change management. Technical review by a business owner (Option A) may be part of the change approval process, cost-benefit analysis (CBA) after implementation (Option C) may be part of post-implementation evaluation, and business continuity testing (Option D) may be related to disaster recovery planning

I am a change manager. B. User Acceptance Testing sometimes called beta testing or end-user testing, is a phase of software development in which the software is tested in the "real world" by the intended audience or business representative D. Business Continuity Testing (or Business continuity planning) is related to disaster recovery. We perform validation testing after implementation. I think D is worded to trick you.

Change management involves a systematic approach to managing changes within an organization's IT infrastructure, processes, or systems. Among the options provided: B. User Acceptance Testing (UAT) before implementation User Acceptance Testing (UAT) is a critical phase within change management. It involves testing changes in a controlled environment to ensure that they meet business requirements and are acceptable to end-users or stakeholders before the changes are implemented into the production environment. UAT helps identify potential issues, gather feedback, and validate that the changes will perform as intended, minimizing risks associated with implementation. While the other options mentioned (technical review by the business owner, cost-benefit analysis after implementation, business continuity testing) might be part of various stages in the change management process, UAT specifically focuses on testing changes before their deployment to ensure they meet user expectations and requirements.

My understanding is that change management includes request control, change control, release control, and configuration control. UAT before implementation is a key component included in release control. I would go with B.

It is B. The question refers to what elements are part of change management, the elements are: Schedule and communication plans. Find project champions User Acceptance Training (UAT) Other types of training Live communication Support and feedback Continuous learning Success analysis Therefore UAT is the correct answer. If the question were referring to what elements are necessary to maintain a BCP, these elements are: Change management Version control Error accounting

User Acceptance Testing (UAT) is a crucial component of change management. It ensures that the change (new system, feature, or process) meets the end-users' requirements and expectations before it is fully implemented

B. User Acceptance Testing (UAT) before implementation: UAT is a critical step in the change management process. It involves testing by the end-users to ensure that the system or changes meet their requirements and function correctly in a real-world scenario. This step is essential to validate that the changes will work as expected once deployed. whiles Business continuity testing is part of business continuity planning and disaster recovery rather than the change management process. It ensures that critical business functions can continue during and after a disaster. #ShadTech

Change management is the process to make sure appropriate personnel review and approve changes before they are implemented. I worked for a company that on a daily basis the owners of the system, application, or service was involved with ensuring their proposed changes were NOT going to cause an outage; that is the emphasis of Change management. I vote A

This is a routine process for a change ticket. Without this the change board/team wouldn’t even approve the change.

D is the correct answer