Successful change enablement in SAP OCM ensures users adopt the system effectively. Option B is correct because an enablement team with defined roles (e.g., trainer), skills (e.g., content creation), and time ensures professional execution, avoiding ad-hoc efforts. Option C is correct as a comprehensive strategy (e.g., outlining training phases, tools) guides business areas systematically, aligning enablement with project goals.
Option D is correct because integrating enablement into the project plan (e.g., scheduling training before go- live) ensures visibility and prioritization alongside technical tasks.
Option A is incorrect-reporting to the steering committee overcomplicates governance; the enablement lead coordinates with project management, not executives directly. Option E is incorrect; fit-to-standard workshops (Explore phase) involve process owners/SMEs, not the enablement team, whose role is delivery, not needs derivation. SAP OCM emphasizes structure and integration for enablement success.
"Promote enablement success with a skilled team, a comprehensive strategy, and integration into the project plan to ensure effective user preparation" (SAP Activate, Enablement Best Practices).

Change enablement in SAP cloud implementations focuses on user adoption. Option B is correct because it encompasses all activities-training, workshops, support-that help people (end-users, key users) learn and adopt new SAP systems (e.g., S/4HANA Cloud) and processes (e.g., best practices) in their daily work. This broad definition aligns with SAP OCM's goal of ensuring sustained use post-go-live, addressing both technical skills and behavioral change. For example, enablement might include e-learning on system navigation or process simulations to ease the transition.
Option A is incorrect-supporting leadership to handle resistance is a subset of change leadership, not enablement, which targets users. Option C is incorrect; deliverables (e.g., plans, reports) support OCM broadly, not just enablement, which is action-oriented. Option D is incorrect-upskilling leaders is leadership development, not user-focused enablement. SAP OCM defines enablement as user-centric preparation.
"Change enablement refers to activities that enable people to learn and adopt new SAP systems and processes, ensuring effective integration into their work" (SAP OCM Framework, Enablement Definition).

Post-go-live adoption management is critical in SAP cloud projects due to ongoing updates. Option C is correct because cloud solutions (e.g., S/4HANA Cloud) release new features regularly, requiring users to adapt continually. Option D is correct as monitoring adoption identifies barriers (e.g., resistance, skill gaps) for resolution. Option A is incorrect-attitude shifts may occur but aren't the primary focus. Option B is incorrect; infrastructure sizing is a technical concern, not an adoption driver.
Extract from SAP OCM Concepts: SAP Activate's Run phase emphasizes sustaining adoption through feature updates and issue resolution (SAP OCM Framework).

A communication plan in SAP OCM defines roles to ensure smooth execution of change communication.
Option B is correct because content creation (e.g., drafting newsletters by a change manager) and content review (e.g., checking accuracy by a business lead) are critical responsibilities that must be assigned to avoid delays or errors. Creation involves generating messages (e.g., "Why we're moving to the cloud"), while review ensures alignment with project goals and stakeholder needs (e.g., confirming technical terms are clear). Clear assignment prevents overlap or gaps-imagine a scenario where no one knows who's drafting the go-live announcement, causing confusion.
Option A is incorrect-content approval (final sign-off, often by leadership) is distinct from review and less operational, while delivery (e.g., sending emails) is logistical, often handled by tools or admins, not a core creative responsibility. Option C is incorrect; content assessment (evaluating effectiveness) is post-delivery analysis, and archiving is administrative, not plan-specific. Option D is incorrect-content alignment (ensuring consistency) is part of review, and evaluation overlaps with assessment, neither requiring separate assignment. SAP OCM focuses on creation and review as foundational tasks.
"The communication plan assigns responsibilities for content creation and review to ensure messages are developed and validated effectively" (SAP Activate, Communication Plan Structure).

In SAP Activate, project management (PM) and change management (CM) have distinct roles. Option D is correct-PM handles "hard factors" (e.g., timelines, budgets), while CM addresses "soft factors" (e.g., people, adoption). Option A is incorrect-CM doesn't manage team cooperation. Option B is misleading; both levels overlap. Option C is incorrect-PM and CM share objectives and vision. This division ensures technical and human aspects are covered.
"Project management drives hard factors like schedule and scope, while change management focuses on soft factors like adoption and resistance" (SAP Activate, PM and CM Collaboration).