SAP BTP interviews cover a wide surface: accounts, runtimes, security, integration, and data. These 30 questions hit the concepts interviewers expect from a working BTP developer in 2026.
Platform Fundamentals
Q1. What is SAP BTP?
SAP Business Technology Platform is SAP's cloud platform for extension, integration, and data-to-value scenarios. It bundles runtimes, databases, integration, and AI services under one account model. It is where clean-core extensions live.
Q2. Explain the BTP account model.
Global account at the top, then directories for organization, then subaccounts where services actually run. Each subaccount belongs to a region and one or more environments. Design this hierarchy before creating anything.
Q3. What are entitlements and quotas?
Entitlements grant a subaccount the right to use a service plan; quotas limit how much of it can be consumed. Without an entitlement, the service cannot be instantiated. Misconfigured entitlements are a classic deployment blocker.
Q4. What are the BTP environments?
Cloud Foundry, Kyma, and ABAP are the main runtime environments. Cloud Foundry runs polyglot apps and services; Kyma runs containerized workloads on Kubernetes; ABAP hosts ABAP Cloud (Steampunk). Choose by workload, not habit.
Q5. What is a service plan?
A plan defines the tier and capabilities of a service instance, e.g. free, standard, or enterprise. Plans differ in limits, features, and availability. Always check which plans your region supports before designing.
Cloud Foundry and Kyma
Q6. What are orgs and spaces in Cloud Foundry?
Orgs group related work and users; spaces inside an org isolate apps and service instances per stage. Typical layout: one org per subaccount, spaces for dev, test, and prod. Roles are assigned at both levels.
Q7. What is a buildpack?
A buildpack turns your source code into a runnable droplet for a language runtime like Node.js or Java. Cloud Foundry detects or lets you specify the buildpack. Keep buildpacks current to avoid stale runtimes.
Q8. How do you deploy an app to Cloud Foundry?
Use the cf CLI with a manifest.yml describing the app, memory, routes, and bound services. The MTA deployer (cf deploy) handles multi-target archives with modules and resources. Blue-green deployment minimizes downtime.
Q9. What is Kyma used for?
Kyma is BTP's managed Kubernetes runtime for containerized microservices and serverless functions. Use it for cloud-native workloads needing Kubernetes primitives. For simple CAP apps, Cloud Foundry is usually enough.
Q10. What is an MTA?
A Multi-Target Application packages modules, resources, and service bindings into one deployable archive described by mta.yaml. The deployer resolves dependencies and binds services automatically. It is the standard deployment unit on BTP.
Security
Q11. What is XSUAA?
The Authorization and Trust Management service issues OAuth2 JWT tokens and enforces scopes and role collections. Apps validate the token and check scopes per request. It is the backbone of BTP app security.
Q12. What is the difference between a scope and a role collection?
Scopes are fine-grained permissions defined in xs-security.json; role collections bundle scopes into assignable units for users. Developers define scopes, admins assign role collections. Never hardcode authorization logic around usernames.
Q13. What does the approuter do?
The application router is the single entry point that handles authentication, token forwarding, and routing to backend microservices. It shields UIs from direct service URLs. Configure routes and auth methods in xs-app.json.
Q14. What is the destination service?
It stores connectivity definitions (URLs, auth, proxy settings) that apps consume by name instead of hardcoding endpoints. Destinations can point to on-premise systems via Cloud Connector. Always read credentials from destinations, never from code.
Q15. How do you connect BTP to an on-premise system?
Install the Cloud Connector in the corporate network, expose the needed systems, and create a destination referencing the virtual host. Traffic flows through a secure tunnel. Principal propagation passes the user identity through.
CAP, Data, and Integration
Q16. What is the Cloud Application Programming Model (CAP)?
CAP is SAP's framework for building full-stack services with CDS data models, Node.js or Java runtimes, and OData/REST APIs. It runs on Cloud Foundry or Kyma. It is the default choice for BTP extension apps.
Q17. What is SAP HANA Cloud?
The cloud database-as-a-service for BTP, offering the HANA engine with data lake options. CAP projects bind to it for persistence. Use calculation views or SQLScript for heavy data logic close to the data.
Q18. What is SAP Integration Suite?
BTP's integration platform (formerly CPI) for connecting cloud and on-premise systems via prebuilt content and custom iFlows. It handles A2A and B2B scenarios with adapters for common protocols. Monitor message processing for failures.
Q19. What is Event Mesh?
BTP's enterprise messaging service for asynchronous event-driven communication between apps. Producers publish to topics or queues; consumers subscribe. Use it to decouple services instead of synchronous chains.
Q20. What is the difference between CAP and RAP?
CAP builds cloud-native services on BTP runtimes (Node.js/Java); RAP builds transactional apps inside the ABAP stack, on-premise or ABAP Cloud. Both use CDS modeling. Choose by where the logic must run.
BTP interviews reward breadth with one level of depth: know what each service does and exactly when you would reach for it.
Development, DevOps, and Operations
Q21. What is SAP Business Application Studio?
The cloud IDE for BTP development with dev spaces for CAP, Fiori, and ABAP. It runs in the browser with preconfigured tooling. Use it when local setup is impractical or teams need consistency.
Q22. How do you implement CI/CD on BTP?
Project "Piper" provides Jenkins-based pipelines for build, test, and deployment stages. Pipelines build MTAs, run tests, and deploy across landscapes. Automate early; manual cf pushes do not scale.
Q23. How do you monitor apps on BTP?
Use the Application Logging service for logs, audit log service for security events, and SAP Cloud ALM for operations. Stream logs with cf logs during debugging. Set up alerts before production, not after an incident.
Q24. What is multi-tenancy and how does the SaaS registry help?
Multi-tenancy serves many customers from one app instance with isolated data per tenant. The SaaS Registry manages tenant subscriptions and onboarding callbacks. Your app must separate tenant data strictly, usually by tenant ID.
Q25. What is the HTML5 application repository?
It hosts static UI resources so the approuter can serve them centrally. Fiori apps deploy there instead of inside backend modules. The launchpad service then renders them as tiles.
Q26. What is SAP Build?
The low-code/no-code portfolio on BTP: Build Apps, Build Process Automation, and Build Code. It targets citizen developers and fusion teams. Know where low-code ends and pro-code (CAP) begins.
Q27. How do you handle secrets on BTP?
Store them in user-provided service instances, the credential store, or destination configurations — never in code or mta.yaml. Rotate regularly and scope access by role. Leaked secrets in git history are a painful lesson.
Q28. What is SAP AI Core?
BTP's service for operationalizing AI models with scalable inference and lifecycle management. Apps call it for generative AI and ML scenarios. Pair it with proper data grounding for enterprise use.
Q29. How do you troubleshoot a failed MTA deployment?
Check the deployer logs for the failing module, verify entitlements and quotas in the target space, and confirm service bindings resolve. Most failures are missing entitlements or wrong resource names. Deploy to dev first, always.
Q30. What does clean core mean for BTP extensions?
Keep the ERP core untouched and build extensions side-by-side on BTP using released APIs and events. It keeps upgrades safe and fast. Every extension design should start from this principle.
The strongest BTP candidates connect the dots: security via XSUAA, connectivity via destinations, deployment via MTA, and a clean-core reason for each choice.
Interviewing soon? Drop your toughest question in the comments.