Free Practice Questions for SAP C_WZADM_2404 Exam

 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

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]

Content Federation is a feature that allows SAP Build Work Zone to integrate content from remote content providers, such as SAP S/4HANA and SAP Business Suite. A remote content provider is a solution that exposes content that can be integrated in SAP Build Work Zone, such as apps, groups, catalogs, and roles. The integration of the exposed content is done at the role level. All content items related to these roles are also integrated and are visible in the runtime. For example, if an administrator of an SAP S/4HANA system exposes a business role with its assigned catalogs, groups, and applications, then SAP Build Work Zone can import this role and its related content and display it in a site. The end users who have access to this site can then launch the federated apps and groups from the site. References:

3: Federation of Remote Content Providers

[7]: Adding Apps to Your Site

A role collection is a set of roles that are required to access an application or a service in SAP BTP. A role is a granular authorization that defines what actions a user can perform on a specific resource. A user must be assigned or mapped to a role collection at the SAP BTP subaccount level to access an application that is deployed to SAP BTP (Cloud Foundry). A group is a collection of users that share the same attributes, such as department or location. A user list is a way to manage users in the SAP BTP cockpit. Neither of these are related to the access control of applications or services in SAP BTP. References:

Define a Role Collection

Assign a Role Collection to a User

 A content package is a collection of content items that are bundled together in a ZIP file that can be easily uploaded and installed into your subaccount. According to the SAP Help Portal1, the content items that can be part of a content package are:

Cards

Workspace templates

Home pages

Workflows

Workspaces

Therefore, the correct answer is A, B, and D. UI Integration Cards, workspace templates, and workflows are all examples of content items that can be included in a content package. SAP Fiori applications and launchpad (shell) plugins are not content items that can be part of a content package. References: 1: Content Packages | SAP Help Portal

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 editordoes 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

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

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