Which of the following can you use to create user lists in SAP Build Work Zone? (Choose two.)
Digital Workplace Service admin UI
Digital Workplace Service SCIM API
SAP BTP subaccount admin UI
SAP Cloud Identity Service SCIM API
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
In which SAP Activate phase are the tasks of the cutover plan executed?
Explore
Realize
Run
Deploy
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
Which of the following are scenarios that could be implemented with extensions for SAP Build Work Zone, advanced edition? (Choose three.)
Ensure single-sign-on experience for all users
Show a list of flights or hotels booked by the user in the corporate travel system
Create a new link to corporate policies in the user menu
Change the system logo and color scheme
Show a list of incidents reported by a user from an on-premise or cloud system
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]
Which of the following can be used to integrate SAP IBP with SAP Build Work Zone? (Choose three.)
UI embedding
Guided Experience
Content Federation
Task Collaboration
Content Package
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/
What is the correct order of SAP Activate methodology phases?
Deploy
Explore
Run
Realize
Prepare
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
What can be used to deploy UI Integration Cards to SAP Build Work Zone? (Choose two.)
Admin Console in SAP Build Work Zone.
SAP Business Application Studio.
Command Line Interface (CLI)
Content Manager
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.
Which SAP Build Work Zone administrator type can be assigned using the DWS SCIM API?
Support administrator
Company administrator
Area administrator
Page Content administrator
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
What are some actions that external users CANNOT do? (Choose three.)
Create workspaces
Post in workspace forums
Upload a custom profile picture
Share user homepages with other external users
Access My Workspace
External users are the most restricted user type in SAP Build Work Zone, advanced edition. They are guests of your organization and are given access to only the specific private external workspaces to which they have been invited, as well as to their dedicated home pages (for external users) and their user profile1. Therefore, some actions that external users cannot do are:
Create workspaces: External users cannot create workspaces of any type. They can only join workspaces that they are invited to by internal users or other external users2.
Share user homepages with other external users: External users cannot share their user homepages with other external users. They can only view their own user homepage, which shows the workspaces they are a member of and the content they have recently accessed3.
Access My Workspace: External users cannot access My Workspace, which is a personal workspace for internal users where they can store and manage their own content. External users can only access the workspaces they are invited to and the content they are allowed to see4.
External users can do the following actions:
Post in workspace forums: External users can post in workspace forums of the workspaces they are a member of. They can also subscribe to topics, receive notifications, and mark answers as helpful or correct5.
Upload a custom profile picture: External users can upload a custom profile picture for their user profile. They can also edit their profile information, such as name, email, phone number, and bio.
References:
1: External Users - Overview
2: Managing External Users
3: User Home Page for External Users
4: My Workspace
5: Forum Section
: User Profile
Which SAP Build Work Zone administrator types require an assignment of a role collection? (Choose three.)
Company administrator
Sub-Workspace administrator
Support administrator
Workspace administrator
Area administrator
SAP Build Work Zone administrator types are divided into three levels: company, workspace, and area. Each level has a corresponding role collection that needs to be assigned to the users who perform administrative tasks at that level. The company administrator role collection enables users to manage the overall SAP Build Work Zone service instance, such as creating workspaces, assigning workspace administrators, and configuring global settings. The support administrator role collection enables users to access the support portal and perform tasks such as viewing logs, monitoring performance, and managing incidents. The workspace administrator role collection enables users to manage a specific workspace, such as creating areas, assigning area administrators, and configuring workspace settings. The sub-workspace administrator and area administrator types do not require a role collection assignment, as they are created and managed within the SAP Build Work Zone content manager by the workspace administrator or the area administrator respectively. References:
SAP Build Work Zone, advanced edition - SAP Online Help
Explaining the Provisioning of Users and Roles in SAP Build Work Zone
Which of the following are workspace types? (Choose three.)
Hidden
Public
Private
Recommended
External
Workspace types are the categories that define the visibility and accessibility of workspaces in SAP Build Work Zone. There are three types of workspaces: public, private, and external. Public workspaces are open to all users of the system and can be discovered and joined by anyone. Private workspaces are restricted to invited members only and cannot be searched or accessed by others. External workspaces are created for external users who are not part of the system and can only access the workspace through a unique URL. Hidden and recommended are not workspace types, but workspace attributes. Hidden workspaces are those that are marked as hidden by the workspace owner or administrator and do not appear in the workspace list or recommendations. Recommended workspaces are those that are suggested to the user based on their profile, preferences, or activities. References:
What are SAP Build Work Zone workspaces? |Summer Tutorial Series |Lesson 3: Workspaces, section “Step 1 – Creating a new workspace”
[SAP Build Work Zone Administrator Guide], section “Workspaces”
How can Launchpad shell plugins be deployed to SAP Build Work Zone?
Automated deployment from SAP Business Application Studio into the DWS administration console
Direct upload into the SAP BTP subaccount HTMLS application section
Automated deployment from SAP Business Application Studio into the SAP BTP subaccount HTMLS application section
Direct upload into the DWS administration console
Launchpad shell plugins are HTML5 applications that can be deployed to SAP Build Work Zone using SAP Business Application Studio. The deployment process is automated and involves creating a project from a template, adding the shell plugin code, and deploying the project to the SAP BTP subaccount HTML5 application section. The launchpad administrator can then add the shell plugin app to the launchpad using the launchpad configuration cockpit. References:
Exploring Launchpad Plugins - SAP Learning
Add a new HTML5 application to the MTA - SAP Help Portal
Creating and Configuring Shell Plugin Apps - SAP Help Portal
In My Inbox, you can access content from which of the following components?
Workflows from SAP Build Work Zone
Notifications from SAP SuccessFactors
Workflows from SAP BTP Workflow Management
Notifications from other SAP solutions
In My Inbox, you can access content from the following components:
Workflows from SAP Build Work Zone: You can process tasks that are created by workflows that you design and run on SAP Build Work Zone. For more information, see Using My Inbox.
Workflows from SAP BTP Workflow Management: You can process tasks that are created by workflows that you design and run on SAP Business Technology Platform Workflow Management. For more information, see Configure My Inbox App.
Notifications from other SAP solutions: You can receive notifications from other SAP solutions that are integrated with SAP Build Work Zone, such as SAP SuccessFactors, SAP S/4HANA, SAP Ariba, and SAP Fieldglass. For more information, see Exploring the Information Architecture. The option B is not correct because notifications from SAP SuccessFactors are not accessed directly in My Inbox, but rather through the integration with SAP Build Work Zone. References:
Using My Inbox
Configure My Inbox App
Exploring the Information Architecture
Please match actions to the SCIM API user endpoints.POST /Users PATCH /Users/{id} GET /Users PUT /Users/{id}
Update the entire user profile
Update specific fields of a user profile
Create a user profile
Return a list of user profiles
Action
Endpoint
Create a user profile
POST /Users
Update specific fields of a user profile
PATCH /Users/{id}
Update the entire user profile
PUT /Users/{id}
Return a list of user profiles
GET /Users
The {id} parameter is a unique identifier for each user profile. The POST, PATCH, and PUT methods require a JSON body that contains the user attributes and values to be created or updated. The GET method can accept query parameters to filter, sort, or paginate the user profiles. For more details, you can refer to the SCIM 2.0 specification1 or the Microsoft Entra SCIM implementation2
Which of the following content artifacts can be transported using the SAP Cloud Transport Management service integration?
UI integration cards
Applications
Workpages
Workspaces
The SAP Cloud Transport Management service integration allows you to transport various content artifacts between subaccounts, such as UI integration cards, applications, and workpages. UI integration cards are reusable user interface elements that display data from different sources in a consistent way. Applications are software solutions that run on SAP Business Technology Platform and provide specific functionality for users. Workpages are collections of UI integration cards that can be arranged in different layouts and accessed from the SAP Build Work Zone home page. Workspaces are not content artifacts that can be transported using the SAP Cloud Transport Management service integration, but rather logical containers that group related content artifacts and provide collaboration features for users. References:
UI integration cards: [UI Integration Cards]
Applications: [Applications]
Workpages: [Workpages]
Workspaces: [Workspaces]
Which of the following features can you enable as sections in a workspace? (Choose three.)
Content
Applications
Messages
Worl
Forums
You can enable the following features as sections in a workspace: content, workpages, and forums. The content section allows you to add different types of content to your workspace, such as cards, widgets, applications, documents, links, and videos. The workpages section allows you to create and edit pages that display content in a flexible layout. The forums section allows you to create and participate in discussions with other workspace members. You can also subscribe to topics, receive notifications, and mark answers as helpful or correct. The applications and messages features are not available as sections in a workspace, but you can access them from other places. You can add applications to your workspace as content items or as tiles on your workpages. You can access messages from the notification center or from the SAP Mobile Start app. References:
Content section: [Content Section]
Workpages section: [Workpages Section]
Forums section: [Forum Section]
Applications: [Applications]
Messages: [About Notifications] and [SAP Mobile Start]