C-CPI-2506 SAP Certified Associate Integration Developer Practice Questions

The Scheduler configuration in timer-based sender adapters (like SFTP Polling or Timer Start) provides options to define a precise schedule. You can select specific days of the week (Monday to Friday) and define multiple time ranges (e.g., 09:00 to 17:00) during which the polling should be active. This is the standard, most efficient way to meet this requirement without custom scripting.

The proxy.client.ip is the standard flow variable in API Management that holds the IP address of the client making the request to the API Proxy. The 'Assign Message' policy is the correct tool for creating, modifying, or deleting HTTP headers. By using this policy to set the 'X-Forwarded-For-Client' header to the value of {proxy.client.ip}, the requirement is fulfilled.

The Dead Message Queue (or Dead Letter Queue) is a standard messaging pattern for error handling. When a consuming application repeatedly fails to process a message (e.g., due to malformed data), the message broker will move the message to a configured DMQ after a set number of retries. This prevents the 'poison message' from blocking the processing of subsequent valid messages in the main queue and allows for later analysis and manual intervention.

Open Connectors provides a library of pre-built connectors to a wide range of non-SAP, third-party cloud applications. It abstracts the complexity of authentication (e.g., OAuth) and provides a harmonized, RESTful API with a standardized data model for each connected application. This significantly reduces the development effort needed to connect to many different SaaS providers.

The Content Enricher step enriches the entire message payload. To perform enrichment on individual sub-elements (like each product item), the standard pattern is to first use a Splitter (e.g., Iterating Splitter) to break the composite message into individual messages, one for each item. Then, the Content Enricher is used on each individual split message. Finally, a Gather step is used to reassemble the enriched individual messages back into a single composite message.

This is the correct publish-subscribe pattern. Publishing to a topic allows multiple, independent consumers. The auditing application subscribes via a queue to ensure message persistence and guaranteed, exactly-once delivery (with QoS 1). The market data application subscribes directly to the topic with QoS 0 (at-most-once delivery), which is suitable for its non-critical requirement.

Policies in the Preflow apply to all requests. To create an exception, the security policy must be moved out of the Preflow. By placing the 'Verify API Key' policy in the default flow (which acts as a catch-all) and creating a specific conditional flow for /public/status with no security policies, the requirement is met. The specific flow for /public/status is matched and executed, and processing continues without hitting the default flow's security policy.

The Iterating Splitter is designed for large messages, as it processes splits sequentially without loading the entire message into memory, preventing memory-related errors. The Content Enricher is the correct step to call an external service to add data to the current message (the individual order). The Gather step is used to combine the enriched messages back into a single message if required, or can be omitted if orders are sent individually after enrichment.

The core principle of a 'Clean Core' is to avoid modifications to the standard SAP code. Custom logic should be implemented as side-by-side extensions on SAP BTP or as in-app extensions using public, released APIs. Directly modifying standard ABAP programs creates dependencies that complicate upgrades and maintenance, which is precisely what the Clean Core strategy aims to prevent.