C_WZADM_2404 SAP Certified Associate - SAP Build Work Zone - Implementation and Administration Questions and Answers

 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

A shadow user is a user that is automatically created on the SAP BTP subaccount level when a user logs in to SAP Build Work Zone for the first time1. The shadow user is assigned the SAP BTP subaccount viewer role collection, which is required for accessing SAP Build Work Zone2. If a shadow user does not exist on the SAP BTP subaccount level, the user cannot login to SAP Build Work Zone. The other options are not valid reasons for the login issue, because:

SAP BTP global account viewer role collection is not required for accessing SAP Build Work Zone2.

Active default identity provider on SAP BTP subaccount level is a prerequisite for enabling SAP Build Work Zone3, but not a reason for the login issue.

SAP BTP subaccount viewer role collection is automatically assigned to the shadow user2, so it is not missing unless the shadow user does not exist. References: 1: Shadow Users 2: SAP BTP Subaccount Viewer Role Collection 3: Enable SAP Build Work Zone

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.

The HR content package is a collection of content items such as UI integration cards, guided experience, or workspace templates that are bundled together in a ZIP file and can be easily uploaded and installed to your subaccount1. The HR content package provides the following functionalities:

Workspace templates: These are pre-built workspaces that you can use to create your own workspaces for various HR scenarios, such as onboarding, offboarding, performance management, and so on. You can customize the workspace templates to suit your needs and preferences1.

Guided experience: These are workflow-based cards that help you perform specific tasks through a multistep process possibly spanning multiple systems. For example, you can use the Onboarding Guided Experience to provide a personalized journey for your new hires from the time they receive an offer letter to their first 90 days at your company. You can also use the Return to Workplace Guided Experience to plan a safe return to the workplace for your company employees2.

UI Integration Cards: These are cards that display data from various sources and allow you to interact with them. For example, you can use the Employee Profile Card to view and edit the personal and professional details of an employee. You can also use the Employee Feedback Card to give and receive feedback from your peers and managers1.

The HR content package does not include chatbots or content templates as part of its functionalities. References:

Guided Experiences | SAP Help Portal

SAP Help Portal

To use SAP Build Work Zone OData APIs or webhooks, you must connect to the Digital Workplace Service (DWS) component of the SAP Build Work Zone solution architecture. The DWS is responsible for providing the APIs and webhooks that enable integration with other SAP or third party solutions. The DWS also handles the user authorization and authentication using OAuth or SAML workflows. The other options are not correct because they are not related to the SAP Build Work Zone APIs and webhooks. Content Manager is a tool for managing content in SAP Build Work Zone, SAP BTP subaccount is a logical unit for managing applications and services on SAP Business Technology Platform, and SAP API Management is a service for managing, securing, and analyzing APIs. References:

Explaining APIs and Webhooks

Using Push Notifications for Webhooks

 Launchpad shell plugins are HTML5 applications that can be deployed to SAP Build Work Zone using SAP Business Application Studio. The deployment process is automated and involves creating a project from a template, adding the shell plugin code, and deploying the project to the SAP BTP subaccount HTML5 application section. The launchpad administrator can then add the shell plugin app to the launchpad using the launchpad configuration cockpit. References:

Exploring Launchpad Plugins - SAP Learning

Add a new HTML5 application to the MTA - SAP Help Portal

Creating and Configuring Shell Plugin Apps - SAP Help Portal

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

 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”

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

 To implement SAP Build Work Zone, advanced edition in a multi-tier landscape, you need to create subscriptions in separate SAP BTP subaccounts. This is because SAP Build Work Zone, advanced edition is a subscription-based service that requires a dedicated subaccount for each tenant. You cannot create multiple subscriptions or service instances in the same subaccount, nor can you create multiple sites within a single subscription. Each subscription represents a separate site with its own content,configuration, and users. By creating subscriptions in separate subaccounts, you can align your SAP Build Work Zone landscape with your core business system landscape and enable content transport across different tiers. References:

Explaining the Planning Landscape for SAP Build Work Zone

Getting Started With SAP Build Work Zone

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

 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

Content package versioning is a feature that allows you to manage the updates of content packages in SAP Build Work Zone. Content packages have three types of versions: major, minor, and patch. Each version has a different impact on the existing content items and configurations. You can choose how you want to update your content packages based on the version type. The available options are:

Automatic update only for patch versions: This option will automatically update your content packages whenever there is a new patch version available. Patch versions are the least disruptive updates that usually fix bugs or improve performance. You will still need to manually update your content packages for major and minor versions.

Manual update for all versions: This option will give you full control over when and how you want to update your content packages. You will need to manually update your content packages for all types of versions: major, minor, and patch. This option is recommended if you have customized your content packages extensively and want to avoid any potential conflicts or errors.

Automatic update for all versions: This option will automatically update your content packages whenever there is a new version available, regardless of the version type. This option is recommended if you want to always have the latest features and enhancements of your content packages. However, this option may also cause some issues or changes in your existing content items and configurations, especially for major and minor versions.

The option that is NOT available for content package versioning is manual update only for minor versions. This option does not make sense because minor versions are more significant updates than patch versions, and they may introduce new features or change existing functionalities. Therefore, it would be illogical to update only minor versions manually and leave patch versions to be updated automatically. References:

Content Package Versioning

 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

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