Change agents in SAP OCM are key employees who support adoption within their units, and motivation is critical to their effectiveness in a cloud project's change network. Option A is correct because fostering visibility-e.g., being recognized by leadership during a townhall-boosts their professional profile, making their role rewarding. Imagine an agent praised for rallying their team; this public acknowledgment drives engagement. Option B is correct as peer exchange across units (e.g., in network meetings) offers collaboration and learning-e.g., a sales agent sharing tips with a finance agent-building a sense of community and value.
Option E is correct because looking behind the scenes of a transformation (e.g., understanding why cloud standardization was chosen) satisfies curiosity and gives agents a privileged perspective, enhancing their investment in the project.
Option C is incorrect-designing business processes is typically a task for process owners or consultants during fit-to-standard workshops (Explore phase), not change agents, who focus on communication and support, not process creation. Option D is also incorrect; while skill development (e.g., project management) might occur incidentally, it's not a primary motivator or structured outcome for agents, who are selected for influence, not training. SAP OCM emphasizes intrinsic and social motivators like visibility, connection, and insight to sustain agent enthusiasm, aligning with their role as grassroots advocates.
"Motivate change agents with opportunities for visibility, peer exchange, and insight into the transformation to maintain their active engagement in the change network" (SAP Activate Methodology, Change Network Motivation Strategies).

A business readiness test (or assessment) in SAP OCM, typically in the Deploy phase, evaluates preparedness for go-live. Option A is correct because its main goal is detecting people-related issues-e.g., low training uptake or resistance in a unit-that could disrupt the transition, allowing mitigation before launch. For instance, a survey showing poor process understanding triggers extra enablement.
Option B is incorrect-identifying managers needing motivation is a stakeholder analysis task (Prepare), not readiness testing's focus. Option C is incorrect; collecting communication ideas is a planning activity, not the test's purpose, which is assessment. Option D is incorrect-incentive systems are HR-related and outside OCM's readiness scope. SAP OCM uses this test to ensure a smooth go-live.
"The business readiness test aims to detect people-related issues and challenges prior to go-live, enabling timely corrective actions" (SAP Activate, Business Readiness Assessment).

A change network kick-off meeting in SAP OCM launches the change agent network. Option C is correct because the change manager outlines the approach and agent roles, setting expectations. Option D is correct as the sponsor's input underscores the project's strategic value, motivating agents. Option A is incorrect- subproject managers focus on technical areas, not the change network. Option B is also incorrect; past experiences may inform planning but aren't a typical agenda item for agents. The focus is on role clarity and project significance.
"The change network kick-off includes the change manager defining roles and the sponsor reinforcing project importance to align and motivate agents" (SAP Activate, Change Network Setup).

In SAP projects, external advisors bring expertise, while internal managers operationalize it. Option A is correct because the internal change manager, embedded in the organization, ensures knowledge transfer for sustainability. Option C is correct as the internal manager executes tasks (e.g., communication) due to their proximity to stakeholders. Option E is correct because the external advisor provides strategic approaches and tools (e.g., templates from SAP Activate), leveraging their expertise. Option B is incorrect-developing plans is collaborative, not solely external. Option D is incorrect; holistic responsibility is shared, not fully outsourced. This division balances external best practices with internal execution.
"External advisors provide best-practice approaches and tools, while internal change managers execute activities and ensure knowledge transfer for long-term capability" (SAP Activate Methodology, Change Management Roles and Responsibilities).

The change manager in SAP OCM must set boundaries to avoid being the sole "people fixer." Option A is correct-describing OCM as a "long-distance endeavor" with joint effort clarifies it's an ongoing, collective process (e.g., spanning Prepare to Run), not a solo fix-it role. For instance, adoption issues in Run require sustained teamwork, not just the change manager's intervention. Option B is correct because calling it a "team sport" emphasizes that the project team-PM, IT, business-shares responsibility (e.g., PM schedules, IT supports, OCM guides), preventing the change manager from being overburdened. Option D is correct as framing OCM as a "core leadership task" highlights that business leaders must drive buy-in (e.g., a VP addressing resistance), not just delegate to the change manager.
Option C is incorrect-OCM isn't a project management task; it's a distinct discipline collaborating with PM, not subsumed under it. Option E is incorrect; a "checkbox approach" misrepresents OCM's dynamic, adaptive nature-strict procedures don't fit SAP's agile methodology. SAP OCM stresses shared ownership to manage expectations.
"Clarify that change management is a continuous, team-based effort requiring leadership support, not a solitary or rigid task, to define its scope accurately" (SAP OCM Framework, Change Manager Role Clarification).