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.