SAP BTP Integration Interview Questions

Start from the expected business outcome, identify the first failed agent, tool, workflow, context or governance step, and use runtime evidence before changing the design. Scenario context: An agent passes conversational testing but in production calls a pricing API twice for every request. Action-level evaluation reveals the unnecessary tool loop and the team adds a step limit and regression test. Avoid: - Text-only evaluation.\n- No action-level assertions.\n- No runtime limits.\n- Sensitive logs.\n- No regression after tool changes.

I would compare environment-specific configuration first: externalized receiver URLs, destinations, credentials/security material, certificates, connectivity and tenant-specific values. Then I would inspect deployment status and message monitoring to find the first failing step. I would not change mapping logic until the runtime evidence shows the mapping is actually the problem.

Start from the expected business outcome, identify the first failed agent, tool, workflow, context or governance step, and use runtime evidence before changing the design. Scenario context: An invoice-resolution agent retries an update after a timeout and creates a duplicate change because the first call actually succeeded. The design is changed to use a stable idempotency key and a workflow state that checks the previous outcome before retrying. Avoid: - Agent used as workflow state store.\n- No timeout.\n- Blind retries.\n- No escalation.\n- Write operations without idempotency.

Start from the expected business outcome, identify the first failed agent, tool, workflow, context or governance step, and use runtime evidence before changing the design. Scenario context: An organization has 60 agents across several platforms. Ten have no owner and multiple teams built overlapping procurement agents. Central discovery plus LeanIX/Signavio context allows consolidation and clarifies which agents actually improve business processes. Avoid: - No owner.\n- Agent count used as success metric.\n- Classic assets ignored during migration.\n- No retirement control.\n- Credentials left active after decommission.

Start from the expected business outcome, identify the first failed agent, tool, workflow, context or governance step, and use runtime evidence before changing the design. Scenario context: A sales-risk agent uses yesterday’s analytical snapshot and recommends blocking an order that was already cleared. The fix is to use the analytical context for reasoning, then re-read the live order before any action. Avoid: - Stale context.\n- No provenance.\n- Analytics treated as transactional source.\n- Undefined business semantics.

The body is the main payload. Headers are message metadata that can be used by processing steps or adapters and may be sent onward depending on configuration. Exchange properties are internal flow context values commonly used for routing and processing and are not automatically part of the outbound message. The choice should match how the data is intended to travel through the flow.