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.