SAP BTP Interview Questions and Answers

• Org – created when Cloud Foundry is enabled for a subaccount.
• Spaces – isolated areas for applications and services, often per team or stage.
• Applications – deployed with buildpacks; scaled by instances, memory and disk.
• Routes – URLs mapped to applications.
• Service instances and bindings – credentials are injected into the app environment (VCAP_SERVICES).

Applications should be stateless so instances can be added or replaced at any time.

Kyma is a managed Kubernetes runtime with modules for API exposure (API rules with authentication), eventing, serverless functions, a service mesh and the SAP BTP service operator for creating BTP service instances from Kubernetes. Choose it when you need containers, fine-grained control over deployments, polyglot microservices or an existing Kubernetes skill set. Cloud Foundry remains simpler for standard CAP and Node.js or Java applications.

An MTA is a package of modules (for example a CAP service, a database deployer, an application router and UI content) and the resources (service instances) they need, described in mta.yaml. It is built into an .mtar archive with the MTA Build Tool and deployed in one step to Cloud Foundry, which creates services, deploys modules in order and binds them. MTAs are also the unit transported between subaccounts.

The application router is the single entry point for a business application's UI. It authenticates users by redirecting them to the identity provider, forwards requests with the user's token to backend services or destinations according to routes in xs-app.json, and serves static UI content. In many setups, a managed application router provided by SAP Build Work Zone is used instead of deploying your own.

• Authentication is handled by an identity provider, typically SAP Cloud Identity Services – Identity Authentication, which can also proxy to a corporate identity provider such as Microsoft Entra ID.
• Authorisation for applications is commonly provided by the Authorization and Trust Management service (XSUAA), which issues OAuth 2.0 tokens. Applications define scopes, attributes and role templates in xs-security.json.
• Administrators combine roles into role collections and assign them to users or identity provider groups.

SAP Cloud Identity Services is a set of identity services:

• Identity Authentication (IAS) – login, single sign-on, multi-factor authentication and federation with corporate identity providers.
• Identity Provisioning (IPS) – synchronises users and groups between source and target systems.
• Authorization Management – policy-based authorisation used by newer SAP cloud applications.

Many SAP cloud products, including Joule and SAP Build, expect a customer IAS tenant to be in place.

Principal propagation forwards the identity of the logged-in cloud user to a backend system, so the backend applies that user's own authorisations instead of a shared technical user. For on-premise systems it typically works through the Cloud Connector, which issues a short-lived X.509 certificate for the user; the backend maps the certificate to a user. The destination uses the *PrincipalPropagation* authentication type.

S/4HANA can publish business events, for example when a business partner or sales order changes, through its event enablement framework. Events are sent to an event broker such as SAP Event Mesh or SAP Advanced Event Mesh, where consumers subscribe through queues and topics. Consumers then react asynchronously, often calling an API for full details. This decouples systems, avoids polling and lets new consumers be added without changing the source.

Event Mesh is a capability for SAP-centric, asynchronous messaging between applications. Advanced Event Mesh is a fully managed, distributed event broker service designed for large volumes and complex landscapes, with event brokers deployable across clouds and regions, dynamic routing between brokers and an event portal for designing and governing events. The choice depends on volume, latency, topology and governance needs.

The SAP Business Accelerator Hub (formerly SAP API Business Hub) catalogues SAP APIs, events and integration content, with documentation and a sandbox. API Management in Integration Suite places API proxies in front of backends and applies policies such as authentication, quotas, spike arrest, threat protection and transformation. A developer portal lets internal or partner developers discover APIs and request access, while analytics shows usage and errors.

• Sender and receiver adapters – HTTPS, SOAP, OData, IDoc, SFTP, AS2, Kafka and others.
• Message processing steps – content modifier, router, splitter, aggregator, message mapping, XSLT, and Groovy or JavaScript scripts.
• Exception subprocess – error handling within the flow.
• Persistence – JMS queues and data stores for reliable, asynchronous processing and retries.
• Security material – keystores, credentials and OAuth clients.
• Monitoring – message processing logs with adjustable log levels.

A provider subaccount runs the application, and each customer (tenant) subscribes from its own consumer subaccount. The SaaS provisioning service calls the application on subscription, so it can set up tenant-specific resources such as database containers. CAP provides built-in multitenancy support, and tenant isolation is based on the tenant ID in the user's token.

An HDI (SAP HANA Deployment Infrastructure) container is an isolated schema with its own technical users, into which an application's design-time database artifacts (tables, views, procedures) are deployed. Each application or tenant gets its own container, which avoids naming conflicts and enables consistent, repeatable deployments. CAP generates HDI artifacts from CDS models.

SAP Datasphere provides data warehousing and data integration with business semantics. SAP Analytics Cloud provides BI, planning and predictive analytics. SAP Business Data Cloud brings these together with SAP-managed data products from SAP applications and partner data platforms, so business data can be used for analytics and AI with its context preserved. Explain them from the angle of a use case you know.

SAP Build Process Automation is a low-code tool for workflows, approvals, forms, business rules and robotic process automation. Processes can be triggered by events, APIs or forms, call S/4HANA through actions and destinations, and run bots on desktops for tasks without APIs. It suits approval extensions and repetitive tasks that should not be built inside the ERP.

SAP Build Work Zone provides business sites and launchpads on BTP. The standard edition offers a central launchpad that can federate content from S/4HANA and other SAP systems, plus custom UI5 and Fiori apps from the HTML5 application repository. The advanced edition adds workspaces, collaboration and richer content for digital workplaces.