SAP Business Technology Platform (BTP) distinguishes between Business users and Platform users. Business users are end-users who access applications, such as SAP Fiori apps or custom solutions, hosted on BTP to perform business tasks. Their access is managed via role collections that grant permissions to specific business functionalities. Platform users, in contrast, are administrators or developers who manage the BTP environment, including subaccounts, services, and configurations, using tools like the BTP Cockpit. They have administrative privileges to configure and deploy applications. Key users, while relevant in some SAP contexts, are not a distinct BTP user type, often overlapping with business users. Technical users are not a standard category in BTP's user classification, as their functions are covered by platform users or system accounts. This distinction ensures clear separation of responsibilities, enabling secure and efficient management of BTP resources while supporting business operations and administrative tasks in a cloud-based environment.

Composite roles in SAP systems group multiple single roles to simplify user assignment, but they have notable disadvantages. One disadvantage is that changes to the included single roles, such as adding or removing transactions, are not immediately visible in the composite role's menu, requiring a renewed import to update the composite role's structure. This delay can lead to inconsistencies during role maintenance, complicating administration. Another disadvantage is that changes to authorizations within a composite role can only be made through the included single roles, as composite roles do not allow direct authorization maintenance. This restriction limits flexibility and requires administrators to modify each single role individually, increasing effort and potential for errors. Menus from included roles can be mixed in the composite role, making option B incorrect, and deleting transactions from the composite role menu does not affect the included roles, ruling out option D. These limitations highlight the need for careful planning when using composite roles to ensure efficient and secure role management.

In SAP systems, archiving change documents for user master records involves specific archiving objects to manage historical data efficiently. The archiving object US_PASS is used to archive changes related to user passwords, such as password resets or updates, which are critical for tracking user account modifications.
Similarly, US_USER is used to archive changes to user master records, including details like user IDs, names, and group assignments, ensuring a comprehensive record of user profile modifications. These objects allow administrators to store historical data securely while freeing up system resources. In contrast, US_AUTH is related to authorization assignments, not user master record changes, and US_PROF deals with profile assignments, which are separate from user master data. By using US_PASS and US_USER, SAP ensures that changes to sensitive user information are preserved for audit and compliance purposes, supporting security governance in large-scale SAP environments. This archiving process helps maintain system performance while retaining essential historical data for regulatory and forensic analysis.

To restrict access to SAP Enterprise Search models in the SAP Fiori launchpad, the authorization objects SDDLVIEW and S_ESH_CONN are used. SDDLVIEW controls access to data definition language (DDL) views, which are often underlying components of search models, ensuring that only authorized users can access or execute these views within the Fiori environment. S_ESH_CONN governs access to enterprise search connectors, which link search models to the Fiori launchpad, allowing administrators to restrict which users can utilize specific search functionalities. These objects provide granular control over search model access, aligning with security and segregation of duties requirements. S_ESH_ADM is used for administrative tasks related to enterprise search, not direct model access, and RSDDLTIP is not a standard SAP authorization object. By leveraging SDDLVIEW and S_ESH_CONN, SAP ensures that search capabilities in the Fiori launchpad are securely managed, preventing unauthorized access to sensitive data while enabling efficient search functionality for authorized users.

In SAP S/4HANA, the user types that can log on in interactive mode are Dialog User and Service User.
Dialog Users are designed for human interaction, allowing individuals to log on via the SAP GUI or Fiori launchpad to perform tasks like data entry or reporting. They support full interactive access, including personalized sessions and user-specific settings. Service Users, while primarily used for web-based or anonymous access (e.g., via Fiori apps or web services), can also support limited interactive logon in specific scenarios, such as testing or administrative tasks, depending on system configuration. System Users are intended for background processes, like batch jobs, and do not support interactive logon. Communication Users are used for machine-to-machine interactions, such as API calls, and are not configured for interactive access. These distinctions ensure that interactive access is restricted to appropriate user types, enhancing security by limiting human logon capabilities to Dialog and Service Users while aligning with SAP's user management framework.