Free SAP C_WZADM_01 Practice Exam with Questions & Answers | Set: 2

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/

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 CloudPlatform Identity Authentication service] : [SAP Build Work Zone, advanced edition - User Menu] : [SAP Build Work Zone, advanced edition - Custom Links]

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 .

Home pages are the landing pages that users see when they access SAP Build Work Zone. They can display information that is relevant to the company, an area, or a workspace. There are some aspects that need to be considered when working with home pages, such as:

• Home pages have a dedicated content area that can be customized using the page builder. The content area is where you can add rows, columns, widgets, cards, and other elements to create a layout for your home page. The content area is different from the feed area, which shows the latest updates and notifications from the company, area, or workspace1.
• The home page editor has different layout options compared to workspaces. The home page editor allows you to create a persistent navigation bar with links to other pages or external URLs. You can also add a header image and a title to your home page. The workspace editor does not have these options, but it allows you to add tabs to organize your content into different pages2.

Some aspects that are not true about home pages are:

• External home pages can only be configured in the external user Company Admin Area. This is not true, because external home pages can also be configured in the external user Area Admin Area. External home pages are the home pages that are shown to external users, who are users that do not belong to your company but have access to some of your content. You can create external home pages for the company level and for each area level. To do so, you need to switch to the external user Company Admin Area or the external user Area Admin Area, which are separate from the internal user admin areas3.
• Company area home pages are always shown to all users. This is not true, because company area home pages are only shown to the users who belong to that specific area. Company area home pages are the home pages that are designed for a specific area or department within the company. They display information that is relevant to that area and also include the area feed. Content is shared by everyone in the specific area. To create a company area home page, you need to be an administrator that is assigned to that area1.

References:

• Home Pages
• Adding Content to Workpages
• External Users

Out of the box, you can use the following options to integrate Microsoft Teams and SAP Build Work Zone, advanced edition:

• Microsoft Teams application for SAP Build Work Zone: This is a custom app that you can download from SAP Build Work Zone, advanced edition and upload to Microsoft Teams. It allows you to access and share your workspaces, inbox, and apps from SAP Build Work Zone, advanced edition within Microsoft Teams. You can also chat with your colleagues in Microsoft Teams from your site. For more information, see 1.
• SharePoint Online integration for document repositories: This is a feature that enables you to use SharePoint Online as a document repository for your workspaces in SAP Build Work Zone, advanced edition. You can create, edit, and share documents stored in SharePoint Online from your workspaces. You can also use the Microsoft Teams chat feature as part of the SharePoint integration. For more information, see 2.
• Microsoft Teams UI integration cards: These are cards that you can use to display information from SAP Build Work Zone, advanced edition in Microsoft Teams. You can create and configure these cards using the UI Integration Card Designer in SAP Build Work Zone, advanced edition. You can also use actions and parameters to enable interactions with the cards. For more information, see 3.

The options that are not available out of the box are:

• Microsoft Teams chat enabled standalone: This is not a feature that is provided by SAP Build Work Zone, advanced edition. You can only use the Microsoft Teams chat feature as part of the SharePoint integration or the Microsoft Teams application for SAP Build Work Zone, advanced edition.
• Microsoft Teams chat enabled as part of the SharePoint integration: This is not a separate option, but rather a sub-feature of the SharePoint Online integration for document repositories. You cannot enable the Microsoft Teams chat feature without integrating with SharePoint Online.

References:

• 1: Integrating with Microsoft Teams | SAP Help Portal
• 2: Integrating with SharePoint Online | SAP Help Portal
• 3: UI Integration Cards | SAP Help Portal

A subscription of SAP Build Work Zone is an application that allows users to access the solution and its features, such as creating and joining workspaces, accessing integrated tools and applications, and personalizing their sites. A service instance of SAP Build Work Zone is a space in SAP BTP where the solution runs and where content packages and UI integration cards can be deployed using APIs. Both the subscription and the service instance require the activation of SAP Cloud Identity Services (IPS) as a prerequisite, but only the subscription requires a post-booster activation of IPS to enable user authentication and authorization. The post-booster activation of IPS is a step that must be performed after creating a subscription of SAP Build Work Zone in the SAP BTP cockpit. It involves configuring the IPS settings, such as the identity provider, the trust configuration, and the role collection mapping. The service instance does not require this step, as it inherits the IPS settings from the subscription. References:

• Create a Subscription for SAP Build Work Zone
• Create a Space and a Service Instance
• Deploy Content Packages Using APIs
• Deploy UI Integration Cards Using APIs

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]

SAP Build Work Zone APIs are application programmable interfaces that allow other SAP or third party solutions to integrate with SAP Build Work Zone, to either query data-based on scope, or create new content. Some of the tasks that can be accomplished using SAP Build Work Zone APIs are:

• Granting access to single pages: APIs support single-use tokens for granting immediate, short-term access to single pages1.
• Create new content: APIs can be used to create new content packages, HTML5 applications, extensions, or UI integration cards1.
• Query data: APIs can be used to query data from SAP Build Work Zone, such as users, groups, pages, spaces, or notifications1.

The other options are incorrect because they are related to webhook subscriptions, not APIs. Webhook subscriptions are used to register for notifications of certain updates or activities within SAP Build Work Zone, such as page creation, space deletion, or user invitation1. Webhooks can also be used to notify gamification service, which is a third party service that provides gamification features for SAP Build Work Zone2.

References:

• Explaining APIs and Webhooks, Unit 2, Lesson 3, Slides 3-6
• SAP Build Work Zone Webhook Document, Section 2.1.1