SAP C_WZADM_2404 SAP Certified Associate - SAP Build Work Zone - Implementation and Administration Exam Practice Test

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

The SAP Workflow service provides three SAP Fiori applications for working with workflows in SAP Build Work Zone1:

My Inbox: This application allows you to access and manage your workflow tasks from different sources in one central place2. You can view, approve, reject, forward, or add comments to your tasks, as well as perform mass actions on multiple tasks2. You can also customize the layout and filter options of your inbox, and use the search function to find specific tasks2.

Monitor Workflows: Workflow Definitions: This application allows you to monitor the status and performance of your workflow definitions3. You can view the details of each workflow definition, such as the version, description, start conditions, and context data3. You can also see the number of workflow instances that are running, completed, or failed for each workflow definition, and drill down to the instance level3.

Monitor Workflows: Workflow Instances: This application allows you to monitor the status and performance of your workflow instances. You can view the details of each workflow instance, such as the start time, end time, duration, and current user task. You can also see the graphicalrepresentation of the workflow model, and the log entries for each step of the workflow execution.

References: 1: SAP Workflow Service 2: My Inbox 3: Monitor Workflows: Workflow Definitions : Monitor Workflows: Workflow Instances

 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 schema of an SAP Build Work Zone URL that is visible to end users is composed of the following elements:

The unique subdomain, which is a custom name chosen by the customer when creating the SAP Build Work Zone service instance.

The DWS datacenter, which is the region where the service instance is deployed, such as eu10, us10, or ap10.

The work zone type, which is either workzone for SAP Build Work Zone, standard edition, or workzoneadv for SAP Build Work Zone, advanced edition.

The suffix .ondemand.com, which is the domain name for SAP Cloud Platform applications.

Therefore, the correct schema is https:// .ondemand.com.

The other options are incorrect because they do not follow the correct order or format of the URL elements. They also confuse the subaccount subdomain and the subaccount datacenter with the unique subdomain and the DWS datacenter. The subaccount subdomain and the subaccount datacenter are related to the SAP BTP subaccount that hosts the SAP Build Work Zone service instance, not the URL that is visible to end users.

References:

Introducing SAP Build Work Zone, Unit 2, Lesson 1, Slide 5

SAP Build Work Zone - Implementation and Administration, Unit 2, Lesson 2, Slide 6

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

 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

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

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

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

SAP Business Application Studio is the recommended IDE for developing UI Integration Cards. SAP Business Application Studio is a modular development environment that provides desktop-like experience for developing business applications on SAP Business Technology Platform. It offers a set of tools and templates to create UI Integration Cards easily and efficiently. SAP Business Application Studio also enables direct deployment of UI Integration Cards to SAP Build Work Zone content repository. References:

SAP Business Application Studio

Direct Deployment of UI Integration Cards to SAP Work Zone

Developing UI Integration Cards

UI integration cards are a way to display information and application content from different backend systems in a unified and consistent way in SAP Build Work Zone. They can support operations on the UI, such as choosing the card header or a button, and they can call multiple backend systems using destinations. Destinations are a way to connect to external services or applications using a simple name. They must be maintained at the SAP BTP subaccount level and have the HTMLS.ForwardAuth Token property set to true. This property enables the SAP Build Work Zone to forward the authentication token to the destination service. UI integration cards cannot only consume business data from SAP systems, but also from non-SAP systems, as long as they are accessible via destinations.

For more information about UI integration cards, you can refer to the following resources:

UI Integration Cards | SAP Help Portal1

Direct Deployment of UI Integration Cards to SAP Work Zone | SAP Blogs2

Developing UI Integration Cards | SAP Help Portal3

SAP Build Work Zone, advanced edition - SAP Online Help4

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

 In My Inbox, you can access content from the following components:

Workflows from SAP Build Work Zone: You can process tasks that are created by workflows that you design and run on SAP Build Work Zone. For more information, see Using My Inbox.

Workflows from SAP BTP Workflow Management: You can process tasks that are created by workflows that you design and run on SAP Business Technology Platform Workflow Management. For more information, see Configure My Inbox App.

Notifications from other SAP solutions: You can receive notifications from other SAP solutions that are integrated with SAP Build Work Zone, such as SAP SuccessFactors, SAP S/4HANA, SAP Ariba, and SAP Fieldglass. For more information, see Exploring the Information Architecture. The option B is not correct because notifications from SAP SuccessFactors are not accessed directly in My Inbox, but rather through the integration with SAP Build Work Zone. References:

Using My Inbox

Configure My Inbox App

Exploring the Information Architecture

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

To perform the initial product setup for SAP Build Work Zone, standard edition, you need to do the following steps:

Set up a trial account on SAP BTP, if you don’t have one already. This will allow you to access the SAP BTP cockpit and the SAP Build Work Zone, standard edition service. You can also use a regular account with SAP BTP Free Tier service plan for SAP Build Process Automation1.

Run the booster on SAP BTP to automatically create a subscription and a service instance for SAP Build Work Zone, standard edition. The booster will also configure the necessary roles and authorizations for you to access the service. You can find the booster in the SAP BTP cockpit under Boosters SAP Build Work Zone, standard edition21.

Optionally, you can also complete the configurator steps to customize your SAP Build Work Zone, standard edition site, such as adding a logo, a theme, and a site name. You can access the configurator from the SAP BTP cockpit under Services Instances and Subscriptions SAP Build Work Zone, standard edition Configurator3.

You don’t need to install a business content package as part of the initial product setup. This is an optional step that you can do later if you want to use predefined content for SAP Build Work Zone, standard edition, such as templates, cards, and widgets4. References:

SAP Build Work Zone, standard edition - SAP Online Help

Configure SAP Build Work Zone, Standard Edition | SAP

SAP Build Work Zone, advanced edition - SAP Online Help

Questions about SAP Build Work Zone, standard edition

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

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

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.