Pass the SAP Certified Application Associate C_WZADM_01 Questions and answers with ExamsMirror

 The following are the features of SAP Build Work Zone that enable users to create and consume content:

UI embedding: This feature allows users to embed UI elements such as UI Integration Cards, URL apps, SAPUI5 apps, and WebDynpro ABAP apps into SAP Build Work Zone pages and workspaces123. UI embedding enables users to access various applications and services from a single interface and create personalized and engaging experiences.

Guided Experience: This feature allows users to create and consume interactive and step-by-step guides that help them complete tasks and workflows in SAP Build Work Zone and other applications12. Guided Experience enables users to learn and perform complex processes with ease and efficiency.

Content Package: This feature allows users to create and consume reusable and modular content bundles that contain UI elements, guided experiences, and workspace templates124. Content Package enables users to share and distribute content across different SAP Build Work Zone instances and environments.

References: 1: https://blogs.sap.com/2021/11/16/sap-work-zone-starter-tutorials/  2: https://learning.sap.com/learning-journey/implement-and-administer-sap-build-work-zone/explaining-the-architecture-of-sap-build-work-zone_c5cfecde-4e06-448e-9755-3fc76c77f74f  3: https://blogs.sap.com/2023/03/30/access-fiori-apps-via-sap-build-work-zone-site-with-federated-sap-s-4hana-content/  4: https://blogs.sap.com/2022/11/15/sap-build-work-zone-saps-no-code-offering-for-building-business-sites/

 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

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]

 UI integration cards are the most-used method to show business data on SAP Build Work Zone workpages because they allow you to display application content from different sources side by side without the user having to switch screens. They contain a certain set of information from an app or page that’s presented to users in a specific context. You can use cards to group information, link to more details, present a summary, and much more. As a result, your users get all the information they need on a single screen. UI integration cards can also interact with each other on the same workpage, making them more dynamic and responsive. References: UI Integration Cards | SAP Help Portal, Direct Deployment of UI Integration Cards to SAP Work Zone | SAP Blogs

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

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

 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

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