C_WZADM_2404 Exam Dumps - SAP Certified Associate Questions and Answers

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 advanced edition of SAP Build Work Zone (formerly known as SAP Work Zone) extends the standard edition (formerly known as SAP Launchpad Service) by providing additional features and capabilities that are not available in the standard edition. Some of the aspects that are specific to the advanced edition are:

Blending of business data and unstructured content: The advanced edition allows users to create and consume different types of content, such as blogs, multimedia, surveys, polls, wiki pages, events, knowledge base articles, tasks, and feeds, and integrate them with business datafrom SAP and third-party applications. This enables users to have a holistic and engaging work experience that combines structured and unstructured information across different formats and channels1.

Empowering end users to create content: The advanced edition empowers business users with powerful page building and content authoring tools that enable them to create and publish content without requiring coding skills or IT support. Users can create dynamic, modern, and personalized user experiences using templates, widgets, and drag-and-drop features. Users can also collaborate and share content with their teams and colleagues using workspaces, feeds, and comments12.

The aspects that are not specific to the advanced edition are:

Integrating SAP and third-party business content: Both the standard and the advanced edition allow users to access information and processes from SAP and third-party business applications using UI integration cards, which are reusable components that display application content in a unified and consistent way. Users can also use destinations to connect to external services or applications using a simple name34.

Unifying access to SAP business applications: Both the standard and the advanced edition provide a simple, modern, and consistent user interface that provides a unified entry point to SAP business applications, such as SAP S/4HANA, SAP SuccessFactors, SAP Ariba, and SAP Analytics Cloud. Users can access the applications using role-based navigation and convenient single or no-password access via Single Sign-On (SSO)34.

 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

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

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

 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”

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

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 Build Work Zone is a service on SAP Business Technology Platform (SAP BTP) that runs on the Cloud Foundry environment. It is not available on the NEO environment, nor as a standalone on-premise solution. SAP SuccessFactors Work Zone is a product that provides HR-specific content and integration with SAP SuccessFactors HXM Suite on the SAP Build Work Zone, advanced edition solution. It is not a separate module of SAP SuccessFactors, but rather a complementary offering that enhances the user experience and productivity of HR processes. References: What you should know about SAP Build Work Zone, standard and advanced edition – formerly known as SAP Launchpad Service and SAP Work Zone | SAP Blogs, SAP Build Work Zone, advanced edition | SAP Help Portal, SAP SuccessFactors Work Zone | SAP Help Portal

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