This is a REST API based on the System for Cross-domain Identity Management (SCIM 2.0) specification that allows you to assign roles to users directly inside SAP Build Work Zone1.

Admin UI of the SAP BTP subaccount cockpit: This is a graphical user interface that allows you to assign role collections to users on the SAP BTP subaccount level234.

Attribute mapping for the connected Identity Provider: This is a configuration option that allows you to automatically create shadow users and map role collections based on the Groups assertion attribute from the connected Identity Provider1.

References: 2: https://help.sap.com/docs/build-process-automation/sap-build-process-automation/assign-sap-build-work-zone-roles-to-users  1: https://learning.sap.com/learning-journey/implement-and-administer-sap-build-work-zone/explaining-the-provisioning-of-users-and-roles-in-sap-build-work-zone_f81cff40-ea59-49fc-8c9e-65f68b63a812  3: https://developers.sap.com/tutorials/spa-configure-workzone.html  4: https://help.sap.com/docs/btp/sap-business-technology-platform/assign-users-to-role-collections

The Fit-to-Standard Analysis is a process of identifying the gaps between the customer’s business requirements and the standard SAP solutions, and determining the best way to close those gaps1. When pre-delivered content is planned to be used, such as the content packages provided by SAP Build Work Zone, some activities can help prepare the Fit-to-Standard Analysis, such as:

Expose business content: This means making the relevant business content (for example, SAP Fiori apps) available and accessible in the launchpad component of SAP Build Work Zone. This can be done by configuring the destinations, catalogs, and roles for the business content sources2. Exposing business content can help demonstrate the standard SAP solutions and evaluate their fit with the customer’s needs.

Maintain destination to SAP SuccessFactors: This means creating and configuring a destination to connect SAP Build Work Zone to SAP SuccessFactors, which is a cloud-based human resource management system. This can be done by using the SAP BTP cockpit or the SAP Cloud Connector3. Maintaining destination to SAP SuccessFactors can help leverage the pre-built content packages for SAP SuccessFactors that are available in SAP Build Work Zone, such as the Employee Onboarding package4.

The other options are incorrect because they are not related to the pre-delivered content for SAP Build Work Zone. SAP Cloud Transportation Management service and SAP IBP are different SAP solutions that are not part of the content packages for SAP Build Work Zone.

References:

Proven practices for fit-to-standard for your SAP Activate project, Section 1

Explaining the Prepare Phase, Section 2.2

Create and Configure Destinations, Section 2.1

SAP Build Work Zone Content Packages, Section 2.2

Users can share feed updates including photos, comments and other status updates in the Workspace and Profile sections of SAP Build Work Zone, advanced edition. The Workspace section allows users to create and join workspaces that are dedicated to specific projects, teams, or topics. Users can post updates, share files, and collaborate with other members in the workspace feed. The Profile section displays activities and updates that directly affect the user on their profile wall. For example, the user will see all status updates and content posted by them or directly addressed to them (@mentions). The user can also see updates on changes to their profile information. The Tools section is where users can access various tools and applications that are integrated with SAP Build Work Zone, such as SAP Build Process Automation, SAP Build Application Studio, and SAP Analytics Cloud. The My Workspace section is where users can access their personal dashboard, tasks, notifications, and bookmarks. Neither of these sections allow users to share feed updates. References:

Workspace

Profile

Tools

My Workspace

 To create user lists in SAP Build Work Zone, you can use either the Digital Workplace Service SCIM API or the SAP Cloud Identity Service SCIM API. Both of these APIs allow you to manage users and groups programmatically using the System for Cross-domain Identity Management (SCIM) protocol. The Digital Workplace Service SCIM API is used to create user lists in the Digital Workplace Service admin UI, while the SAP Cloud Identity Service SCIM API is used to create user lists in the SAP BTP subaccount adminUI. You cannot use the Digital Workplace Service admin UI or the SAP BTP subaccount admin UI directly to create user lists, as they do not provide the option to do so. References:

Creating User Lists

Digital Workplace Service SCIM API

SAP Cloud Identity Service SCIM API

The tasks of the cutover plan are executed in the Deploy phase of SAP Activate. The Deploy phase covers the implementation of the target SAP solution into a Productive (Go Live) state for use by the target business users; this is referred to as the Project Cutover1. The cutover plan describes all required tasks that must be performed before the go-live and needs to cover the following tracks: Infrastructure, System Design, Security, Data, and Training2. The cutover plan is refined and updated during or after the cutover simulation, which is also part of the Deploy phase1. The Deploy phase ends with the successful go-live of the SAP solution and the transition to the Run phase3. References: 1: SAP Project Manager’s Guide to SAP Project Cutover 2: Cutover highlights for SAP S/4HANA New implementation 3: SAP Activate Elements and Phases

Extensions for SAP Build Work Zone, advanced edition are custom applications that can be developed and deployed to enhance the user experience and functionality of SAPBuild Work Zone, advanced edition. Extensions can be used to integrate data and content from various sources, such as SAP or third-party systems, into SAP Build Work Zone, advanced edition. Extensions can also be used to customize the look and feel of SAP Build Work Zone, advanced edition, such as changing the logo, color scheme, or layout. Extensions can be developed using SAP Business Application Studio or any other development tool that supports the Cloud Foundry environment12.

The scenarios that could be implemented with extensions for SAP Build Work Zone, advanced edition are:

Show a list of flights or hotels booked by the user in the corporate travel system (B): This scenario requires integrating data from an external system (the corporate travel system) into SAP Build Work Zone, advanced edition. This can be achieved by developing an extension that uses the SAP Build Work Zone, advanced edition APIs to fetch and display the relevant data in a card or a widget on a workpage34.

Change the system logo and color scheme (D): This scenario requires customizing the appearance of SAP Build Work Zone, advanced edition. This can be achieved by developing an extension that uses the SAP Build Work Zone, advanced edition APIs to modify the system settings, such as the logo, color scheme, or theme5.

Show a list of incidents reported by a user from an on-premise or cloud system (E): This scenario requires integrating data from another SAP or third-party system (the incident management system) into SAP Build Work Zone, advanced edition. This can be achieved by developing an extension that uses the SAP Build Work Zone, advanced edition APIs to fetch and display the relevant data in a card or a widget on a workpage34.

The scenarios that could not be implemented with extensions for SAP Build Work Zone, advanced edition are:

Ensure single-sign-on experience for all users (A): This scenario does not require developing an extension, as SAP Build Work Zone, advanced edition already supports single-sign-on (SSO) for all users. SSO can be configured by the administrator using the SAP Cloud Platform Identity Authentication service.

Create a new link to corporate policies in the user menu ©: This scenario does not require developing an extension, as SAP Build Work Zone, advanced edition already allows adding custom links to the user menu. This can be done by the administrator using the SAP Build Work Zone, advanced edition UI.

References: 1: SAP Build Work Zone, advanced edition - Developer Guide 2: SAP Build Work Zone, advanced edition - Extensions 3: SAP Build Work Zone, advanced edition - Cards and Widgets 4: SAP Build Work Zone, advanced edition - APIs 5: [SAP Build Work Zone, advanced edition - System Settings] : [SAP Build Work Zone, advanced edition - Themes] : [SAP Build Work Zone, advanced edition - Single Sign-On] : [SAP Cloud Platform Identity Authentication service] : [SAP Build Work Zone, advanced edition - User Menu] : [SAP Build Work Zone, advanced edition - Custom Links]

 The following are the features of SAP Build Work Zone that enable users to create and consume content:

UI embedding: This feature allows users to embed UI elements such as UI Integration Cards, URL apps, SAPUI5 apps, and WebDynpro ABAP apps into SAP Build Work Zone pages and workspaces123. UI embedding enables users to access various applications and services from a single interface and create personalized and engaging experiences.

Guided Experience: This feature allows users to create and consume interactive and step-by-step guides that help them complete tasks and workflows in SAP Build Work Zone and other applications12. Guided Experience enables users to learn and perform complex processes with ease and efficiency.

Content Package: This feature allows users to create and consume reusable and modular content bundles that contain UI elements, guided experiences, and workspace templates124. Content Package enables users to share and distribute content across different SAP Build Work Zone instances and environments.

References: 1: https://blogs.sap.com/2021/11/16/sap-work-zone-starter-tutorials/  2: https://learning.sap.com/learning-journey/implement-and-administer-sap-build-work-zone/explaining-the-architecture-of-sap-build-work-zone_c5cfecde-4e06-448e-9755-3fc76c77f74f  3: https://blogs.sap.com/2023/03/30/access-fiori-apps-via-sap-build-work-zone-site-with-federated-sap-s-4hana-content/  4: https://blogs.sap.com/2022/11/15/sap-build-work-zone-saps-no-code-offering-for-building-business-sites/

SAP Activate methodology is a modular and agile framework that helps project teams with detailed steps to deliver SAP S/4HANA projects. It consists of six phases that are run in an iterative manner. The phases are:

Prepare: This phase involves setting up the project, defining the scope, and planning the resources, timeline, and budget. It also includes running the booster for SAP Build Work Zone, advanced edition, which automates some of the setup steps12.

Explore: This phase involves validating and refining the solution scope, using the SAP Best Practices and SAP Model Company content as a reference. It also includes configuring the solution using the guided configuration tools and testing the fit-to-standard scenarios34.

Realize: This phase involves completing the configuration of the solution, including any customizations, extensions, and integrations. It also includes performing data migration, testing, and cutover activities56.

Deploy: This phase involves moving the solution from the quality system to the production system, and ensuring a smooth transition. It also includes providing training and enablement to the

UI Integration Cards are reusable components that display information and application content from different backend systems in a unified and consistent way in SAP BuildWork Zone. They can be deployed to SAP Build Work Zone using one of the following methods:

Admin Console in SAP Build Work Zone: This method allows users to manually upload a ZIP file that contains the UI card definition and resources to the Admin Console UI Integration Cards section, using the Upload Card button. Users can also view, edit, and delete the existing UI cards in the Admin Console1.

SAP Business Application Studio: This method allows users to directly deploy the UI card from SAP Business Application Studio to SAP Build Work Zone, using the UI Integration Card: Deploy to SAP Build Work Zone, advanced edition option in the context menu of the manifest.json file. This method requires the subscription to SAP Business Application Studio to exist on the same subaccount as the subscription to SAP Build Work Zone, and a token-exchange destination to be configured. Users can also package the UI card into a ZIP file and download it for manual upload, using the UI Integration Card: Package option2.

The methods that are not used to deploy UI Integration Cards to SAP Build Work Zone are:

Command Line Interface (CLI): This method is not supported by SAP Build Work Zone, as there is no CLI tool available for UI Integration Cards development or deployment.

Content Manager: This method is used to manage the unstructured content in SAP Build Work Zone, such as blogs, multimedia, surveys, polls, wiki pages, events, knowledge base articles, tasks, and feeds. It is not used to deploy UI Integration Cards, which are considered as structured content3.

The DWS SCIM API is a REST API based on the System for Cross-domain Identity Management (SCIM 2.0) specification that is used to manage users and user lists in the Digital Workplace Service (DWS) layer of SAP Build Work Zone1. The DWS SCIM API can be used to assign the company administrator role to users who are authorized to manage the entire SAP Build Work Zone tenant2. The company administrator role is required in addition to the role collection that is assigned to users on the SAP BTP subaccount level2.

The other options are incorrect because they are not assigned using the DWS SCIM API, but rather using the Site Manager UI or the Content Manager API. The support administrator role is assigned to users who can access the support tools and troubleshoot issues in SAP Build Work Zone3. The area administrator role is assigned to users who can manage a specific area within SAP Build Work Zone, such as spaces, pages, or notifications. The page content administrator role is assigned to users who can create and edit pages in SAP Build Work Zone.

References:

Explaining APIs and Webhooks, Unit 2, Lesson 3, Slide 5

Manage Administrators Using SCIM API, Section 2.2

About the Site Manager, Section 2.1

[About Roles and Role Assignment Restrictions], Section 2.2

[Create and Edit Pages], Section 3.1