The integration of Microsoft SharePoint Online document libraries into SAP Build Work Zone is facilitated through a dedicated "Documents" card or widget. This interface provides users with a context menu for each document, allowing them to perform several key actions directly from the Work Zone environment. According to official SAP documentation, these primary actions include downloading a local copy of the file, editing the document (which typically opens it in the appropriate Microsoft Office Online editor in a new tab), and deleting the document, provided the user has the necessary permissions in SharePoint.

B. Annotate: Direct annotation of documents is not a standard, out-of-the-box feature provided by the SharePoint Online integration card within SAP Build Work Zone.

C. Comment: While adding comments is a supported collaborative feature, the official documentation lists Download, Edit, and Delete as the core document management actions available directly from the primary context menu.

1. SAP Help Portal: SAP Build Work Zone

advanced edition - Administration Guide.

Section: Integrating Content and Tools -> Integrating Microsoft SharePoint Online Document Libraries -> Using the Documents Card.

Content: This section explicitly lists the actions available from the document's context menu: "From the context menu of a document

you can select one of the following actions: Open

Download

Edit

Delete

Details." This directly supports answers A

D

and E as primary

listed actions. It mentions commenting as a separate capability.

Content packages in SAP Build Work Zone, advanced edition, serve as the primary mechanism for lifecycle management. They are used to bundle various configuration and content items, such as apps, roles, catalogs, groups, spaces, and pages, created in a source system (e.g., development). This bundle forms a single, transportable, and deployable unit (an .mtar file) that can be imported into a target system (e.g., quality assurance or production), ensuring consistency across the landscape.

B. Web content artifacts to a single deployable unit (package)

This is too specific. Content packages include structural and authorization artifacts like roles and catalogs, which are not solely "web content artifacts."

C. Development and content artifacts to an archive for optimized storage

The primary purpose is deployment and transport between systems, not long-term archival or optimized storage. The package is a transport container.

---

1. SAP Help Portal: SAP Build Work Zone

Advanced Edition - Administration Guide.

Section: Lifecycle Management > Transporting Your Content

Content: The documentation explicitly states

"You can transport your content items from a source to a target subaccount. To do so

you export the content items from the source subaccount as a package

and then you import this package to the target subaccount." This confirms the function of bundling artifacts into a deployable package for transport. It lists exportable items like apps

catalogs

groups

and roles

which fall under "development and content artifacts."

2. SAP Help Portal: SAP Build Work Zone

Advanced Edition - Administration Guide.

Section: Lifecycle Management > Export a Package

Content: This section details the process of creating a package (.mtar file) from selected content items. This reinforces that the package is a "single deployable unit" containing various artifacts

not just an archive for storage or limited to web content.

In SAP Build Work Zone, advanced edition (formerly SAP Jam), every workspace must be created with one of three privacy (type) settings:

• Public – visible to all authenticated users.

• Private – visible and accessible only to invited members.

• External – enables adding users from outside the tenant and is visible only to members and admins.

No “Hidden” or “Recommended” category exists at workspace-type level; those terms apply to pages or recommendation flags, not to the workspace’s privacy classification.

A. Hidden – “Hidden” applies to individual pages; there is no “Hidden” workspace type.

D. Recommended – “Recommended” is a flag used by administrators to highlight workspaces; it is not a privacy/type setting.

1. SAP Help Portal – SAP Build Work Zone

advanced edition > Building Workspaces > “Creating a Workspace”

Privacy Settings subsection (Version 2402

paragraph 2).

2. SAP Jam Collaboration Admin Guide

1H 2023

Section “Group Types”

pp. 52-55: lists Public

Private and External only.

3. SAP Build Work Zone

advanced edition Administrator Guide

2024 Q2

Section 4.3 “Workspace Privacy Options”

Table 1.

In SAP Build Work Zone, administrative areas are used to delegate administrative tasks. When an administrator first accesses the Admin Console, a default, top-level administrative area named 'Company' is automatically created. This 'Company' area is foundational and includes all users within the organization's SAP Build Work Zone instance, serving as the primary container for administration before any further delegation is configured.

A. The company area's name and description can be edited by an administrator, so it is not un-editable.

B. The company area is created automatically during the initial setup of the service; it is not an optional component.

D. The company area, by default, includes all users in the organization, making membership inherent rather than optional.

1. SAP Help Portal

SAP Build Work Zone

advanced edition Documentation. (2024). Administrative Areas. "When you first access the Admin Console

you'll see that a default administrative area called Company has been created for you. The Company area is the top-level area and it includes all the users in your organization. You can edit the Company area name and description." [Link: https://help.sap.com/docs/build-work-zone-advanced-edition/sap-build-work-zone-advanced-edition/administrative-areas]

Role collections in SAP BTP, which grant users authorizations for applications like SAP Build Work Zone, can be assigned through several methods. Administrators can perform manual assignments directly in the SAP BTP subaccount cockpit. For automated, large-scale user management, the recommended approach is to map role collections to user groups from a federated Identity Provider (IdP). Programmatically, the SCIM API provided by the Digital Workplace Service (the foundation of SAP Build Work Zone, advanced edition) allows for managing users and groups, which are in turn mapped to role collections, thus automating user provisioning and authorization.

A. SAP Build Work Zone Content Manager: This tool is used to manage content visibility by assigning roles (not role collections) to pages, apps, and widgets. It does not assign role collections to users.

C. Authorization & Trust Management Service API: While this low-level platform API can technically assign role collections, the service-specific SCIM API (B) and IdP mapping (E) are the standard and recommended methods for programmatic and automated assignments in this context.

---

1. SAP Help Portal

SAP Business Technology Platform

Assigning Role Collections: This document explicitly details the two primary methods for assignment.

For option D (BTP Cockpit): "You can assign role collections to users or user groups in the SAP BTP cockpit." (Section: Assign Users or User Groups to a Role Collection in the Cockpit)

For option E (IdP Mapping): "We recommend that you manage users and their authorizations by mapping role collections to user groups on the level of the identity provider." (Section: Map Role Collections to User Groups in Your Identity Provider)

2. SAP Help Portal

SAP Build Work Zone

advanced edition

User and Group Management with the SCIM API: This document confirms the use of the service-specific SCIM API for managing groups that are mapped to role collections.

For option B (SCIM API): "The SCIM V2.0 API allows you to manage users and groups in the Identity Directory... You can map these groups to role collections in your subaccount on the SAP BTP." (Introduction section)

3. SAP Help Portal

SAP Build Work Zone

advanced edition

About Roles and Authorizations: This document clarifies the distinction between platform-level role collections and roles managed within the Content Manager.

For option A (Content Manager): It describes how administrators use the Content Manager to "assign roles to the content that you create" to control visibility

which is distinct from assigning platform-level role collections to users. (Section: Roles)

When working with home pages in SAP Work Zone, it's crucial to understand their unique characteristics. Home pages function as the primary landing page and have a dedicated, configurable content area distinct from other spaces like workspaces. The Page Editor, used for building these pages, provides different layout options, templates, and widgets specifically tailored for a company-wide home page experience, which differ from those available for workspace pages. These differences reflect the distinct purposes of providing central navigation and communication (home page) versus team-based collaboration (workspace).

A. While external home pages are configured in the "External User Administration" area, this is a specific rule for one user type, not a general consideration for all home page work.

B. This is incorrect. SAP Work Zone uses "Audiences" to target content, allowing administrators to assign different home pages to different user groups, ensuring relevance and personalization.

1. SAP Help Portal

SAP Build Work Zone

advanced edition

Administration Guide

"Home Pages": This section describes the home page as the main landing page for users after they log in

establishing it as a dedicated area. This supports option C.

2. SAP Help Portal

SAP Build Work Zone

advanced edition

Administration Guide

"Page Templates": This document explicitly states: "There are several out-of-the-box page templates that you can use to create pages

for example

a Home Page template and a Workspace Overview template." This differentiation in templates implies different layouts and capabilities

supporting option D.

3. SAP Help Portal

SAP Build Work Zone

advanced edition

Administration Guide

"Working with the Page Editor": This guide details the use of sections

columns

and grids to create page layouts. The options and available widgets are context-sensitive depending on whether a home page or a workspace page is being edited

which further supports option D.

4. SAP Help Portal

SAP Build Work Zone

advanced edition

Administration Guide

"Audiences": This source explains that audiences can be used to target pages

directly contradicting the claim in option B that a company home page is always shown to all users. It states

"You can use audiences to target content and ensure that users only see what is relevant to them."

SAP Build Work Zone, advanced edition, extends the capabilities of the standard edition by incorporating features for creating comprehensive digital experiences. It specifically allows for the blending of business data (e.g., application tiles) with unstructured content like documents, wikis, and blogs within collaborative workspaces. Furthermore, it empowers business users (not just administrators) to create and manage their own content, such as pages and workspaces, fostering a more dynamic and collaborative environment. The standard edition primarily focuses on providing a centralized, administrator-curated launchpad for applications.

A. Integrating SAP and third party business content is a core feature of both the standard and advanced editions, as both provide a central entry point to various applications.

C. Unifying access to SAP business applications is the fundamental purpose of the standard edition, which is built upon the SAP Launchpad service.

1. SAP Help Portal

SAP Build Work Zone Documentation: "What Is SAP Build Work Zone?" This document explicitly differentiates the two editions. It states

"The advanced edition of SAP Build Work Zone expands the standard edition with capabilities to build rich and engaging business sites... It combines the launchpad experience with capabilities to blend business data and unstructured content... It also empowers business users to create content..." This directly supports answers B and D.

2. SAP Discovery Center

SAP Build Work Zone

advanced edition: The "Features" section for the advanced edition service lists capabilities such as "Workspace creation and management

" "Content management (for example

blogs

wikis

documents)

" and "Page building and layout tools for business users." These features directly correspond to empowering end-users to create content (D) and blending it with business data (B). In contrast

the standard edition's features are focused on the launchpad experience

which covers options A and C.

3. SAP Feature Scope Description for SAP Build Work Zone: This official document provides a detailed matrix comparing the features. It clearly assigns capabilities like "Workspaces

" "Knowledge Base

" "Forums

" and "Content Page Builder" exclusively to the advanced edition

which are the mechanisms for blending content (B) and enabling user-generated content (D). The standard edition is shown to cover "Application Launcher" and "Content Federation

" which relate to options A and C.

The activation and configuration of SAP Cloud Identity Services - Identity Provisioning (IPS) is a foundational setup step performed after running the initial booster for SAP Build Work Zone. This process establishes the mechanism for provisioning users and roles from a source system (like an HR system or Identity Authentication service) to the SAP Build Work Zone solution. This configuration is done once at the tenant/subscription level to manage the user base for the entire application. It is an administrative task exclusive to the subscription and is not related to individual service instances, which are primarily used for API-based interactions.

A. API-based deployment of UI integration cards

This action requires a service instance of SAP Build Work Zone (standard/api plan) and a service key to authenticate the API calls.

B. Application for users to access the solution

While the subscription provides the user-facing application, option D describes a more specific administrative scenario exclusive to the subscription's initial setup and lifecycle management.

C. API-based deployment of content packages

This process uses the Content Deployment API, which, like other APIs, requires a service instance and service key for authentication and authorization.

---

1. SAP Help Portal: SAP Build Work Zone

Advanced Edition - Initial Setup.

Reference: In the "Initial Setup" guide

the section "Run the Booster for the Initial Setup" describes the automated configuration. The subsequent manual steps

detailed in sections like "Configure Identity Provisioning

" clearly outline that IPS is configured for the entire subscription to manage user access to the application. This is distinct from service instance management.

Document: SAP Build Work Zone

Advanced Edition > Administration Guide > Initial Setup.

2. SAP Help Portal: SAP Build Work Zone

Advanced Edition - Content Deployment API.

Reference: The "Prerequisites" section for using the Content Deployment API explicitly states the need to create a service instance and a corresponding service key. This confirms that scenarios involving API-based deployment (Options A and C) are directly tied to a service instance

not just the subscription.

Document: SAP Build Work Zone

Advanced Edition > Development > APIs for SAP Build Work Zone

Advanced Edition > Content Deployment API.

3. SAP Discovery Center: Set up SAP Build Work Zone

advanced edition.

Reference: This official mission guides administrators through the setup process. Project board tasks clearly separate the "Booster: Enable SAP Build Work Zone" (which handles the subscription and high-level trust) from subsequent tasks like "Configure Identity Provisioning Service". This reinforces that IPS configuration is a subscription-level administrative task.

Document: SAP Discovery Center > Missions > Set up SAP Build Work Zone

advanced edition.

The standard and recommended architecture for a multi-tier landscape (e.g., development, quality assurance, production) on SAP Business Technology Platform (BTP) is to use separate, dedicated subaccounts for each tier. This approach ensures complete isolation of configurations, content, user authorizations, and data between the environments. You subscribe to the SAP Build Work Zone, advanced edition service in each respective subaccount, creating distinct instances. Content and configurations are then promoted across the landscape from one subaccount to another using transport mechanisms like the Content Transport service.

A. Create multiple sites within a single subscription.

This does not provide the necessary isolation for a multi-tier landscape, as all sites would share the same underlying content repository, configurations, and user base.

B. Create multiple subscriptions in an SAP BTP subaccount.

It is not technically possible to create more than one subscription for the same multitenant application, such as SAP Build Work Zone, within a single SAP BTP subaccount.

C. Create multiple services instances in an SAP BTP subaccount.

SAP Build Work Zone, advanced edition, is provisioned as an application subscription, not a service that can be instantiated multiple times within the same subaccount like a database service.

1. SAP Help Portal

SAP Business Technology Platform Documentation

Account Model: "Subaccounts let you structure a global account according to your organization's and project's requirements with regard to members

authorizations

and quotas... For example

you can create a subaccount for each of your departments

or for each of your development projects (representing a specific landscape)." This document establishes the principle of using subaccounts for landscape separation.

2. SAP Help Portal

SAP Build Work Zone

Advanced Edition Documentation

Transporting Content Between Subaccounts: "To transport your content items from a source subaccount to a target subaccount

you can use one of the following tools: Content Transport service [or] Manual transport...". This official procedure explicitly presumes the existence of separate source and target subaccounts for lifecycle management

confirming the multi-subaccount landscape model.

3. SAP Help Portal

SAP Build Work Zone

Advanced Edition Documentation

Initial Setup: The setup process

particularly when using automated boosters

guides the administrator to run the setup within a specific subaccount. This reinforces that the subscription and its environment are scoped to a single subaccount.