SAP C_WZADM_2404 Exam

The feed widget setting that is used on the home page level to show all public feed updates is Global. The feed widget is a type of widget that embeds a feed in an external web page. The feed widget builder allows users to create and customize feed widgets using various settings, such as the feed source, the feed type, the feed layout, and the feed filter. The feed source setting determines which feed is displayed in the widget. There are four options for the feed source setting: Public, Global, Home, and Company. The Public option displays the public feed of the site, which includes all public updates from all workspaces and members. The Global option displays the global feed of the site, which includes all public and private updates from all workspaces and members that the user has access to. The Home option displays the home feed of the user, which includes all updates that are relevant to the user, such as updates from their workspaces, followed members, and @mentions. The Company option displays the company feed of the user, which includes all updates from the user's company, such as updates from their colleagues, managers, and subordinates. The feed widget setting that is used on the home page level to show all public feed updates is Global, because it shows all the updates that the user can see on the site, regardless of their workspace or member affiliation. The other options are either too restrictive (Home and Company) or too broad (Public) for the home page level.Reference:

Widget Builders

About Widgets

Access to workspaces in SAP Build Work Zone is controlled by role collections, which are groups of roles that define the permissions and access rights for users. Role collections are assigned to users or groups in the SAP BTP subaccount cockpit, and they determine which workspaces the users can see and access in SAP Build Work Zone. Role collections can also be used to control the access to applications and content within the workspaces.Reference:

SAP Build Work Zone, advanced edition | SAP Help Portal, section ''Role Collections''

Access SAP Build Work Zone, advanced edition from the SAP Build Lobby | SAP, step 2.2

Deep Dive into SAP Build Work Zone | SAP Blogs - SAP Community, section ''SAP Build Work Zone, advanced edition (previously SAP Work Zone service)''

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.Reference:

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

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.Reference:

Explaining APIs and Webhooks

Using Push Notifications for Webhooks

The SAP Activate Explore phase is the phase where the project team validates the fit of the standard SAP solution to the customer's business requirements and identifies any gaps or deltas that need to be addressed1.The key deliverables of this phase are2:

Fit-to-Standard Analysis: This is a series of workshops where the project team demonstrates the predefined scenarios and processes in the SAP solution using the customer's starter system and sample data.The customer validates the fit of the standard solution to their business needs and identifies any gaps or deltas that require additional configuration, customization, or extension3.

Data Load Preparation: This is the process of preparing the data migration objects and templates, defining the data migration strategy and approach, and performing data quality checks and cleansing.The project team also executes the initial data load to the quality system and validates the results4.

The other options are not part of the SAP Activate Explore phase, but rather of the following phases:

Integration setup: This is part of the SAP Activate Realize phase, where the project team configures and tests the integration scenarios between the SAP solution and other systems, such as legacy systems, third-party applications, or cloud services5.

Cloud System Provisioning: This is part of the SAP Activate Prepare phase, where the project team requests and receives the access to the SAP cloud systems, such as the starter system, the quality system, and the production system6.