SAP SAP Certified Application Associate - SAP Build Work Zone - Implementation and Administration C_WZADM_01 Exam Dumps: Updated Questions & Answers (May 2025)

 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

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

 Access to workspaces in SAP Build Work Zone is controlled by role collections, which are groups of roles that define the permissions and access rights for users. Role collections are assigned to users or groups in the SAP BTP subaccount cockpit, and they determine which workspaces the users can see and access in SAP Build Work Zone. Role collections can also be used to control the access to applications and content within the workspaces. References:

SAP Build Work Zone, advanced edition | SAP Help Portal, section “Role Collections”

Access SAP Build Work Zone, advanced edition from the SAP Build Lobby | SAP, step 2.2

Deep Dive into SAP Build Work Zone | SAP Blogs - SAP Community, section “SAP Build Work Zone, advanced edition (previously SAP Work Zone service)”

 To access the administration console of SAP Build Work Zone, you need to have the administrator permission in Digital Workspace Service. This permission is granted by the company administrator or the area administrator of the site that you want to access. Without this permission, you will not see the Administration Console option under your avatar in the User Actions menu. The other options (B, C, and D) are not related to the administration console access, but to the SAP BTP account and subaccount level permissions that are required for setting up SAP Build Work Zone. References:

SAP Build Work Zone, advanced edition - SAP Online Help

SAP Build Work Zone - Implementation and Administration

The SAP Activate Explore phase is the phase where the project team validates the fit of the standard SAP solution to the customer’s business requirements and identifies any gaps or deltas that need to be addressed1. The key deliverables of this phase are2:

Fit-to-Standard Analysis: This is a series of workshops where the project team demonstrates the predefined scenarios and processes in the SAP solution using the customer’s starter system and sample data. The customer validates the fit of the standard solution to their business needs and identifies any gaps or deltas that require additional configuration, customization, or extension3.

Data Load Preparation: This is the process of preparing the data migration objects and templates, defining the data migration strategy and approach, and performing data quality checks and cleansing. The project team also executes the initial data load to the quality system and validates the results4.

The other options are not part of the SAP Activate Explore phase, but rather of the following phases:

Integration setup: This is part of the SAP Activate Realize phase, where the project team configures and tests the integration scenarios between the SAP solution and other systems, such as legacy systems, third-party applications, or cloud services5.

Cloud System Provisioning: This is part of the SAP Activate Prepare phase, where the project team requests and receives the access to the SAP cloud systems, such as the starter system, the quality system, and the production system6.

References: 1: SAP Activate Elements and Phases | SAP Blogs 2: SAP Activate – Explore Phase: Use Fit-to-Standard to confirm business process fit and identify gaps in your SAP S/4HANA Cloud Implementation | SAP Blogs 3: Fit-to-Standard Analysis | SAP Help Portal 4: Data Load Preparation | SAP Help Portal 5: Integration Setup | SAP Help Portal 6: Cloud System Provisioning | SAP Help Portal

An administrative area is a designated space for subject matter experts to manage content and interact within their lines of business. Company administrators assign area administrators to administrative areas. Area administrators have a subset of company administrator capabilities to perform area-related tasks. The company area is created by default and it is the top level of the internal structure of the site. Information on the company level is visible to all users in the company. There can only be one company level. If you want to add multiple subsidiaries or business areas, you can create different administrative areas for them. References:

Administrative Areas

Area & Workspace Configuration

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/

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 .

 Development artifacts are the components that are created or modified by developers to implement the business requirements of a project. In SAP Activate for SAP Build Work Zone, the development artifacts include launchpad plugins and UI integration cards. Launchpad plugins are extensions that enhance the functionality of the SAP Fiori launchpad, such as adding custom tiles, actions, or notifications. UI integration cards are reusable UI components that display data from different sources in a compact and user-friendly way. Home pages and workspaces are not development artifacts, but configuration artifacts. Configuration artifacts are the settings that are applied by administrators or end users to customize the appearance and behavior of the SAP Build Work Zone service, such as creating home pages, workspaces, or assigning roles and permissions. References:

SAP Build Work Zone Developer Guide, section “Development Artifacts”

SAP Build Work Zone Administrator Guide, section “Configuration Artifacts”

 To add business apps to the Applications menu, you need to use the Content Manager tool, which is located in the Site Manager. The Content Manager includes various editors that you can use to configure apps, groups, roles, and catalogs1. You can add business apps from different sources, such as content channels or manually, and assign them to roles, groups, and catalogs2. You can also add the apps to the workpages of your site using the page designer widget gallery3. The Applications menu is a single page in SAP Build Work Zone, advanced edition, that displays the business apps as tiles that a user can launch2.

The other options are not correct, because:

Work Zone Configurator is a tool that allows you to create and manage SAP Build Work Zone, advanced edition sites, but it does not have the functionality to add business apps to the Applications menu.

Administration Console is a tool that allows you to manage the global settings and security of SAP Build Work Zone, advanced edition, but it does not have the functionality to add business apps to the Applications menu.

Channel Manager is a tool that allows you to create and manage content providers, which are sources of business apps and content, but it does not have the functionality to add business apps to the Applications menu. You need to use the Content Manager to add the apps from the content providers to your site.

References: 1: Content Manager | SAP Help Portal 2: Adding Apps to Your Site | SAP Help Portal 3: Add an SAPUI5 App to a Workpage in SAP Build Work Zone, advanced edition | SAP Developers : Work Zone Configurator | SAP Help Portal : Administration Console | SAP Help Portal : Federation of Remote Content Providers | SAP Help Portal