Q: 3
In the SAP Activate run phase the new system is monitored, maintained, and optimized to ensure it
runs smoothly and efficiently. Which change management activity can only be realized in the run
phase of the cloud implementation?
Options
Discussion
Its C. You can't measure user adoption until the system is live, D is a trap here.
Likely C. You can only measure real user adoption once the system is live, which happens in the run phase. D happens during hypercare or even earlier sometimes, I think. Feel free to argue if you see it different.
D, not C. Pulse checks usually kick off right after go-live for feedback, so I figured it was more specific to the run phase. Official SAP Activate guides and some practice exams mention pulse checks as a key run activity, but not 100% sure.
I don’t think it’s C. D for the pulse check because those are usually a key part of user feedback right after go-live. Not 100% but that's how I've seen it handled in projects. Anyone else?
I could see D being argued, since pulse checks usually happen once people start using the new system, but isn't that sometimes done during hypercare too? I picked D, figuring checking in with users makes sense right after rollout. Not totally sure though, maybe I'm missing a detail from the Activate phases.
C tbh, only in the run phase can you gather actual user adoption metrics since before that users aren't in the live system. D (pulse check) can be done in earlier project steps too, so C fits best I think.
Option C but you might want to double-check the official guide and some exam practice tests to confirm since wording on these "only" questions can be tricky.
This is classic SAP jargon confusion! C
Option D, since pulse checks usually happen as part of post-go-live activities. I think C is a trap here, seems like both could fit but D feels more in line with run phase feedback.
C , since measuring actual user adoption only makes sense once users are active in the live system.
Be respectful. No spam.
