ERPClimb logoERPClimb
Login

SAP BTP Integration BTP Fundamentals Interview Questions

BTP Fundamentals comes up in SAP BTP Integration interviews because it is one of the few areas where an interviewer can tell, in two questions, whether you have worked with the process or only read about it.

Foundational concepts of SAP Business Technology Platform covering the global account, subaccount, and entitlement hierarchy, tenant provisioning, and the runtime environments (Cloud Foundry and Kyma) that host integration and extension workloads, preparing consultants to reason about design, deployment, and support decisions across BTP-based integration projects.

This page carries 11 reviewed SAP BTP Integration btp fundamentals interview questions, each with a complete written answer and no sign-in required. The set breaks down into 3 foundational, 5 mid-level and 3 advanced questions, so you can start at the top for a first interview or skip ahead to the scenario-based items for a senior round.

The fastest way to use this page is to read the question, answer it yourself, and only then read the answer. The gap between your version and the written one is your actual revision list for btp fundamentals.

Read the full guide: SAP BTP Interview Questions

11 BTP Fundamentals questions with answers

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.
easyBTP Fundamentals

3. A mid-size company is starting with SAP BTP. Explain what BTP is and how you would organize it initially.

BTP is SAP's platform for application development and automation, integration, data and analytics, and AI. The global account holds the contract and entitlements; subaccounts (per region) host environments like Cloud Foundry or Kyma and services; directories can group subaccounts. I'd start with DEV/TEST/PROD subaccounts per solution area in one region, trust to the corporate IdP, least-privilege role collections, planned entitlements, and a transport path. Services are consumed as instances (by apps) or subscriptions (SaaS). Monitor consumption from day one.
mediumBTP Fundamentals

4. 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

5. 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

6. 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.
mediumBTP Fundamentals

7. A side-by-side extension must read S/4HANA on-premise data. Which runtime would you pick and how does it connect?

Choose the runtime by team skills and needs: Cloud Foundry for a CAP Node.js/Java app with simple operations; Kyma if containers/microservices and Kubernetes skills exist; ABAP environment for ABAP-centric teams. Connect via Cloud Connector installed on-premise (outbound tunnel, virtual host mapping, exposed paths only), the connectivity service, and a destination with proxy type OnPremise; use principal propagation if user authorizations must apply. Test with check connection and monitor Cloud Connector logs.
mediumBTP Fundamentals

8. Several apps hard-code URLs and passwords for back-end systems. How do you redesign connectivity with destinations?

Create central destinations per target system and purpose with naming conventions; set proxy type Internet or OnPremise (with location ID); choose authentication by need: OAuth2 client credentials or basic for technical integration, principal propagation or OAuth2 SAML bearer for user context; add additional properties for tools (e.g. HTML5 or SAP Build). Refactor apps to read destinations via the destination service, remove secrets from code, and transport destination definitions per environment.
hardBTP Fundamentals

9. 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

10. 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

11. 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.

Related lesson

BTP Fundamentals Part 3: Destinations for On-Premise and Cloud Systems

Related topics

Integration SuiteJoule Studio and AI AgentsCPI iFlowsCAPAPI ManagementEvent MeshCloud ConnectorSAP AI Agent HubIdentity AuthenticationSAP BuildTransport ManagementKyma Runtime

Next practice step

Practice with Interview AITake a mock test

Go deeper on this topic