C_WZADM_2404 Practice Exam Questions with Answers SAP Certified Associate - SAP Build Work Zone - Implementation and Administration Certification

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”

The SAP Build Work Zone mobile app passcode policy can be configured in the SAP BTP subaccount mobile service. This is the SAP Mobile Services instance that is used by the SAP Mobile Start app as an https endpoint for authentication and routing. It provides an Admin Cockpit that allows administrators to access logs and configure specific settings for the app, such as the passcode policy. The passcode policy determines the minimum length, complexity, and expiration time of the passcode that users mustcreate to access the app. By default, the passcode should have a minimum length of 8 digits/characters and it is possible to allow biometric authentication (for example, face ID, fingerprint) upon successful passcode creation. To access the SAP BTP subaccount mobile service, administrators need to have the MobileAdmin role assigned to them and construct the URL for the SAP Mobile Services Admin Cockpit. References:

Accessing SAP Mobile Services Settings

About the SAP Build Work Zone Advanced Mobile App

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

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

Guided experiences 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 employees. References:

Guided Experiences | SAP Help Portal

Illustrating Extensibility in SAP Build Work Zone

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

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]

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.

Users can share feed updates including photos, comments and other status updates in the Workspace and Profile sections of SAP Build Work Zone, advanced edition. The Workspace section allows users to create and join workspaces that are dedicated to specific projects, teams, or topics. Users can post updates, share files, and collaborate with other members in the workspace feed. The Profile section displays activities and updates that directly affect the user on their profile wall. For example, the user will see all status updates and content posted by them or directly addressed to them (@mentions). The user can also see updates on changes to their profile information. The Tools section is where users can access various tools and applications that are integrated with SAP Build Work Zone, such as SAP Build Process Automation, SAP Build Application Studio, and SAP Analytics Cloud. The My Workspace section is where users can access their personal dashboard, tasks, notifications, and bookmarks. Neither of these sections allow users to share feed updates. References:

Workspace

Profile

Tools

My Workspace

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

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

 Content packages enable you to easily install various types of content into your subaccount1. A content package is a collection of content items such as cards, workspace templates, home pages, workflows, and workspaces that are bundled together in a ZIP file2. You can create content packages in SAP Business Application Studio, and deploy them to SAP Build Work Zone using the Development Tools for SAP Build Work Zone extension3. Content packages allow you to bundle development and content artifacts to a single deployable unit (package) that can be easily uploaded and installed in your subaccount. References: 1: SAP Build Work Zone, advanced edition - SAP Online Help 2: Content Packages | SAP Help Portal 3: Create and Deploy Content Packages for SAP Build Work Zone Advanced Edition using BTP | SAP Blogs : SAP Build Work Zone, standard edition - SAP Online Help

 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