C is correct because ensuring alignment in architecture, configuration, and integration is one of the objectives of using scaling Scrum techniques when coordinating large teams in complex projects. Scaling Scrum techniques are methods that help to apply Scrum principles and practices across multiple teams working on a large-scale product or program. Scaling Scrum techniques aim to ensure alignment in architecture, configuration, and integration by establishing a common vision, backlog, definition of done, and cadence for the teams, and by facilitating cross-team communication and collaboration

• B is correct because Lift and Shift is one of the transition scenarios that are possible when adopting RISE with SAP. Lift and Shift is a scenario where the customer moves their existing SAP system to the cloud without changing the code or configuration. It is suitable for customers who want to reduce their infrastructure costs and complexity, and prepare for future innovation.
• C is correct because New Implementation is one of the transition scenarios that are possible when adopting RISE with SAP. New Implementation is a scenario where the customer sets up a new SAP S/4HANA system in the cloud with predefined configuration and data migration from their legacy system. It is suitable for customers who want to adopt the latest SAP innovations and best practices, and simplify their business processes.
• E is correct because System Conversion is one of the transition scenarios that are possible when adopting RISE with SAP. System Conversion is a scenario where the customer converts their existing SAP ERP system to SAP S/4HANA in the cloud, while preserving their data and customizations. It is suitable for customers who want to leverage the benefits of SAP S/4HANA, such as improved performance, user experience, and analytics, and retain their existing business processes. Verified References:
• : RISE with SAP – Business Transformation as a Service
• : RISE with SAP – Transition Scenarios

A is correct because the Scrum team is the one that determines the tasks that are required to complete the committed backlog items in a Sprint. The Scrum team is a self-organizing and cross-functional group of people who work together to deliver a potentially releasable increment of the product at the end of each Sprint. The Scrum team breaks down the user stories into smaller and manageable tasks, and assigns them to the team members based on their skills and availability.