C_WZADM_01 Practice Exam Questions with Answers SAP Certified Application Associate - SAP Build Work Zone - Implementation and Administration Certification

In SAP Build Work Zone, you can perform various actions on integrated Microsoft SharePoint Online documents, such as liking, commenting, annotating, downloading, marking as a featured item, and bookmarking1. However, you cannot edit or delete any content from SharePoint Online within SAP Build Work Zone. These actions need to be taken in SharePoint directly1. Therefore, the correct options are A. Download, B. Annotate, and C. Comment. References: 1: Exploring Integrations With Microsoft - SAP Learning

 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 admin UI. 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

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]

UI Integration Cards are reusable components that display information and application content from different backend systems in a unified and consistent way in SAP Build Work 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.

Knowledge base articles can be created in the workspaces Knowledge Base feature, which is enabled by the workspace administrator. The workspace has a Knowledge Base page that displays the knowledge base articles created in the workspace and where users can create knowledge base articles. Users can select a template, insert images, links, and videos, assign a category, and set permissions and publish settings for the knowledge base articles. Users can also view, edit, tag, like, bookmark, and comment on the published knowledge base articles. References:

• SAP Build Work Zone, advanced edition | SAP Help Portal, section “Knowledge Base”
• SAP Build Work Zone, advanced edition - SAP Online Help, section “Creating, Publishing and Editing Knowledge Base Articles”

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

My Workspace is a personal workspace that only you can access and edit1. You cannot invite other users to join your My Workspace, unlike other workspaces that can be shared with internal or external users23. The layout of My Workspace can be based on templates, just like other workspaces1. You can also create multiple tabs in My Workspace, as well as in other workspaces1. References: 1: SAP Build Work Zone, advanced edition - SAP Online Help, https://help.sap.com/docs/build-work-zone-advanced-edition/sap-build-work-zone-advanced-edition/workspaces-8ff3df94802449f3877af5c380b22c4b  2: What are SAP Build Work Zone workspaces? |Summer Tutorial Series Lesson 3: Workspaces, https://blogs.sap.com/2022/10/04/what-are-sap-work-zone-workspaces-summer-tutorial-series-lesson-3-workspaces/  3: Enhance the Digital Workplace Experience using SAP Work Zone – Overview and Components, https://blogs.sap.com/2021/03/30/enhance-the-digital-workplace-experience-using-sap-work-zone-overview-and-components/

Application tiles are created and configured in the Content Manager, which is a tool located in the Site Manager of SAP Build Work Zone. The Content Manager includes various editors that you can use to configure apps, groups, roles, and catalogs. Once configured, the app appears as a tile in the Applications page of your site - a single page that acts as an embedded launchpad. You can also implement custom visualizations for your app tiles, such as Static App Launcher and Dynamic App Launcher. References:

• 7: Adding Apps to Your Site
• 8: Add an SAPUI5 App to a Workpage in SAP Build Work Zone, advanced edition
• 9: Implement Custom Visualization

The feed widget setting that is used on the home page level to show all public feed updates is Global. The feed widget is a type of widget that embeds a feed in an external web page. The feed widget builder allows users to create and customize feed widgets using various settings, such as the feed source, the feed type, the feed layout, and the feed filter. The feed source setting determines which feed is displayed in the widget. There are four options for the feed source setting: Public, Global, Home, and Company. The Public option displays the public feed of the site, which includes all public updates from all workspaces and members. The Global option displays the global feed of the site, which includes all public and private updates from all workspaces and members that the user has access to. The Home option displays the home feed of the user, which includes all updates that are relevant to the user, such as updates from their workspaces, followed members, and @mentions. The Company option displays the company feed of the user, which includes all updates from the user’s company, such as updates from their colleagues, managers, and subordinates. The feed widget setting that is used on the home page level to show all public feed updates is Global, because it shows all the updates that the user can see on the site, regardless of their workspace or member affiliation. The other options are either too restrictive (Home and Company) or too broad (Public) for the home page level. References:

• Widget Builders
• About Widgets

The correct sequence of tasks for running the onboarding procedure for SAP Build Work Zone is as follows:

• uk.co.certification.simulator.questionpool.PList@1869ef70

• uk.co.certification.simulator.questionpool.PList@1869f030

• uk.co.certification.simulator.questionpool.PList@1869f0a0

References:

• Prerequisites
• Setting Up User Management and Authentication
• Run the Booster
• SAP BTP Onboarding Series – Step-by-Step guide to activate your SAP Build Work Zone, advanced edition
• [Post Booster Configuration]
• [Creating User Lists]
• [Run the Configurator]
• [Onboarding to SAP Build Work Zone, advanced edition – Setup and Configuration]

 Role collections are created in the Perform Post-Booster step of the product setup. This step involves running the Work Zone Configurator, which creates the role collections for SAP Build Work Zone and SAP SuccessFactors Work Zone. These role collections are used to assign authorizations to users and groups on the SAP BTP subaccount level1. References: 1: Explaining the Provisioning of Users and Roles in SAP Build Work Zone, 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

Launchpad (shell) plugins are a way to extend the functionality and appearance of the SAP Build Work Zone header bar, sub-navigation bar, user menu, and user settings. They are different from UI integration cards, which are a way to display information and application content from different backend systems in a unified and consistent way in SAP Build Work Zone. Some of the characteristics that are applicable to launchpad (shell) plugins, but not to UI integration cards, are:

• The SAP Build Work Zone Advanced extension is required in SAP Business Application Studio: This extension provides a set of tools and templates to create, test, and deploy launchpad (shell) plugins to SAP Build Work Zone. It also enables the direct deployment of the launchpad (shell) plugin 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 file1.
• The application logs can be accessed from SAP BTP cockpit: Since launchpad (shell) plugins are deployed as HTML5 applications to SAP BTP, their application logs can be viewed and downloaded from the SAP BTP cockpit, under the HTML5 Applications section. This can help troubleshoot any issues or errors that occur during the runtime of the launchpad (shell) plugin2.
• The source code can be downloaded directly from SAP BTP cockpit: Another feature of deploying launchpad (shell) plugins as HTML5 applications to SAP BTP is that their source code can be downloaded as a ZIP file from the SAP BTP cockpit, under the HTML5 Applications section. This can help backup or restore the launchpad (shell) plugin code, or share it with other developers2.

The characteristics that are not applicable to launchpad (shell) plugins, but to UI integration cards, are:

• They are managed via the administration console of DWS: UI integration cards are managed via the administration console of SAP Build Work Zone, under the UI Integration Cards section. Here, users can upload, view, edit, and delete the UI integration cards that are available for their site. Launchpad (shell) plugins are not managed via the administration console, but via the SAP Business Application Studio or the SAP BTP cockpit34.
• They are listed in the Content Manager based on the HTMLS content provider setup: UI integration cards are listed in the Content Manager of SAP Build Work Zone, under the HTMLS content provider, which is a way to connect to external HTML5 applications or UI integration cards. Users can browse, search, and add the UI integration cards to their site pages using the Content Manager. Launchpad (shell) plugins are not listed in the Content Manager, as they are not considered as content, but as extensions4 .

Shadow users are users that are created in the SAP BTP subaccount to map the users from the connected identity provider. Shadow users are required for users to access SAP Build Work Zone. The following methods can be used to create shadow users:

• Automatic creation upon login via connected identity provider: This is the recommended and default method for creating shadow users. When a user logs in to SAP Build Work Zone for the first time using an identity provider such as SAP Cloud Identity Services, a shadow user is automatically created and assigned to the role collections that are mapped to the groups attribute in the identity provider1.
• Admin UI on the SAP BTP subaccount cockpit: This is a manual method for creating shadow users. An administrator can use the SAP BTP subaccount cockpit to create and manage shadow users and assign them to role collections2.
• Authorization & Trust Management Service API: This is a programmatic method for creating shadow users. An administrator can use the Authorization & Trust Management Service API to create, read, update, and delete shadow users and assign them to role collections3.

The following methods cannot be used to create shadow users:

• Import from SAP SuccessFactors Employee Central: This method can be used to import users from SAP SuccessFactors Employee Central to SAP Cloud Identity Services, but not to create shadow users in the SAP BTP subaccount.
• CSV file upload in the SAP BTP subaccount cockpit: This method can be used to upload users and assign them to role collections in the SAP BTP subaccount, but not to create shadow users. Shadow users are created only when the users log in via the connected identity provider. References:
• 1: Explaining the Authentication Flow of SAP Build Work Zone
• 2: Assign SAP Build Work Zone Roles to Users
• 3: Authorization & Trust Management Service API
• : Importing Users from SAP SuccessFactors Employee Central
• : Uploading Users and Assigning Them to Role Collections