In SAP Build Work Zone, advanced edition, users can share feed updates in two primary locations. A 'Workspace' provides a collaborative feed where team or project members can post updates, comments, and files, fostering group collaboration. Additionally, a user's 'Profile' page contains a personal feed or wall. This allows individuals to post personal status updates, share photos, and engage in discussions visible to their network, similar to a social media profile.

A. Tools: This area within a workspace is for accessing integrated business applications and specific functionalities, not for posting social feed updates.

B. My Workspace: This is a user's private, personal space for managing their own content, tasks, and bookmarks; it is not designed for sharing updates with other users.

1. SAP Help Portal - SAP Build Work Zone

advanced edition

"Workspace Feed": "The workspace feed is the central place for collaboration in a workspace. It's where you can post and view updates

comments

and discussions from other workspace members." This source confirms that a Workspace (C) has a feed for sharing updates.

2. SAP Help Portal - SAP Build Work Zone

advanced edition

"Managing Your Profile": "Your profile page is your personal space in your company's SAP Build Work Zone

advanced edition. You can post updates on your profile wall

upload and manage your content

and view your bookmarks." This source confirms that a user's Profile (D) has a wall/feed for updates.

3. SAP Help Portal - SAP Build Work Zone

advanced edition

"My Workspace": "My Workspace is your own personal and private workspace. It's a place where you can upload and manage your own content

create and manage your tasks

and view your bookmarks." This source clarifies that My Workspace (B) is private and not for sharing updates with others.

The Web Content Card in SAP Build Work Zone utilizes the HTML (inline frame) tag to embed external or internal web pages directly into a workpage. This is the standard modern HTML element for displaying a nested browsing context, effectively loading another HTML page within the current one. Official SAP documentation confirms this by discussing security considerations, such as the Content-Security-Policy frame-ancestors directive and the X-Frame-Options HTTP header, which are specifically designed to control whether a resource is allowed to be embedded within an .

A. : This tag is part of the obsolete element in HTML5 and is not used in modern web applications like SAP Build Work Zone.

B. : This tag is intended for embedding external content such as plugins or multimedia files, not for embedding entire HTML documents.

D. : This is an anchor tag used to create a hyperlink that navigates the user to another page, rather than embedding the page's content.

Users can access SAP Build Work Zone, advanced edition, on mobile devices through two primary methods. The first is via the SAP Mobile Start app, which serves as the native mobile entry point, providing an integrated and enhanced user experience with features like push notifications and widgets. The second method is by using a standard mobile web browser. The sites created with SAP Build Work Zone, advanced edition, are designed to be responsive, ensuring they adapt to the screen size of the mobile device for seamless access to content and applications.

C. SAP Build Work Zone Advanced app: There is no official, standalone mobile application with this specific name. The designated native mobile client is the SAP Mobile Start app.

D. SAP SuccessFactors app: This application is the dedicated mobile client for the SAP SuccessFactors HXM Suite and is not a general-purpose client for accessing the SAP Build Work Zone platform.

1. SAP Help Portal: SAP Build Work Zone

Advanced Edition - Administration Guide

Section: Setting Up Mobile Access.

This official guide explicitly states: "Users can access sites of SAP Build Work Zone

advanced edition on their mobile devices in one of the following ways: Using the SAP Mobile Start app... Using a mobile browser..." This directly validates options A and B.

2. SAP Help Portal: SAP Mobile Start - Feature Scope Description.

This document details the functionality of SAP Mobile Start

clarifying its role: "SAP Mobile Start is the native entry point to the Intelligent Enterprise that works as a mobile client for the SAP Build Work Zone

advanced edition." This confirms SAP Mobile Start as the official native app.

The integration of SAP Build Work Zone, advanced edition with the SAP Cloud Transport Management service allows for the transport of business content between subaccounts. The transport is managed by exporting content into a Multi-Target Application (MTA) archive. According to the official SAP documentation, the list of transportable artifacts explicitly includes Workspaces. When a Workspace is exported, all its dependent content, including its Workpages, assigned Applications, and UI integration cards, are automatically packaged with it for transport. Therefore, all four listed items are artifacts that can be transported using this mechanism.

This section is not applicable as all listed options (A, B, C, and D) are correct. Each artifact is part of the content that can be transported via the SAP Cloud Transport Management service integration.

1. SAP Help Portal: SAP Build Work Zone

advanced edition

"Content That Can Be Transported". This official documentation explicitly lists the content that can be transported. The list includes:

Workspaces

Workpages

Applications

UI integration cards

Roles

Themes

Content packages

(Source: SAP Help Portal

Administering SAP Build Work Zone

advanced edition > Transporting Content Between Subaccounts > Content That Can Be Transported)

2. SAP Help Portal: SAP Build Work Zone

advanced edition

"Exporting Content". This guide details the process

stating

"From the Content Manager

you can export one or more workspaces from your subaccount to an MTA file." This confirms that the workspace is the primary unit for initiating a transport

which includes all the other listed artifacts.

(Source: SAP Help Portal

Administering SAP Build Work Zone

advanced edition > Transporting Content Between Subaccounts > Exporting Content)

UI integration cards are designed to be flexible components for displaying business data from various sources on a user's workspace, such as SAP Build Work Zone.

A key characteristic is their ability to securely access data on behalf of the logged-in user. This is achieved by configuring the destination in SAP BTP with the property HTML5.ForwardAuthToken set to true, which ensures the user's identity (JWT) is forwarded to the backend system.

Furthermore, a single UI integration card can be developed to fetch and aggregate data from multiple backend systems. This is a core feature, allowing the card to present a consolidated view of information from different sources (e.g., combining data from an SAP S/4HANA system and a third-party CRM system).

C. They can only consume business data from SAP systems.

This is incorrect. UI integration cards can connect to any backend system that exposes data via standard REST or OData APIs, regardless of whether it is an SAP or non-SAP system.

D. Destinations must be maintained at the SAP BTP subaccount level.

This is incorrect. While subaccount-level destinations are commonly used, SAP Build Work Zone also supports the creation and use of site-level destinations, which are specific to a particular site.

1. SAP Help Portal - SAP Build Work Zone

advanced edition - Create a Destination for a UI Integration Card: This official guide explicitly states the requirement for the HTML5.ForwardAuthToken property. In the procedure for creating a destination

Step 6 instructs to add the property HTML5.ForwardAuthToken and set its value to true. This directly supports answer A.

Source: SAP Help Portal

SAP Build Work Zone

advanced edition

Section: Create a Destination for a UI Integration Card.

2. SAP Help Portal - SAP Integration Suite - Integration Cards: The documentation on the architecture of integration cards explains their data handling capabilities. It details how the data section of the card manifest can define requests to different URLs

which can be mapped to different destinations pointing to various backend systems. This flexibility is fundamental to their design and supports the ability to call multiple systems

validating answer B.

Source: SAP Help Portal

SAP Integration Suite

Section: Integration Cards.

3. SAP Help Portal - SAP Build Work Zone

advanced edition - Site-Level Destinations: This document describes the concept of site-level destinations

which can be created and managed within the context of a specific site. This confirms that destinations are not exclusively maintained at the subaccount level

making option D incorrect.

Source: SAP Help Portal

SAP Build Work Zone

advanced edition

Section: Administration Guide -> Configuring External Integrations -> Site-Level Destinations.