When using the Local SAP S/4HANA Database Schema migration approach, file size limitations are as follows:
Option A: 160 MB per file
This option is incorrect. The maximum file size is measured per ZIP file, not per individual file.
Option B: 100 MB per ZIP file
This option is correct. The maximum allowed size for each ZIP file is 100 MB.
Option C: 160 MB per ZIP file
This option is correct. In some contexts, the maximum ZIP file size is 160 MB, depending on system configurations.
Option D: 100 MB per file
This option is incorrect. The limitation applies to ZIP files, not individual files.
In summary, when migrating data using the Local SAP S/4HANA Database Schema approach, ensure that each ZIP file does not exceed 100 MB or 160 MB, depending on your system's specific configuration and limitations.

In SAP S/4HANA Cloud, private edition, assigning roles to users is managed through the SAP Fiori app" Maintain Business Users". This application allows administrators to assign business roles to users, thereby granting them the necessary permissions to access specific applications and perform their job functions.
Option A: SAP Fiori app "Maintain Business Users"
This option is correct. The "Maintain Business Users" app is designed for assigning business roles to users, facilitating the management of user permissions within the system.
Option B: SAP Fiori app "Launchpad Designer"
This option is incorrect. The "Launchpad Designer" app is utilized for configuring the layout and content of the SAP Fiori launchpad, not for assigning roles to users.
Option C: SAP Fiori app "Maintain Business Roles"
This option is incorrect. While the "Maintain Business Roles" app is used to create and manage business roles, the actual assignment of these roles to users is performed through the "Maintain Business Users" app.
Option D: Role maintenance in the SAP GUI
This option is incorrect. In SAP S/4HANA Cloud, private edition, role assignments are managed via SAP Fiori apps rather than the traditional SAP GUI.
Therefore, to assign roles to users in SAP S/4HANA Cloud, private edition, the appropriate tool is the SAP Fiori app"Maintain Business Users".

Migrating data directly from an SAP ERP system (e.g., ECC) to SAP S/4HANA Cloud Private Edition involves transferring data without intermediate staging or external tools. Let's evaluate the options:
* A. A Remote Function Call (RFC) connects the SAP ERP source system to the SAP S/4HANA Migration Cockpit: This is correct. The SAP S/4HANA Migration Cockpit supports direct data migration from an SAP ERP system using an RFC connection. This method, known as the "Direct Transfer" approach, allows the Migration Cockpit to extract data from the source SAP system (e.g., ECC) in real-time via RFC, map it to S/4HANA structures, and load it into the target system. It's designed for SAP-to-SAP migrations and is a standard feature for Private Edition under a new implementation or selective data transition scenario.
* B. The Software Update Manager (SUM) tool migrates the legacy database from the SAP ERP source system to SAP S/4HANA Cloud Private Edition: This is incorrect. SUM is used for system conversions (e.g., upgrading ECC to S/4HANA), not direct data migration. It handles database migration and conversion as part of an in-place upgrade, not a separate data transfer to a cloud system.
* C. Extract, Transform, and Load (ETL) tools are used to migrate data from the SAP ERP source system to SAP S/4HANA Cloud Private Edition (through a separate SAP HANA staging database)
This is incorrect. While ETL tools (e.g., SAP Data Services) can be used with a staging database approach in the Migration Cockpit, this is not "direct" migration-it involves an intermediary step, disqualifying it from this context.
* D. SAP Integration Suite connects the SAP ERP source system to the SAP S/4HANAMigration Cockpit: This is incorrect. SAP Integration Suite is a middleware tool for ongoing integrations (e.g., syncing data between systems), not a data migration tool for one-time transfers like those handled by the Migration Cockpit.
In summary, data is migrated directly from an SAP ERP system to SAP S/4HANA Cloud Private Edition usingA(A Remote Function Call (RFC) connects the SAP ERP source system to the SAP S/4HANA Migration Cockpit).
References:
* SAP Learning: "SAP S/4HANA Migration Cockpit - Direct Transfer" (learning.sap.com)
* SAP Help Portal: "Direct Data Migration with RFC" (help.sap.com)
* SAP Official Site: "SAP S/4HANA Cloud Private Edition - Data Migration" (www.sap.com)

Key-user in-app extensibility in SAP S/4HANA Cloud Private Edition allows users to make specific adaptations and extensions directly within the system.
Option A: Define a custom table in the SAP Fiori app "Custom Business Objects." This option is correct. The "Custom Business Objects" app enables key users to create custom business objects, which include defining custom tables, without the need for developer intervention.
Option B: Create a custom object with the Business Object Processing Framework (BOPF).
This option is incorrect. Creating custom objects with BOPF requires developer skills and access to development tools, which goes beyond key-user in-app extensibility.
Option C: Define a core data services (CDS) view with the ABAP development tools for Eclipse.
This option is incorrect. Defining CDS views using ABAP development tools is a developer task and is not part of key-user in-app extensibility.
Option D: Create a custom application UI with UI adaptation at runtime.
This option is correct. UI adaptation at runtime allows key users to modify the user interface of applications, such as adding or hiding fields, without coding.
In summary, key-user in-app extensibility in SAP S/4HANA Cloud Private Edition includes defining custom tables using the "Custom Business Objects" app and creating custom application UIs through UI adaptation at runtime.