When you create a Cl/CD job for a low-code project, which options are available in the Release stage ? Note: There are 2 correct answers to this question.

Question

Options

• ADeploy to Private Server
• BDeploy to Cloud Foundry
• CDeploy to Cloud Transport Management Service
• DUpload to FTP server

• A
  7% (1)
• B
  93% (13)

Explanation

In SAP's Continuous Integration and Delivery (CI/CD) service on BTP, the Release stage for low-code projects (such as SAP Build Apps) supports Cloud Foundry (B) as a direct runtime deployment target on BTP, and Cloud Transport Management Service (C) as the mechanism to transport applications across system landscapes (e.g., dev → test → prod). These two reflect SAP's standard, supported delivery paths for BTP-hosted low-code solutions.

Why the distractors are wrong:

• A (Private Server): SAP's CI/CD service does not offer a "Deploy to Private Server" option in the Release stage - BTP pipelines are designed for cloud-native targets, not arbitrary private infrastructure.
• D (FTP Server): FTP upload is not a recognized Release stage option; it has no place in SAP's managed CI/CD pipeline configuration.

Memory tip: Think "CF + cTMS" - Cloud Foundry is where your app runs, Cloud Transport Management is how it travels through the landscape. If a Release option isn't a standard SAP BTP runtime or transport tool, it won't appear in this stage.

No community discussion yet for this question.