ERPClimb logoERPClimb
BTP · Platform Fundamentals

SAP BTP Interview Questions

BTP questions now open most SAP technical interviews, even for roles that are not platform roles. Interviewers use them to test one thing: whether you understand where extensions, integrations and data services live in a clean-core landscape — or whether you still picture everything inside the ERP box.

The questions on this page come from ERPClimb's reviewed question bank and cover the fundamentals that decide the rest of the conversation: the account model, the two runtimes, Integration Suite and iFlow thinking, how BTP reaches on-premise systems through the Cloud Connector, HANA Cloud versus on-premise HANA, the IAS/XSUAA security chain, and the CAP-versus-RAP positioning question that closes almost every BTP round.

Each answer is written to be said out loud: the concept first, the decision it drives second, and the trade-off last. If you can explain why no inbound firewall ports are needed for the Cloud Connector without hesitating, you are already ahead of most candidates.

What interviewers actually probe

Cloud Foundry versus Kyma

The runtime-choice question. Expect to justify the pick from control over containers and event-driven scale — not from which one is newer.

How BTP reaches on-premise

Cloud Connector plus Destinations is the standard connectivity probe. The follow-up is always security: the tunnel is outbound, and Principal Propagation is where strong candidates separate.

CAP versus RAP

The closing question of most BTP rounds. The expected answer positions both frameworks by stack and extension style — side-by-side and open ecosystems versus ABAP-native and S/4HANA-deep — not by declaring a winner.

8 questions with full answers

Ordered from foundational to advanced. No sign-in required.

easyBTP Fundamentals

1. Can you explain what SAP BTP is and name its five main functional pillars?

SAP Business Technology Platform (BTP) is an integrated offering that provides the technical foundation for the entire SAP ecosystem, acting as a Platform-as-a-Service (PaaS). It is organized into five main pillars: Application Development and Automation (using tools like SAP Build and CAP), Integration (SAP Integration Suite), Data and Analytics (SAP HANA Cloud and SAP Analytics Cloud), AI (SAP AI Core), and extended services. The primary goal of BTP is to allow businesses to turn data into value, compose end-to-end business processes, and build extensions without modifying the SAP S/4HANA core, adhering to the 'Keep the Core Clean' philosophy. By using BTP, developers can bridge the gap between different line-of-business applications while leveraging built-in security and governance features.
easyBTP Fundamentals

2. How are Global Accounts, Subaccounts, and Directories structured within the BTP cockpit?

In SAP BTP, the hierarchy begins with the Global Account, which represents a customer's commercial agreement with SAP and serves as the container for all resources, billing, and entitlements. To organize projects and environments, customers create Subaccounts, which are regional entities where applications are actually deployed and services are consumed. Each subaccount has its own dedicated quota, users, and regional configuration. Directories act as an intermediate organizational layer used to group subaccounts together for easier management, allowing for the application of common policies and monitoring across a specific set of subaccounts within a single Global Account. This structure allows a large enterprise to isolate development, testing, and production environments effectively while maintaining central billing.
mediumBTP Fundamentals

3. Explain the role of Destinations and the SAP Cloud Connector when connecting BTP to an on-premise S/4HANA system.

To connect BTP applications to an on-premise S/4HANA system, we use the SAP Cloud Connector in conjunction with BTP Destinations. The Cloud Connector is a small agent installed behind the customer's firewall that initiates an outbound SSL tunnel to BTP, meaning no inbound ports need to be opened, which satisfies high-security requirements. Inside the Cloud Connector, we define which specific on-premise resources (like OData services or RFCs) are exposed. On the BTP side, we create a 'Destination' which stores the connection URL (often a virtual host defined in the Cloud Connector), the proxy type (On-Premise), and the authentication credentials. When a BTP app calls the destination, the request is securely routed through the tunnel to the specific on-premise S/4HANA system.
mediumBTP Fundamentals

4. What are the primary differences between the Cloud Foundry and Kyma runtimes, and when would you choose one over the other?

The Cloud Foundry (CF) runtime is a mature, polyglot environment that uses buildpacks to manage application lifecycles, making it the go-to choice for standard business logic and CAP-based applications where the developer wants to focus on code rather than infrastructure. In contrast, the Kyma runtime is based on Kubernetes and is designed for containerized microservices and event-driven architectures using Docker and Helm. You should choose Cloud Foundry for rapid development of standard web applications and extensions where standard buildpacks suffice. Kyma is preferred when you need full control over the container orchestration, require sidecar patterns, or need to handle high-volume event processing from SAP S/4HANA using its native integration with the SAP Event Mesh.
mediumBTP Fundamentals

5. What is the purpose of the SAP Integration Suite, and can you describe a typical iFlow use case?

SAP Integration Suite is an integration platform-as-a-service (iPaaS) that allows for seamless connectivity between SAP and non-SAP systems, whether they are in the cloud or on-premise. Its core component, Cloud Integration (formerly CPI), uses Integration Flows (iFlows) to define the path and transformation logic for data. A typical iFlow use case would be integrating SAP SuccessFactors with an on-premise Payroll system: the iFlow would start with a timer or HTTPS sender, fetch changed employee records using the SuccessFactors adapter, transform the data format (e.g., JSON to XML) using a mapping step, and finally send the data to the on-premise system via the SAP Cloud Connector using the IDOC or SOAP adapter. This ensures data consistency across the landscape without direct point-to-point connections.
hardBTP Fundamentals

6. What are the differences between CAP and RAP, and how should a developer choose between them?

The Cloud Application Programming Model (CAP) and the ABAP RESTful Application Programming Model (RAP) are two distinct frameworks for building enterprise-grade services on BTP. CAP is a framework of languages, libraries, and tools for building multi-platform services, focusing on Core Data Services (CDS) for data modeling and supports both Node.js and Java. It is positioned for side-by-side extensions where you want to use open-source technologies. RAP, on the other hand, is the evolution of ABAP development, specifically designed for S/4HANA and BTP ABAP Environment. It uses CDS for data modeling and ABAP for business logic (Behavior Pools). You choose RAP when you are working within the ABAP stack or building extensions that require deep integration with existing ABAP logic, whereas CAP is chosen for modern, cloud-native applications that leverage the JavaScript or Java ecosystems.
hardBTP Fundamentals

7. How does BTP handle security using Identity Authentication Service (IAS), XSUAA, and Role Collections?

Security in BTP is managed through a combination of identity federation and fine-grained authorization. The SAP Identity Authentication Service (IAS) acts as a cloud-based Identity Provider (IdP) that handles user login and authentication, often federated with a customer's corporate Azure AD. Once a user is authenticated, the XSUAA (SAP Authorization and Trust Management) service takes over to manage authorizations within the Cloud Foundry environment by issuing OAuth2 access tokens. Developers define 'scopes' and 'roles' in their application's xs-security.json file. These roles are then grouped into 'Role Collections' in the BTP cockpit, which are finally assigned to users or user groups. This layered approach ensures that authentication is centralized while authorization remains specific to the application's needs.
hardBTP Fundamentals

8. What are the key differences between SAP HANA Cloud and the traditional on-premise SAP HANA database?

SAP HANA Cloud is a fully managed, cloud-native version of the HANA database that differs from the on-premise version primarily through its elastic scaling and storage architecture. While on-premise HANA requires manual hardware sizing and maintenance, HANA Cloud allows users to scale compute and memory independently and automatically handles patching and backups. A key technical differentiator is the multi-tier storage strategy in HANA Cloud, which includes the high-performance in-memory layer, a disk-based 'native storage extension', and an integrated Data Lake for massive volumes of cold data. This allows for better cost management as not all data needs to reside in expensive RAM. Furthermore, HANA Cloud serves as the single source of truth in BTP, providing advanced analytics, spatial, and graph capabilities as a service.

Practise by experience level

Fresher1-3 years

The questions above are tagged by the experience levels they are normally asked at, so the same page works for a first interview and for a lead-developer round.

SAP BTP Interview Questions FAQ

What is SAP BTP in one sentence?

SAP's platform-as-a-service portfolio — application development, integration, data and analytics, and AI services — used to build extensions and integrations without modifying the S/4HANA core. Interviewers listen for the clean-core connection, not a list of service names.

What is the difference between a global account and a subaccount?

The global account is the commercial contract and entitlement container; subaccounts are the regional, independently configured units where applications actually deploy and services are consumed. Directories sit between them purely for organization and shared policy.

When do you need the SAP Cloud Connector?

Whenever a BTP application must reach an on-premise system such as S/4HANA. The connector sits behind the customer firewall and opens an outbound tunnel — no inbound ports — and a BTP Destination stores the virtual host and credentials the app calls.

Is CAP replacing RAP?

No. They serve different stacks: CAP targets Node.js and Java developers building side-by-side cloud-native services, while RAP is the standard for ABAP-based development in S/4HANA and the BTP ABAP Environment. The expected answer positions them, it does not pick one.

What secures a BTP application?

Authentication runs through the Identity Authentication Service as the identity provider, and authorization through XSUAA, which issues OAuth2 tokens based on scopes and roles declared in xs-security.json. Administrators group roles into Role Collections in the cockpit and assign them to users or federated groups.

Next practice step

Practise these questions with Interview AITake a mock test

Related SAP interview topics

ERP Climb is an independent educational platform and is not affiliated with SAP SE.