Free Isaca Cybersecurity Audit Certificate Actual Exam Questions - Question 10 Discussion

C imo, sticking to schedules is key in change management because delays can cause all sorts of knock-on problems for the business. If changes don’t happen on time, it can disrupt other dependent processes and slow down progress. While minimizing disruptions (B) is important, a change done late or early can still throw things off even if it’s smooth. So ensuring change happens as planned is a fundamental goal that supports keeping the business stable overall. Communication (A) and ROI validation (D) are more like parts of the bigger picture but not the primary goal themselves.

It’s B because the main point of change management is to keep everything running without hiccups. While communication and schedules matter, stopping business disruptions is the top priority here.

I get why B is popular, but I think A deserves a look too. If changes aren’t communicated properly, it can create confusion and unplanned disruptions. So making sure process owners know ahead of time can actually help minimize those disruptions indirectly. Still, between minimizing disruption directly (B) and just communicating (A), minimizing disruption seems more critical as the primary goal here. So I’d say B fits best because it’s about keeping the business stable when changes happen—that’s the whole point of change management.

I see why B stands out, but could A also be crucial since communication might prevent issues before they happen? Maybe the primary goal includes proactive communication, not just minimizing disruption after the fact.

It’s B because the main focus of change management is to keep the business running smoothly during changes. Options A and C are more about communication and timing, not the primary goal.

B vs D? I’m going with B because the main point of change management is to avoid messing up the business operations when changes happen. D sounds more like a project evaluation step rather than the primary goal during the actual change process. Communicating or scheduling are important but don’t capture the main purpose like minimizing disruption does.

Is this asking about business impact mainly or more about keeping things on track with the IT team? Seems like it could be interpreted a couple ways.