C_CPI Flashcards — Free SAP Certified Associate - Integration Developer Study Cards

Define an OAuth2 Client Credentials artifact in the runtime keystore settings and select the OAuth2 Client Credentials authentication type directly within the configuration settings of the HTTP Receiver adapter.

Configuring the OAuth2 Client Credentials credential object in the Cloud Integration Keystore and referencing it inside the HTTP Receiver adapter ensures that SAP Integration Suite automatically manages the lifecycle, caching, and concurrent request handling of access tokens securely without custom scripting. This prevents rate-limiting issues on the authorization server and optimizes overall integration performance.

Sequential Processing.

The 'Parallel Processing' option in the Splitter component allows for concurrent processing, but when strict ordering is required, you must disable it or use 'Sequential' mode. This configuration is essential for scenarios where downstream systems rely on the chronological arrival of data, such as sequencing order updates or financial ledger entries, ensuring that state-dependent operations are handled accurately without race conditions.

Enable 'Client Certificate Authentication' and upload the partner's CA certificate as a trusted certificate in the tenant's keystore.

Mutual TLS authentication in SAP Cloud Integration requires the sender adapter to be configured for client certificate authentication and the tenant keystore to trust the CA that issued the client certificate. Importing the partner's CA certificate ensures that any certificate signed by that CA is accepted, fulfilling the requirement without importing individual certificates.

Content Modifier step followed by XSLT Mapping and Router

Placing the Content Modifier first allows setting necessary headers before routing occurs. The XSLT Mapping step then transforms the payload structure accordingly. Finally, the Router step evaluates the previously established header values to direct the message flow correctly, ensuring all prerequisites are met before evaluation takes place in the route branches.

A Java keystore (JKS) containing the partner's public certificate, deployed as a Keystore artifact.

For an HTTPS sender adapter to authenticate a partner using a client certificate, the integration flow must trust the partner's certificate. This is achieved by deploying a Keystore artifact that contains the partner's public certificate. The sender adapter references this keystore to validate the client certificate during the TLS handshake. Using a keystore with your own private key is for outbound scenarios, and PGP or OAuth2 artifacts serve different security purposes.

Value Mapping artifact.

Value Mappings are stored within the Integration Package and are explicitly designed for reusability. By maintaining mapping tables in a central location, you ensure data consistency across different scenarios. This is a critical development practice because it reduces maintenance effort, minimizes errors caused by duplicate data definitions, and simplifies updates when business codes change across integrated enterprise systems.

The Message object.

The Message object is the primary interface in Groovy scripts for interacting with the current message processing context. By using methods such as getHeaders(), getProperties(), and getBody(), developers can dynamically inspect and modify the data flowing through the pipeline. Mastering this API is crucial for building flexible, reusable custom logic that goes beyond the standard capabilities offered by pre-built adapter components.

Router

The Router step is specifically designed for content-based routing in SAP Cloud Integration. It evaluates message properties or header values against defined XPath or expression conditions to direct the flow down specific branches, ensuring dynamic processing paths depending on the incoming data payload. This pattern is fundamental when building flexible integration landscapes.

HTTPS sender adapter

The HTTPS sender adapter is the correct choice because it exposes a generic HTTP endpoint that accepts arbitrary payloads such as JSON and supports synchronous request-response processing. SOAP, OData, and IDoc adapters all impose protocol-specific payload structures that the partner explicitly cannot support.

The Content Modifier set a property instead of a header, and the Router is configured to read from headers, so the value is never found.

Headers and exchange properties are separate namespaces in SAP Cloud Integration. When a Content Modifier writes to a property but a Router expression reads from a header, the lookup returns empty and the default branch is taken. Verifying and aligning the storage type in both steps resolves the issue.

Use the OData receiver adapter with Principal Propagation authentication and configure the required certificate-based trust with the Cloud Connector.

Principal propagation in Cloud Integration is implemented by the OData receiver adapter using the Principal Propagation authentication option. The runtime requests a short-lived certificate from the Cloud Connector on behalf of the logged-on user, and the backend trusts that certificate. This requires trust configuration between the tenant, Cloud Connector, and backend. Client Credentials, basic authentication, and stored credentials do not convey the actual business user identity.

Configure the HTTP receiver adapter with OAuth 2.0 Client Credentials authentication and select a Security Material of type OAuth2 Client Credentials that stores the client ID, client secret, and token service URL.

OAuth 2.0 client credentials flows require a security material that holds the client ID, client secret, and token service URL. SAP Cloud Integration provides the OAuth2 Client Credentials artifact type for exactly this purpose, and the HTTP receiver adapter uses it to fetch and cache the access token. This removes hardcoded secrets and avoids per-message token requests.

The user-defined function is not marked as a queue function, so it processes each Item context individually and resets the accumulator for every Item node.

A user-defined function that accumulates a value across multiple source contexts must be set as a queue function in the message mapping. Otherwise, the mapping runtime invokes it once per context, resetting the accumulator and producing an incorrect sum such as 0. Marking the function as a queue function ensures it is invoked once and can iterate over all Item nodes.

Use an if-else condition in the mapping expression to check for the existence of the source element before accessing it.

The correct approach is to guard the access to the optional source element with a conditional expression in the mapping. This prevents the runtime from evaluating a missing node, which would otherwise cause a null reference error. The other options either reference non-existent settings or attempt to solve the problem outside the mapping, which is not reliable for per-occurrence optional elements.

Splitter (General Splitter) with streaming enabled

The General Splitter with streaming enabled reads the CSV payload incrementally and emits one message per record, which keeps memory usage low and allows each record to be sent to the OData service separately. The other steps either transform a single message, copy the same message, or set metadata, and none of them can decompose a large file into individual messages without loading it entirely.

SFTP sender adapter and SFTP receiver adapter.

The integration flow must read files from an SFTP server and write to another SFTP server. This requires an SFTP sender adapter to poll and retrieve files from the source, and an SFTP receiver adapter to send the processed data to the target. Other adapter types like Mail, HTTPS, or OData do not support SFTP file operations, so they cannot fulfill the requirement.

Use the 'join' function with a comma as the delimiter on the repeating node.

To concatenate multiple occurrences of a repeating node into a single delimited string, the 'join' function is designed for this purpose. It takes a context and a delimiter, producing a single string with all values separated by the delimiter. Other functions like 'concat', 'split', or 'substring' do not perform this aggregation on repeating nodes, making 'join' the correct choice.

Use a one-to-many mapping with a context change and a condition check on the Status field before creating the target element.

The requirement is to conditionally create one target element per source element based on a field value. In SAP Cloud Integration Message Mapping, this is achieved with a one-to-many mapping combined with a context change to the source node and a condition check. The context change ensures the mapping operates per Order, and the condition (e.g., using the 'if' function) ensures only approved Orders produce an OrderConfirmation. Other mapping types do not support conditional element creation.