Courseiva

SAP Certified Associate - Integration Developer (C_CPI) — Questions 1–75

218 questions total · 3 pages · All types, answers revealed

Page 1 of 3

Page 2
1
MCQhard

Which security feature is specifically designed to ensure the integrity and authenticity of a message by preventing it from being altered during transit?

A.Transport Layer Security (TLS).
B.Digital Signature.
C.OAuth2 Authentication.
D.Basic Authentication.
AnswerB

A Digital Signature creates a cryptographic fingerprint of the message that is signed by the sender. The receiver uses the sender's public key to verify the signature. If any data in the message changes, the verification will fail, guaranteeing the integrity and authenticity of the transmission.

Why this answer

Message signing using digital signatures ensures both authenticity (who sent it) and integrity (it hasn't been changed). By attaching a cryptographic hash signed with a private key, the receiver can verify that the message content is unchanged. This is a fundamental security requirement for high-trust integration scenarios like B2B financial messaging or government data exchange.

Exam trap

Candidates often confuse encryption with digital signatures, assuming encryption alone guarantees integrity, forgetting that signatures specifically use private keys to verify authenticity and prevent tampering.

2
MCQhard

An integration developer is building an integration flow in SAP Cloud Integration that reads a large IDoc XML payload and must split it into individual IDoc messages before mapping each one to a JSON structure for a non-SAP receiver. The developer wants to avoid loading the entire payload into memory at once and needs each split message to retain the original message headers. Which approach is most appropriate?

A.Use a Message Mapping with a one-to-many mapping to generate multiple target messages from the single source IDoc payload.
B.Use a Multicast with parallel processing and a Content Modifier that extracts each IDoc using XPath before mapping.
C.Use an XML to JSON converter on the whole payload and then a Content Modifier to loop over the array with a Groovy script.
D.Use a General Splitter with XPath /IDOC, set the Streaming option, and enable the Splitter's ability to keep headers; then map each split message individually.
AnswerD

The General Splitter with an XPath expression targeting /IDOC creates one message per IDoc element. Enabling streaming avoids materializing the full document in memory, which matters for large payloads. Preserving headers on the split messages ensures correlation and other context survives, so downstream mapping and receiver calls can rely on them. This directly satisfies the memory and header-retention requirements.

Why this answer

For large repeating XML structures, a General Splitter with an XPath expression creates one message per matched element. Streaming the split avoids holding the entire document, and retaining headers keeps correlation context available for later steps. This combination is the standard way to process each IDoc independently and then map it to JSON for the receiver.

Exam trap

The trap here is assuming that a one-to-many Message Mapping or a Multicast can split a single payload into separate messages, when splitting is actually performed by a Splitter component.

3
MCQmedium

An integration developer is configuring a JMS receiver adapter in SAP Cloud Integration. Messages must be consumed in the exact order they were produced, and the queue must survive a tenant restart without losing messages. Which JMS queue type and configuration should be used?

A.Use a JMS queue with the default settings; ordering is not guaranteed but messages are persistent.
B.Use a JMS queue with a large message threshold and enable retry on failure; ordering is maintained by the retry mechanism.
C.Use a JMS topic with durable subscriptions; topics preserve order and persist messages across restarts.
D.Use a JMS queue configured with 'Ordered' processing and ensure the queue is persistent.
AnswerD

Configuring the JMS queue for ordered processing ensures that messages are consumed in the exact sequence they were enqueued, which is critical when business logic depends on order. Persistence guarantees that messages survive a tenant restart. This combination directly satisfies both stated requirements without introducing unnecessary complexity.

Why this answer

Ordered processing and persistence are distinct JMS queue attributes in SAP Cloud Integration. The ordered setting enforces FIFO consumption, while persistence ensures messages are not lost on restart. Selecting a queue with both attributes meets the scenario's dual requirements.

Other options either ignore ordering or rely on mechanisms that do not provide sequence guarantees.

Exam trap

The trap here is assuming that default JMS queues are always ordered or that retry logic can substitute for explicit ordering configuration.

4
MCQmedium

An integration developer is configuring a SOAP receiver adapter in SAP Cloud Integration to call an external web service. The web service requires WS-Security with a username token for authentication. Which configuration is necessary in the SOAP adapter to meet this requirement?

A.Configure the 'Authentication' tab with 'Basic' authentication and provide username and password.
B.Set the 'Message Exchange Pattern' to 'Request-Reply' and add a username token in the message body.
C.Use the 'OAuth 2.0' authentication option and configure a client credentials grant.
D.Enable the 'Use WS-Security' option and select 'Username Token' as the security type.
AnswerD

The SOAP adapter in SAP Cloud Integration provides a 'Use WS-Security' option where you can select 'Username Token' to include a username token in the SOAP header. This directly satisfies the web service's requirement for WS-Security with a username token, ensuring authentication is properly handled.

Why this answer

To satisfy the web service's requirement for WS-Security with a username token, the SOAP adapter must be configured with the 'Use WS-Security' option and 'Username Token' selected. This embeds the credentials in the SOAP header according to the WS-Security standard, ensuring the external service authenticates the request successfully.

Exam trap

The trap here is confusing WS-Security with HTTP Basic authentication or OAuth, which are different protocols and would not meet the web service's specific WS-Security requirement.

5
MCQmedium

Refer to the exhibit. You are using the XML-to-JSON converter in an integration flow. Based on the error log, what is the most appropriate action to resolve this issue?

A.Increase the message size limit in the tenant settings.
B.Use an XSLT Mapping to wrap the XML content in a single root tag.
C.Change the Content-Type header to application/xml.
D.Disable the 'Use Namespaces' option in the converter.
AnswerB

An XSLT mapping is the standard tool for transforming XML structures. By creating a parent element that encapsulates the existing multiple root nodes, the resulting XML becomes well-formed for the converter, satisfying the technical requirement for a single root element in the generated JSON output format.

Why this answer

The XML-to-JSON converter strictly requires a single root element to map the structure into a valid JSON object. When multiple root elements are present, the converter cannot determine the JSON hierarchy. Addressing this via an XSLT mapping or a Content Modifier before the conversion ensures compliance with JSON specifications, which is a common requirement when integrating between XML-based SAP systems and JSON-consuming external cloud applications.

Exam trap

Candidates often attempt to fix invalid XML structure directly in the converter settings or by using a Content Modifier to delete tags, rather than using XSLT to restructure the entire payload.

6
MCQmedium

A developer needs to read a message from an SAP Cloud Integration JMS queue and process it only if a custom header named Priority equals 'High'. The queue is shared by multiple consumers. Which approach ensures only high-priority messages are processed by this flow while others remain available for other consumers?

A.Set the JMS sender adapter's transaction type to 'None' and rely on the adapter to skip messages without the Priority header.
B.Configure the JMS sender adapter with a message selector that filters on the Priority header equal to 'High'.
C.Consume all messages from the queue and use a Router step to discard those whose Priority header is not 'High'.
D.Create a separate JMS queue for high-priority messages and modify all producers to route based on the Priority header.
AnswerB

The JMS sender adapter supports message selectors, which allow the flow to consume only messages matching a header condition. Setting the selector to Priority = 'High' ensures this flow receives only high-priority messages, while other messages stay in the queue for other consumers. This is the standard JMS filtering mechanism and avoids processing unwanted messages.

Why this answer

JMS message selectors let a consumer filter messages by header or property values at the broker level. Configuring the JMS sender adapter with a selector for Priority = 'High' means the flow only receives matching messages, while non-matching messages remain in the queue for other consumers. This satisfies both the filtering and shared-queue requirements without extra routing logic.

Exam trap

The trap here is consuming all messages and filtering in the flow, which removes non-matching messages from the queue and prevents other consumers from processing them.

7
MCQhard

An integration developer is troubleshooting an integration flow whose SFTP sender adapter intermittently processes the same file twice. The partner writes files with a temporary extension and renames them once fully uploaded. Which adapter setting should be reviewed first to prevent duplicate processing?

A.The Post-Processing setting that marks consumed files, such as moving or deleting them after successful processing
B.The Poll Interval configured on the SFTP sender channel
C.The file name pattern restriction, for example limiting reads to files ending in .done
D.The Maximum Reconnect Attempts and Retry Interval values on the SFTP channel
AnswerA

Post-processing actions such as Move, Delete, or archiving change the file's state or location after a successful read, so the same physical file no longer matches on the next poll. This is the standard mechanism for exactly-once-style consumption with the SFTP sender adapter and directly prevents the reported duplicate processing.

Why this answer

Duplicate reads occur because the adapter has no memory of previously consumed files unless post-processing changes their state. Configuring a post-processing action such as Move, Delete, or Archive after successful processing removes or relocates the file so subsequent polls cannot match it again. Poll interval, filename patterns, and reconnect settings all affect detection or connectivity, not consumption tracking, so they cannot resolve the duplication.

Exam trap

The trap here is focusing on polling frequency or filename filters, when duplicate consumption is actually controlled by what the adapter does with a file after it has been successfully read.

8
Multi-Selecthard

An integration developer must configure an integration flow in SAP Cloud Integration to process messages from a JMS queue in a reliable way. The flow must ensure that a message is only removed from the queue after successful processing, and that failed messages are retried. Which TWO configuration actions should be performed? (Choose two.)

Select 2 answers
A.Configure the receiver adapter to use a best-effort delivery mode so failures are ignored and processing continues.
B.Configure the JMS sender adapter with a transaction type that uses the queue's transactional acknowledgement so the message is committed only on success.
C.Set the JMS queue to 'auto-delete' so that messages are removed immediately after being read by the adapter.
D.Increase the JMS queue's maximum message size so large payloads are not rejected during processing.
E.Enable the retry settings on the JMS sender adapter so that transient failures cause the message to be redelivered according to the configured backoff.
AnswersB, E

A transactional JMS sender ties message acknowledgement to the completion of the flow. The message remains on the queue and is only committed when processing succeeds, which guarantees it is not lost if a downstream step fails, directly satisfying the reliability requirement.

Why this answer

Reliable JMS consumption requires transactional acknowledgement so the message is committed only after successful processing, plus retry settings so transient failures trigger redelivery. Auto-delete, best-effort delivery, and size limits address different concerns and either cause message loss or have no bearing on acknowledgement and retry behavior.

Exam trap

The trap here is treating queue size or auto-delete as reliability controls, when acknowledgement semantics and retry configuration are what actually prevent message loss.

9
MCQeasy

An integration developer needs to store a reusable set of credentials that will be used by multiple integration flows in SAP Cloud Integration. The credentials must be encrypted and accessible only to the integration flows that require them. Which artifact should the developer create?

A.A Keystore artifact in the Security Material section of the tenant.
B.A Data Store artifact in the Monitor section of the tenant.
C.A Number Range artifact in the Security Material section of the tenant.
D.A User Credentials artifact in the Security Material section of the tenant.
AnswerD

User Credentials is a security artifact in SAP Cloud Integration that stores a username and password pair in encrypted form. It can be referenced by multiple integration flows, and access is controlled through role-based permissions. This is the standard way to securely store reusable credentials for adapters such as SFTP, HTTPS, and Mail, matching the requirement.

Why this answer

User Credentials is the correct security artifact for storing encrypted username-password pairs that can be reused across multiple integration flows. It is managed under Security Material, supports role-based access, and is referenced by adapters that require basic authentication. Keystores, Data Stores, and Number Ranges serve entirely different purposes and cannot fulfill this requirement.

Exam trap

The trap here is confusing a Keystore with User Credentials because both reside under Security Material and both are encrypted.

10
MCQhard

An integration developer is troubleshooting a failed message processing in SAP Cloud Integration. The integration flow uses a Groovy script to set a property named 'customerId' from the message body. The script throws a NullPointerException when the body is empty. The developer wants to ensure that the property is set to a default value if the body is empty, without causing the flow to fail. Which approach should be used in the Groovy script?

A.Use the message.getBody(InputStream.class) method and read the stream without null checks.
B.Configure a Content Modifier step before the script to set a default body if empty.
C.Wrap the property assignment in a try-catch block and ignore the exception.
D.Use the message.getBody(String.class) method and check for null before assigning.
AnswerD

Using message.getBody(String.class) and checking for null allows the script to handle an empty body gracefully. If the body is null, the script can assign a default value to the property, preventing the NullPointerException. This approach ensures the integration flow continues without failure, which is the desired outcome.

Why this answer

The Groovy script should explicitly check if the message body is null before attempting to extract the customer ID. Using message.getBody(String.class) returns null for an empty body, allowing the script to assign a default value. This prevents the NullPointerException and ensures the property is always set, maintaining flow stability.

Exam trap

The trap here is thinking that a try-catch block alone solves the problem, but it does not set a default value, leaving the property unset and causing downstream issues.

11
MCQmedium

An integration developer needs to configure a scenario where SAP Cloud Integration sends messages to an SAP S/4HANA Cloud system using the OData protocol. The developer must ensure that the connection uses the tenant's own credentials and that the OData service is called with the correct HTTP method for creating a new entity. Which receiver adapter and HTTP method should be used?

A.SOAP receiver adapter with HTTP method POST
B.OData V2 receiver adapter with HTTP method PUT
C.OData V2 receiver adapter with HTTP method POST
D.HTTP receiver adapter with HTTP method GET
AnswerC

The OData V2 receiver adapter is designed to connect to OData services, including those in SAP S/4HANA Cloud. To create a new entity, the HTTP POST method is used, as defined by the OData protocol. The adapter allows configuration of authentication, such as using tenant credentials via a credential alias.

Why this answer

The OData V2 receiver adapter is the correct choice for connecting to OData services in SAP S/4HANA Cloud. To create a new entity, the HTTP POST method is required as per the OData protocol. The adapter supports authentication using tenant credentials, ensuring secure and proper communication.

Exam trap

The trap here is confusing the HTTP method for creating an entity (POST) with updating (PUT) or retrieving (GET), and also assuming that a generic HTTP adapter can replace the OData adapter for OData services.

12
MCQeasy

You are developing an integration flow in SAP Cloud Integration that must transform a CSV file into XML. The CSV file has a header row and uses commas as delimiters. Which step should you use to convert the CSV content into XML?

A.Use a CSV to XML Converter step.
B.Use an XML to JSON Converter step with CSV input.
C.Use a Content Modifier step to set the body to XML.
D.Use a Message Mapping step with a CSV source structure.
AnswerA

The CSV to XML Converter step is specifically designed to transform CSV payloads into XML format. It allows configuration of delimiter, header row handling, and other parsing options. This step is the standard way to convert CSV to XML in SAP Cloud Integration, after which further mapping or processing can occur.

Why this answer

The CSV to XML Converter step is purpose-built to parse CSV content and produce XML. It handles delimiter configuration, header row recognition, and field-to-element mapping. In this scenario, using this step directly transforms the CSV file into XML, enabling subsequent mapping or routing steps to process the data as XML.

Exam trap

The trap here is assuming that Message Mapping or Content Modifier can handle CSV parsing, when a dedicated converter step is required.

13
Multi-Selecthard

You are configuring the JMS adapter in SAP Cloud Integration to consume messages from a queue. You need to ensure that messages are processed exactly once and that failed messages are not silently lost. Which two configuration actions must you take? (Choose two.)

Select 2 answers
A.Set the JMS acknowledgment mode to 'Auto' on the sender channel.
B.Set the queue to 'Non-Exclusive' so multiple consumers can compete for messages without locking.
C.Configure a dead letter queue and set a maximum redelivery count on the JMS queue.
D.Enable 'Use JMS Transaction' on the JMS sender channel so the message is acknowledged only after successful processing.
E.Disable message persistence on the JMS queue to improve performance.
AnswersC, D

A dead letter queue combined with a maximum redelivery count ensures that messages which repeatedly fail are moved to a separate queue instead of being retried indefinitely or discarded. This preserves failed messages for later inspection and prevents silent loss, which is exactly what the scenario requires.

Why this answer

Exactly-once or at-least-once delivery with no silent loss requires transactional acknowledgement tied to processing success and a safety net for repeatedly failing messages. Enabling the JMS transaction on the sender channel ensures acknowledgement occurs only after successful processing, while a dead letter queue with a redelivery limit captures messages that cannot be processed, preserving them for investigation.

Exam trap

The trap here is treating performance-oriented settings such as disabling persistence or using auto acknowledgment as harmless optimizations, when they actually break the reliability guarantees the scenario demands.

14
Multi-Selecthard

An integration developer is designing an integration flow that must call an external REST API and must handle errors so that a failed call triggers a retry and, if the retry also fails, sends an alert. Which TWO steps should the developer include in the integration flow? (Choose two.)

Select 2 answers
A.Add a Message Mapping step that transforms the error response into the request payload.
B.Configure a JMS queue to store the request and have a separate flow poll it indefinitely.
C.Add a Content Modifier that sets the HTTP status code to 200 before the call.
D.Configure the receiver channel with retry settings or wrap the call in a looping process that retries on failure.
E.Add an Exception Subprocess with an alerting step that fires when the retry attempt also fails.
AnswersD, E

To retry a failed external call, the flow needs retry logic, which can be configured on the receiver channel or implemented with a looping process that re-invokes the call when a failure is detected. This directly addresses the requirement that a failed call be retried before any alert is raised.

Why this answer

Handling a flaky external API requires retry logic, which can be configured on the receiver channel or implemented with a loop that re-invokes the call. When retries are exhausted, an Exception Subprocess catches the failure and can send an alert. Together these two steps implement the required retry-then-alert behavior, while the other options neither retry the call nor raise an alert.

Exam trap

The trap here is treating persistence or transformation steps as error handling, when only explicit retry logic plus an Exception Subprocess delivers retry and alerting behavior.

15
MCQhard

An integration developer is designing an integration flow in SAP Cloud Integration that must process incoming messages asynchronously and guarantee that messages are not lost if the tenant restarts. The developer decides to use a JMS queue as the sender. Which configuration ensures that messages are persisted and processed exactly once by the integration flow?

A.Configure the JMS sender adapter with transaction type None and rely on the default retry settings of the runtime.
B.Configure the JMS sender adapter to use a non-persistent queue and set the Maximum Retries to a high value.
C.Configure the JMS sender adapter with transaction type Exactly Once and ensure the queue is configured as a persistent queue.
D.Configure the JMS sender adapter with transaction type Best Effort and enable the Retry on Failure option in the adapter settings.
AnswerC

The Exactly Once transaction type makes the JMS sender adapter participate in a transactional unit of work, so the message is only acknowledged after the integration flow completes successfully. Combined with a persistent queue, which stores messages on disk, this ensures messages survive tenant restarts and are processed exactly once, meeting both durability and delivery guarantees required by the scenario.

Why this answer

Exactly-once processing with no message loss requires two elements: a persistent JMS queue that survives restarts, and the Exactly Once transaction type on the JMS sender adapter so acknowledgment is tied to successful flow completion. Best Effort or None transaction types acknowledge messages prematurely, and non-persistent queues lose data on restart, so only the combination of a persistent queue and Exactly Once satisfies the requirement.

Exam trap

The trap here is believing that retry settings alone provide reliability, when durability and exactly-once delivery actually depend on a persistent queue combined with the Exactly Once transaction type.

16
MCQmedium

During the development of an integration flow, you need to store temporary session variables and pass data across different local integration processes within the same message path. Which step is specifically designed for writing values to the message header or exchange properties, and how should it be used?

A.Data Store Write step, configured to persist session variables in the tenant database.
B.Content Modifier step, configured to set exchange properties for intra-flow data sharing.
C.Router step, configured with XPath expressions to extract and cache session values.
D.Groovy Script step, utilizing message.setHeader() exclusively.
AnswerB

Exchange properties configured via the Content Modifier step exist solely within the scope of the current message exchange. They allow seamless data passing between local integration processes and router branches without incurring database storage costs.

Why this answer

The Content Modifier step provides dedicated capabilities to modify message headers and exchange properties, making it the standard tool for managing session-like variables. Using exchange properties ensures that data remains available throughout the current message processing lifecycle across local integration boundaries.

Exam trap

Candidates often confuse 'Message Headers' with 'Exchange Properties,' assuming they are interchangeable, which leads to failures when data needs to persist across local integration processes that clear message headers.

17
MCQmedium

An integration developer is configuring a Message Mapping in SAP Cloud Integration. The target structure requires an element named CustomerSegment that must be populated from a source field called Tier, but the mapping must also preserve any whitespace-insensitive value and strip surrounding spaces before assignment. Which step should the developer add in the mapping to achieve this?

A.Use a Content Modifier step before the mapping to set a property with the trimmed value.
B.Configure a Groovy script step after the mapping that removes whitespace from the target payload.
C.Add an ifWithoutElse standard function and map Tier directly to CustomerSegment.
D.Add a standard function and select trim before assigning the source field to the target element.
AnswerD

The trim standard function removes leading and trailing whitespace from a string value during message mapping. Applying it between the source Tier field and the target CustomerSegment element ensures the assigned value is normalized without altering internal characters, which satisfies the requirement to strip surrounding spaces while preserving the value's core content.

Why this answer

The trim standard function is the purpose-built mapping function for removing leading and trailing whitespace from a string. Applying it to the Tier source field before it is assigned to CustomerSegment normalizes the value exactly as required. Other approaches either do not target the field, operate outside the mapping context, or unnecessarily post-process the entire message.

Exam trap

The trap here is assuming that any string-handling step applied near the mapping will automatically affect the specific field, when only functions wired directly between source and target fields normalize that value.

18
Multi-Selectmedium

An integration developer is configuring a SOAP receiver adapter in SAP Cloud Integration to call an external SOAP service that requires WS-Security UsernameToken authentication. The developer must also ensure the message is signed. Which TWO actions must be performed to meet these requirements? (Choose two.)

Select 2 answers
A.Enable the WS-Security signing option in the SOAP receiver adapter and configure the keystore alias for the signing key.
B.Create a PGP key pair in the tenant keystore and reference it in the SOAP receiver adapter's encryption settings.
C.Add a Message Mapping step that inserts a UsernameToken element into the SOAP header before the receiver call.
D.Set the SOAP adapter's message exchange pattern to one-way and add a digital signature to the payload using a Groovy script.
E.Configure the SOAP receiver adapter with the WS-Security UsernameToken authentication option and provide the user credentials in a secure parameter.
AnswersA, E

The SOAP receiver adapter includes WS-Security settings where signing can be enabled. You must specify the keystore alias containing the private key and certificate used to sign the message. This ensures the SOAP message is signed as required by the external service.

Why this answer

Meeting both WS-Security UsernameToken authentication and message signing requires configuring the SOAP receiver adapter's WS-Security authentication option with secure credentials, and enabling the signing option with a keystore alias. These adapter settings generate the correct SOAP security headers and XML signature that the external service validates.

Exam trap

The trap here is believing a Message Mapping or Groovy script can produce valid WS-Security headers, when only the SOAP receiver adapter's WS-Security settings generate the correct UsernameToken and XML signature.

19
MCQeasy

An integration developer needs to create a reusable script that can be called from multiple integration flows in SAP Cloud Integration. The script must be version-controlled and accessible across the tenant. Which artifact should the developer use?

A.A Value Mapping artifact
B.A Message Mapping artifact
C.A Script Collection
D.An Integration Flow with a Script step
AnswerC

A Script Collection is a dedicated artifact in SAP Cloud Integration for storing reusable scripts (JavaScript or Groovy) that can be referenced from multiple integration flows. It supports versioning and is accessible tenant-wide. This is the correct choice for sharing scripts across flows without duplicating code, ensuring maintainability and consistency.

Why this answer

The Script Collection is the designated artifact for storing reusable scripts in SAP Cloud Integration. It allows developers to maintain a single version of a script and reference it from any integration flow, promoting code reuse and easier maintenance. Message Mapping, Integration Flow, and Value Mapping artifacts serve different purposes and do not provide a centralized script repository.

Exam trap

The trap here is confusing artifacts that can contain scripts (like an Integration Flow with a Script step) with the dedicated artifact designed for reusable script storage, which is the Script Collection.

20
MCQhard

An integration developer is configuring a SOAP receiver adapter in SAP Cloud Integration to call an external web service that requires WS-Security UsernameToken with a password digest. The developer has configured the adapter with the correct alias for the private key and the user credentials. During testing, the external service rejects the request with a security fault stating that the digest is invalid. What is the most likely cause?

A.The external service expects the digest to be computed using SHA-256, but SAP Cloud Integration always uses SHA-1 for UsernameToken digests.
B.The password stored in the security material contains a trailing space or special character that does not match the password expected by the external service.
C.The SOAP adapter was configured with the WS-Security option 'Sign and Encrypt' instead of 'Username Token', so the digest was not generated correctly.
D.The SOAP adapter does not support WS-Security UsernameToken with password digest and only supports plain text passwords.
AnswerB

WS-Security UsernameToken with password digest is computed from the password, nonce, and timestamp. If the stored password differs even by a trailing space or an incorrectly escaped special character, the digest will not match the one computed by the external service, causing the security fault about an invalid digest.

Why this answer

WS-Security UsernameToken password digest is a hash over the password, nonce, and timestamp. Any discrepancy in the stored password, including invisible characters or incorrect escaping, changes the digest and triggers an invalid digest fault. Verifying the exact password in the security material and ensuring it matches the external service expectation resolves the issue.

Exam trap

The trap here is assuming that a digest error is caused by an unsupported algorithm or wrong security policy, when it is often a simple credential mismatch such as a trailing space.

21
MCQeasy

You need to configure an integration flow in SAP Cloud Integration to receive messages from an external partner via HTTPS. The partner will send messages to a specific endpoint and expects a synchronous response. Which sender adapter should you use?

A.SOAP sender adapter
B.HTTPS sender adapter
C.IDoc sender adapter
D.OData sender adapter
AnswerB

The HTTPS sender adapter in SAP Cloud Integration is designed to accept incoming HTTP/HTTPS requests from external systems. It supports synchronous request-response patterns, allowing the integration flow to process the request and return a response to the caller. This matches the requirement of receiving messages from a partner and providing a synchronous response, making it the correct adapter for this scenario.

Why this answer

The HTTPS sender adapter is the correct choice for receiving messages from an external partner over HTTPS with a synchronous response. It supports standard HTTP methods and can be configured with authentication and endpoint settings. Other sender adapters are protocol-specific and do not match the plain HTTPS requirement.

Exam trap

The trap here is confusing HTTPS with SOAP or OData, assuming that any HTTP-based protocol requires a specialized adapter.

22
MCQmedium

A developer is building an integration flow that calls an external system using the HTTP receiver adapter. The external system requires that a custom header named X-Correlation-ID be sent with each request. The value must come from a property set earlier in the flow. Where should the header be defined so it is sent on the outbound request?

A.In a Content Modifier step placed after the receiver adapter, setting the header on the message.
B.In the HTTP receiver adapter's 'Custom Headers' section, referencing the property with an expression such as ${property.correlationId}.
C.In the sender adapter configuration, adding the header to the inbound request handling.
D.In the integration flow's runtime configuration artifact, declaring the header as an externalized parameter.
AnswerB

The HTTP receiver adapter provides a Custom Headers table where you can define header names and values using expression language. Referencing the property with ${property.correlationId} resolves the value at runtime and attaches it to the outbound request, which is exactly what the external system requires.

Why this answer

Outbound HTTP headers are controlled at the receiver adapter, which offers a Custom Headers table that accepts expression-language values. Referencing the property there ensures the value is resolved and sent. Content Modifier placement, sender adapter settings, and externalized parameters all operate at the wrong layer or timing to affect the outbound request headers.

Exam trap

The trap here is assuming a Content Modifier before the receiver automatically forwards headers, when the HTTP receiver adapter only sends headers explicitly declared in its Custom Headers table.

23
MCQmedium

An integration developer is creating an integration flow in SAP Cloud Integration that receives an IDoc from SAP S/4HANA and must transform it into a JSON structure for a third-party logistics provider. The developer has already imported the IDoc XSD into the integration flow's resources. Which mapping approach should be used to convert the IDoc XML into the target JSON?

A.A Message Mapping followed by an XML-to-JSON converter step
B.An XML-to-JSON converter applied directly to the raw IDoc payload
C.A Message Mapping whose target is defined by a JSON schema artifact
D.A single XSLT mapping that outputs JSON directly as text
AnswerA

The IDoc arrives as XML conforming to the imported XSD, so a Message Mapping can graphically transform it into an intermediate XML structure that matches the desired JSON hierarchy. An XML-to-JSON converter then serializes that XML into JSON for the logistics provider. This two-step approach keeps the structural transformation explicit and testable while letting the converter handle serialization syntax.

Why this answer

Converting an IDoc into a partner-specific JSON document involves two distinct concerns: reshaping the IDoc hierarchy into the target structure, and serializing XML into JSON syntax. A Message Mapping handles the structural transformation using the imported IDoc XSD, producing intermediate XML that reflects the desired layout, and the XML-to-JSON converter then emits valid JSON. Mapping straight to JSON, or converting the raw IDoc without restructuring, does not produce the contracted format.

Exam trap

The trap here is believing the XML-to-JSON converter also restructures field names and hierarchy, when it only changes the serialization syntax.

24
MCQmedium

When designing an iFlow that connects to an external OData API, which step is necessary to ensure that the integration flow handles large data sets efficiently using pagination?

A.Increase the timeout value in the HTTP adapter.
B.Use the OData adapter's pagination support features.
C.Convert the payload to binary format.
D.Disable logging for the OData call.
AnswerB

The OData adapter provides native support for server-side pagination. By enabling this, the integration flow makes multiple sequential calls to retrieve data in segments, which keeps the payload size within manageable limits for the memory heap, ensuring a stable and performant execution of the data extraction process.

Why this answer

Pagination is critical for avoiding memory issues when processing large datasets. By configuring the OData adapter to use 'top' and 'skip' parameters, or by using the built-in pagination support, the iFlow retrieves data in chunks. This is vital because it prevents the runtime from attempting to load millions of records into RAM simultaneously, which would cause an OutOfMemoryError and crash the integration node.

Exam trap

Many candidates incorrectly believe that increasing the JVM heap size or writing custom Groovy scripts to load entire datasets is the standard solution for handling large OData payloads.

25
MCQeasy

An integration developer is using the XML-to-JSON converter in SAP Cloud Integration to transform an incoming XML message. The XML contains an attribute 'currency' on the 'price' element. After conversion, where will this attribute appear in the resulting JSON?

A.As a JSON property named 'currency' nested within the 'price' object, without any prefix.
B.As a JSON property named '_currency' nested within the 'price' object.
C.As a JSON property named 'currency' at the same level as 'price'.
D.As a JSON property named '@currency' nested within the 'price' object.
AnswerD

The XML-to-JSON converter in SAP Cloud Integration follows a convention where XML attributes are represented as JSON properties prefixed with '@'. For an attribute 'currency' on element 'price', the resulting JSON will have a 'price' object containing a property '@currency'. This preserves the attribute's association with its element and is the standard behavior.

Why this answer

The XML-to-JSON converter in SAP Cloud Integration represents XML attributes as JSON properties prefixed with '@'. Therefore, an attribute 'currency' on the 'price' element becomes '@currency' within the 'price' object. This convention ensures attributes are distinct from child elements and maintains the hierarchical relationship.

Other prefixes or placements would not conform to the converter's standard behavior.

Exam trap

The trap here is assuming that XML attributes become regular JSON properties without any special notation, when in fact the converter uses the '@' prefix to denote attributes.

26
MCQeasy

An integration developer must expose an integration flow in SAP Cloud Integration as an HTTPS endpoint that an external partner will call synchronously. The partner will authenticate using a client certificate (mutual TLS). Which configuration must the developer perform on the HTTPS sender adapter to accept and validate the partner's client certificate?

A.Deploy the partner's client certificate as a 'User Credentials' security artifact and select it in the sender adapter.
B.Set the sender adapter's Authorization to 'User Role' and assign the partner's user to the ESBMessaging.send role.
C.Set the sender adapter's Authorization to 'Client Certificate' and reference a deployed Keystore artifact containing the partner's trusted root certificate.
D.Enable 'Allow Public Access' on the sender adapter and rely on IP allowlisting for authentication.
AnswerC

The HTTPS sender adapter supports client certificate authentication. Selecting 'Client Certificate' as the authorization method and referencing a Keystore artifact that contains the partner's trusted root or issuing certificate enables the tenant to validate the certificate presented during the TLS handshake. This is the standard configuration for mutual TLS on an inbound HTTPS endpoint in Cloud Integration.

Why this answer

Mutual TLS on an inbound HTTPS endpoint in Cloud Integration requires selecting Client Certificate authorization on the HTTPS sender adapter and referencing a Keystore artifact that holds the partner's trusted certificate chain. User Role authorization, User Credentials artifacts, and public access with IP allowlisting all fail to perform certificate-based client authentication, so only the Keystore-backed client certificate configuration meets the requirement.

Exam trap

The trap here is confusing inbound client certificate authentication with outbound credential types, such as User Credentials, which cannot store certificates or establish mutual TLS trust.

27
MCQhard

You are configuring a SOAP receiver adapter in SAP Cloud Integration to call an external web service that requires WS-Security UsernameToken with a password digest. The external service also expects the timestamp to be included, and the digest must use SHA-256. Which configuration steps must you perform in the receiver adapter?

A.Enable WS-Security, select 'SAML Token' as the security token, and configure the SAML issuer and subject.
B.Enable WS-Security, select 'X.509 Token' as the security token, and configure the keystore alias for the private key.
C.Enable WS-Security, select 'Username Token' as the security token, and set the password digest algorithm to SHA-1, then add a Content Modifier to insert the Timestamp manually.
D.Enable WS-Security, select 'Username Token' as the security token, set the password digest algorithm to SHA-256, and enable 'Include Timestamp'.
AnswerD

The SOAP receiver adapter's WS-Security configuration allows you to select Username Token, choose the digest algorithm (SHA-256), and include a timestamp. These settings generate the correct WS-Security header with a password digest computed using SHA-256 and a Timestamp element, exactly matching the external service's requirements.

Why this answer

The SOAP receiver adapter's WS-Security settings must match the external service's policy. Selecting Username Token with SHA-256 digest and enabling the timestamp creates the correct WS-Security header. Other token types such as X.509 or SAML would not satisfy the UsernameToken requirement, and SHA-1 would fail the digest algorithm constraint.

Exam trap

The trap here is assuming that any WS-Security token type can be used interchangeably, when the external service's policy strictly demands UsernameToken with SHA-256 and a timestamp.

28
MCQeasy

An integration developer is configuring a SOAP sender adapter in SAP Cloud Integration. The external partner's SOAP client sends a WS-Security UsernameToken header. The developer must validate the incoming credentials against a credential stored in the tenant's Security Material. Which adapter configuration achieves this without writing custom scripts?

A.Set the SOAP sender adapter's Authorization to 'User Role' and map the incoming token to an OAuth client.
B.Set the SOAP sender adapter's Authorization to 'WS-Security Username Token' and select the deployed User Credentials artifact.
C.Enable 'Principal Propagation' on the SOAP sender adapter and trust the partner's IdP certificate.
D.Configure the SOAP sender adapter with 'Client Certificate' authorization and import the partner's public key into the Keystore.
AnswerB

The SOAP sender adapter exposes a WS-Security Username Token authorization mode that validates the incoming UsernameToken against a User Credentials artifact stored in Security Material. Selecting the deployed artifact binds the flow to the stored username and password, so validation happens at the adapter without a script step.

Why this answer

The SOAP sender adapter offers a WS-Security Username Token authorization mode that validates inbound UsernameToken credentials against a User Credentials artifact in Security Material. Selecting that artifact keeps validation at the adapter layer, requiring no Groovy or XSLT script, and ensures only partners presenting the stored credentials can invoke the flow.

Exam trap

The trap here is assuming any inbound SOAP credential is validated by the generic Authorization setting rather than the dedicated WS-Security Username Token mode bound to a Security Material artifact.

29
Multi-Selectmedium

An integration developer needs to make an integration flow's processing logic reusable across multiple flows in the same SAP Cloud Integration tenant. The logic consists of a mapping step and a Groovy script that must be maintained in one place. Which TWO artifacts should the developer create to achieve this? (Choose two.)

Select 2 answers
A.A Script Collection artifact containing the Groovy script
B.A Message Mapping artifact containing the reusable mapping
C.An OData API artifact exposing the mapping as a service
D.A Partner Directory entry storing the script as a binary parameter
E.A Value Mapping artifact containing the target field values
AnswersA, B

A Script Collection artifact stores Groovy or JavaScript resources that can be imported into multiple integration flows. Placing the Groovy script here allows the developer to maintain it in one place and reference it from each flow, which meets the requirement for reusable script logic with a single point of maintenance.

Why this answer

Reusable processing logic in SAP Cloud Integration is achieved by separating the mapping definition and the script into their own artifacts. A Message Mapping artifact centralises the structural transformation, and a Script Collection artifact centralises the Groovy code. Both can be referenced from multiple integration flows, so the logic is maintained in one place and consumed everywhere it is needed.

Exam trap

The trap here is treating the Partner Directory or a Value Mapping as a general-purpose repository for executable logic, when only dedicated mapping and script artifacts provide proper reuse.

30
MCQmedium

An integration developer needs to create a script that reads a custom header named 'Country' from the incoming message and sets a property named 'CountryCode' based on a mapping. The script must be written in Groovy and run in SAP Cloud Integration. Which code snippet correctly retrieves the header and sets the property?

A.def country = message.getProperty("Country"); message.setHeader("CountryCode", country);
B.def country = message.headers["Country"]; message.properties["CountryCode"] = country;
C.def country = message.getHeaders().get("Country"); message.setProperty("CountryCode", country);
D.def country = message.getHeader("Country"); message.setProperty("CountryCode", country);
AnswerD

This snippet uses the correct methods: getHeader to retrieve the header value and setProperty to set a property. In SAP Cloud Integration Groovy scripts, the message object provides getHeader and setProperty methods. This is the standard way to access and set message attributes within a script step.

Why this answer

The correct Groovy script must use the message object's getHeader method to read the 'Country' header and setProperty to create the 'CountryCode' property. The other options use incorrect method names, bracket notation that is not supported, or swap header and property operations. Only the snippet using getHeader and setProperty performs the required actions.

Exam trap

The trap here is assuming that headers and properties can be accessed like Groovy maps or that method names are interchangeable, when the SAP Cloud Integration message API requires specific methods like getHeader and setProperty.

31
MCQhard

An integration developer deploys an integration flow with an HTTPS sender adapter. The flow must expose two different operations, one for creating sales orders and one for querying them, distinguished by the URL path. The developer wants both operations handled within a single integration flow. Which approach is most appropriate?

A.Create a single integration flow with an HTTPS sender adapter and use a Content Modifier to set a header named Operation based on the HTTP method, then route on that header.
B.Configure a single HTTPS sender adapter with a specific address, then use a Router step that evaluates the camelHttpPath header to branch to the appropriate subprocess.
C.Configure two separate HTTPS sender adapter channels, each with a different address, and deploy the integration flow twice with different endpoints.
D.Use a single HTTPS sender adapter with the address set to a wildcard, then use a Router step with XPath conditions on the request payload to branch to the appropriate subprocess.
AnswerB

A single sender adapter can receive all requests, and the integration flow can inspect the camelHttpPath header, which contains the incoming URL path. A Router step with conditions on that header directs each request to the correct subprocess. This keeps both operations in one deployable artifact and cleanly separates them by path, exactly as the scenario requires.

Why this answer

The incoming URL path is available at runtime as the camelHttpPath header, so a single sender adapter can serve multiple operations. A Router step evaluating that header directs each request to the correct branch within one integration flow. This satisfies the requirement of a single deployable artifact while cleanly separating the create and query operations by their distinct paths.

Exam trap

The trap here is assuming that differentiating operations requires multiple sender adapters or deployments, when the URL path is already exposed as a runtime header.

32
MCQeasy

Where is the best place to configure and store the public keys of target systems that require message signing or encryption?

A.In the Integration Flow properties file.
B.In the Keystore.
C.In the Message Mapping editor.
D.In the Content Modifier component.
AnswerB

The Keystore is the dedicated secure storage for all cryptographic keys and certificates in SAP Integration Suite. It provides a secure environment for managing public keys, ensuring that they can be referenced by adapters for encryption and signature verification tasks in a compliant and secure manner.

Why this answer

The Keystore in the Integration Suite is the centralized location for managing cryptographic artifacts, including public/private key pairs and certificates. Storing public keys here is essential for establishing secure communication, as it enables the platform to verify digital signatures and encrypt outgoing payloads according to the target system's security requirements, ensuring the confidentiality and integrity of sensitive enterprise data.

Exam trap

Candidates often assume target public keys should be stored directly in adapter parameters or Value Mappings, rather than recognizing the Keystore as the mandatory centralized repository.

33
MCQmedium

An integration developer is building an integration flow in SAP Cloud Integration that processes incoming XML payloads. The integration flow must validate the XML against an XML Schema Definition (XSD) before routing the message. Which component should the developer configure to perform this structural validation?

A.Content Modifier step configured with an XML validation rule set
B.Message Router configured with an XPath expression check
C.XML Validator integration flow step referencing an XSD resource
D.Script step utilizing standard Java string matching functions
AnswerC

The XML Validator step directly accepts an XSD schema resource from the resources tab and evaluates the incoming message body. It throws an exception if the XML structure violates the defined schema rules, halting execution early.

Why this answer

The XML Validator is specifically designed in SAP Cloud Integration to check incoming message payloads against a provided XSD schema. This ensures structural integrity before any mapping or backend processing occurs, saving valuable system resources and preventing malformed data propagation.

Exam trap

Candidates often mistake the XML Validator for the Content Modifier or XML Modifier, assuming data transformation tools handle schema validation automatically as part of their routine parsing operations.

34
MCQmedium

An integration developer is building an integration flow that must expose an HTTPS endpoint to a partner. The partner requires mutual TLS, and the developer needs to validate the partner's client certificate against a specific trust store. Which configuration should the developer apply on the HTTPS sender adapter?

A.Set the sender adapter to use Client Certificate authentication and select the trust store containing the partner's root CA.
B.Set the sender adapter to use OAuth2 Client Credentials and register the partner as an OAuth client.
C.Set the sender adapter to use Basic authentication and store the partner's credentials in a User Credentials artifact.
D.Set the sender adapter to use Role-Based authentication and assign the partner a role in the tenant.
AnswerA

Mutual TLS requires the server side to validate the client certificate presented by the partner. Configuring Client Certificate authentication on the HTTPS sender adapter and pointing it to the trust store that holds the issuing root CA enables that validation, which directly satisfies the mutual TLS requirement.

Why this answer

Mutual TLS means both sides present certificates and each validates the other. On an HTTPS sender adapter, selecting Client Certificate authentication and referencing the trust store that contains the partner's issuing root CA enables the tenant to validate the incoming client certificate. The other authentication modes rely on credentials or tokens and do not perform certificate chain validation.

Exam trap

The trap here is equating any secure authentication option with mutual TLS, when only client certificate authentication actually validates the partner's X.509 certificate chain.

35
MCQeasy

An integration developer needs to expose a Cloud Integration flow so that an external partner can invoke it synchronously over HTTPS with a JSON payload. The partner will authenticate using a client certificate. Which adapter type and authentication option should the developer configure?

A.A SOAP sender adapter with WS-Security Username Token authentication.
B.An OData sender adapter with OAuth 2.0 client credentials and a scope check.
C.An SFTP sender adapter with public key authentication and a polling schedule.
D.An HTTPS sender adapter with Client Certificate authentication and a dedicated user mapped to the partner's certificate.
AnswerD

The HTTPS sender adapter accepts inbound synchronous calls, and Client Certificate authentication validates the partner's certificate against a configured user mapping. This matches the requirement for certificate-based authentication over HTTPS. It is the standard way to expose a flow for synchronous partner invocation with mutual TLS, ensuring only holders of the trusted certificate can call the endpoint.

Why this answer

Exposing a flow for synchronous HTTPS invocation by an external partner with certificate-based authentication requires the HTTPS sender adapter configured for Client Certificate authentication. The partner's certificate is mapped to a user, and the adapter validates it on each call. Other sender adapters either poll for files, expose specific protocols like OData or SOAP, or use different authentication schemes, so none matches the JSON-over-HTTPS with client certificate requirement.

Exam trap

The trap here is selecting an adapter based on the authentication method alone, when the adapter type must first match the synchronous HTTPS JSON invocation pattern.

36
MCQeasy

An integration developer needs to store a reusable set of mapping rules that translate country codes to country names. These rules will be referenced by multiple integration flows. Which artifact in SAP Integration Suite should be used to define and store these reusable mappings?

A.A Partner Directory entry in the Integration Suite
B.A Message Mapping artifact in the Integration Flow editor
C.A Script Collection artifact in the Integration Suite
D.A Value Mapping artifact in the Integration Suite
AnswerD

Value Mapping is a dedicated artifact in SAP Integration Suite that stores reusable mappings, such as country code to country name. It can be referenced by multiple integration flows, ensuring consistency and reducing duplication. This is exactly the artifact designed for storing and sharing mapping rules across flows, making it the correct choice for this scenario.

Why this answer

Value Mapping is the artifact in SAP Integration Suite specifically designed to store reusable mapping rules, such as code-to-name translations, that can be referenced across multiple integration flows. It provides a central place to manage mappings and ensures consistency. Message Mapping is flow-specific, Script Collection stores scripts, and Partner Directory is for partner configuration, so none of these serve the requirement as directly as Value Mapping.

Exam trap

The trap here is confusing Value Mapping with Message Mapping, where only Value Mapping provides a centrally reusable mapping artifact.

37
MCQhard

An integration developer is configuring an integration flow that receives messages from an HTTPS sender adapter. The flow must ensure that messages are processed exactly once, even if the sender retries due to a timeout. Which feature should be configured to achieve this?

A.Enable the 'Duplicate Message Detection' option in the HTTPS sender adapter
B.Set the 'Retry' option to zero on the HTTPS sender adapter
C.Use the Idempotent Process Call step with a message ID derived from the incoming request
D.Configure the JMS sender adapter with exactly-once quality of service
AnswerC

The Idempotent Process Call step in SAP Cloud Integration ensures that a message is processed only once based on a unique message ID. By deriving the ID from the incoming request, such as a business key or a header, the step can detect and discard duplicate messages. This provides exactly-once processing semantics even if the sender retries, making it the correct solution for this scenario.

Why this answer

Exactly-once processing in SAP Cloud Integration is achieved through idempotency. The Idempotent Process Call step uses a unique message ID to detect and skip duplicates. By deriving this ID from the incoming HTTPS request, the flow ensures that retries do not result in duplicate processing.

Other options either do not apply to the HTTPS sender or do not provide idempotency, so they fail to meet the requirement.

Exam trap

The trap here is assuming that retry settings or duplicate detection options on the sender adapter provide exactly-once processing, when idempotency must be explicitly implemented.

38
MCQhard

An integration developer has an integration flow that uses a Splitter step to split a large XML message into individual records. Each record must be processed by a subsequent mapping and then sent to an SFTP server. The developer notices that the SFTP server receives all records but they are concatenated into a single file. What is the most likely cause?

A.The Splitter step is configured with 'Parallel Processing' enabled, causing messages to be merged before the SFTP adapter.
B.The SFTP adapter's 'Append' option is enabled, causing each new record to be appended to the existing file on the server.
C.The integration flow uses a Gather step after the Splitter, which combines the split messages back into a single message before the SFTP adapter.
D.The SFTP adapter is configured with 'Batch' mode and 'Group by' settings that combine multiple messages into one file.
AnswerC

The Gather step is designed to collect multiple messages from a split and merge them into a single message. If a Gather step is placed after the Splitter and before the SFTP adapter, the individual records will be concatenated into one payload, resulting in a single file on the SFTP server. Removing the Gather step or placing it after the SFTP call would resolve the issue.

Why this answer

A Gather step after a Splitter collects all split messages and merges them into one message. If this combined message is sent to the SFTP adapter, the server receives a single file containing all records concatenated. To send each record as a separate file, the Gather step must be removed or the SFTP call must be placed before any gathering step.

Exam trap

The trap here is overlooking the Gather step, which is specifically designed to recombine split messages, and instead blaming the SFTP adapter or Splitter settings.

39
MCQeasy

During the development of an integration flow in SAP Integration Suite, an integration developer needs to temporarily store a sensitive authentication token in memory across different steps within the same message processing thread, without persisting it to a database. Which feature should the developer use to store this temporary variable?

A.Global Variables stored within the Tenant Management Node persistence layer.
B.Exchange Properties managed via the Content Modifier step.
C.Data Store Operations with an automated retention period of zero seconds.
D.Inbound SOAP Header variables automatically mapped to system environment parameters.
AnswerB

Exchange properties provide an in-memory storage mechanism accessible exclusively within the context of the current message exchange. Utilizing a Content Modifier to set and retrieve exchange properties allows developers to manage contextual variables efficiently without incurring persistence performance penalties.

Why this answer

Exchange properties are specifically designed to store temporary, contextual data objects in memory throughout the lifecycle of a single message processing thread. Unlike global variables or persistent data stores, exchange properties are automatically garbage-collected once message processing completes, ensuring high performance and security compliance.

Exam trap

Many candidates confuse Exchange Properties with Headers or Global Variables. They fail to realize that headers are often passed to the receiver system, whereas properties are strictly for internal flow context.

40
Multi-Selectmedium

An integration developer needs to configure the Cloud Connector to enable secure connectivity between SAP Cloud Integration and an on-premise system. Which TWO actions must be performed? (Choose two.)

Select 2 answers
A.Configure the SAP Cloud Integration tenant to use the Cloud Connector's location ID.
B.Add the on-premise system as an accessible resource in the Cloud Connector.
C.Install and configure the Cloud Connector on a host in the on-premise network.
D.Create a destination in SAP BTP Cockpit that points to the on-premise system.
E.Deploy a connectivity proxy in the SAP BTP subaccount.
AnswersB, C

In the Cloud Connector administration UI, you must define which on-premise systems and resources (such as HTTP services or RFC functions) are accessible from the cloud. This involves specifying the virtual host and port mapping. Without this step, the cloud cannot reach the on-premise system, making it essential for connectivity.

Why this answer

To enable secure connectivity via Cloud Connector, you must install and configure it on-premise and then add the on-premise systems as accessible resources. These two steps establish the secure tunnel and define what can be accessed. Other actions like destinations or location IDs are part of the broader setup but are not direct Cloud Connector configuration tasks.

Exam trap

The trap here is confusing the Cloud Connector configuration with the destination configuration in SAP BTP, which are separate steps.

41
MCQmedium

An integration developer is configuring an integration flow in SAP Cloud Integration that must transform an incoming XML payload into a flat-file CSV format for a legacy system. The developer needs to define the structure of the target CSV file within the integration flow. Which step type should be used to define the target CSV structure?

A.XSLT Mapping step
B.Content Modifier step
C.XML to CSV Converter step
D.Message Mapping step
AnswerC

The XML to CSV Converter step in SAP Cloud Integration allows you to define the target CSV structure by specifying field names, delimiters, and other formatting options. It converts XML to CSV based on a configured schema, which exactly matches the requirement to define the target CSV structure for the legacy system.

Why this answer

The XML to CSV Converter step is specifically designed to transform XML messages into CSV format while allowing the developer to define the target structure, including field names and delimiters. This step ensures the output conforms to the legacy system's expected CSV layout, making it the correct choice for this integration flow.

Exam trap

The trap here is assuming that any mapping step can define a CSV structure, but only the XML to CSV Converter provides the necessary configuration for flat-file output.

42
MCQeasy

An integration developer needs to retrieve a value from a message header and use it to set a property in a subsequent step of an integration flow. Which step should be used to extract the header value?

A.Message Mapping
B.Groovy Script
C.Router
D.Content Modifier
AnswerD

The Content Modifier step allows reading message headers and using them to set exchange properties. It provides a simple configuration interface to map a header to a property, which can then be referenced later in the flow. This directly fulfills the requirement of extracting a header value and storing it as a property.

Why this answer

The Content Modifier step is specifically designed to read message headers and set exchange properties. By configuring it to take a header value and assign it to a property, the developer can then reference that property in later steps. This is the standard, no-code approach for such extraction and is more efficient than scripting or mapping.

Exam trap

The trap here is overcomplicating the solution by considering scripting or mapping steps, when the Content Modifier is the straightforward, purpose-built step for header-to-property operations.

43
MCQhard

An integration developer is debugging an integration flow that uses a Router step with multiple routes. Only the default route executes even though the incoming payload clearly matches a condition in another route. The condition references a header that is set by a Content Modifier placed after the Router in the flow. What is the most likely cause?

A.The Router evaluates conditions against the message state at the point of the Router, so the header is not yet available
B.Router conditions in SAP Cloud Integration can only reference XPath expressions, never header values
C.The default route always takes precedence and prevents other routes from being evaluated
D.The Content Modifier must be configured with the Replace body option for headers to persist across steps
AnswerA

A Router evaluates its route conditions using the message as it exists when execution reaches the Router. A Content Modifier placed after the Router has not run yet, so the referenced header is absent and none of the conditional routes match, causing the default route to be taken. Moving the Content Modifier before the Router resolves this.

Why this answer

Router steps evaluate conditions against the message state at the moment the Router executes. Because the Content Modifier that creates the referenced header is positioned after the Router, the header simply does not exist yet, so the conditional routes evaluate false and the default route runs. Reordering the steps so the header is set before the Router is the appropriate correction.

Exam trap

The trap here is assuming the routing condition itself is malformed, when the real problem is that the step producing the referenced header executes after the Router.

44
MCQmedium

An integration developer is building an integration flow in SAP Cloud Integration that must process each order in a large XML payload individually. The payload contains an Orders root element with many Order child elements. The developer adds an Iterating Splitter step and configures the XPath expression as /Orders/Order. During testing, the flow fails to process the messages as expected. What is the most likely cause?

A.The Iterating Splitter step requires the XPath expression to be wrapped in a namespace prefix, even when no namespaces are used.
B.The XPath expression must be entered as an absolute path with the correct case and element names, and the payload must match the structure exactly.
C.The Iterating Splitter step must use the Streaming XPath option for large payloads, otherwise it silently drops messages.
D.The XPath expression must be specified as /Orders/Order/ with a trailing slash to select all Order elements.
AnswerB

The Iterating Splitter uses XPath 1.0, which is case-sensitive and requires exact element names. If the payload uses different casing or a different root element, or if the expression is not an absolute path, no nodes are selected. The developer must ensure /Orders/Order matches the actual XML structure.

Why this answer

The Iterating Splitter evaluates the XPath expression against the incoming message. If the expression does not match any nodes due to case differences, wrong element names, or a different hierarchy, the splitter produces no messages or fails. Verifying that /Orders/Order matches the payload exactly resolves the issue.

Exam trap

The trap here is assuming the splitter silently handles mismatched XPath or that extra options like streaming or trailing slashes fix a structural mismatch.

45
MCQeasy

An integration developer needs to persist a message to a data store so that a later integration flow run can check whether the same message was already processed. Which SAP Cloud Integration step should be used to store and retrieve this state across flow executions?

A.A Persist step configured with the message payload.
B.A Write step followed by a Read step in the Data Store operations.
C.A JMS queue sender adapter configured with a durable subscription.
D.A Content Modifier that sets a property with the message identifier.
AnswerB

Data Store operations provide persistent storage within the tenant, with Write to store an entry and Read or Select to retrieve it in a later run. Using Write to persist the processed message and Read or Select to check for its existence in a subsequent execution supports exactly the cross-run state requirement described.

Why this answer

Data Store operations are the tenant-local persistence mechanism for integration flows. Writing the processed message identifier and later reading or selecting it lets a subsequent run detect duplicates or share state across executions. Headers and properties are scoped to a single exchange, and no Persist step exists, so the Data Store approach is the correct fit.

Exam trap

The trap here is confusing message-scoped headers and properties with tenant-persistent storage, when only Data Store operations survive beyond a single flow execution.

46
MCQmedium

An integration developer is designing an integration flow in SAP Cloud Integration that must post messages to a receiver system only after first acquiring a short-lived access token, and must never retry the token acquisition more than once per message. Which step type should be used to implement the token request and make its result available to the subsequent receiver call?

A.A Groovy Script step that opens a raw socket to the token endpoint and assigns the response to a header.
B.A Message Mapping step that maps the token endpoint schema to an exchange property using a graphical mapping function.
C.A Content Enricher step that merges the token endpoint response into the message body before the receiver call.
D.A Request Reply step containing a second integration process with an HTTP receiver adapter to the token endpoint, whose response is stored in a property via a Content Modifier.
AnswerD

A Request Reply step invoking a separate integration process lets the flow perform the token call synchronously and return the token to the calling exchange. The Content Modifier then writes the access token into an exchange property, which the later receiver adapter can reference through a dynamic configuration, achieving exactly one token acquisition per message without external scripting.

Why this answer

The token must be fetched exactly once per message and made available to a later receiver call. A Request Reply step that calls a separate integration process with an HTTP receiver adapter performs the synchronous token request, and a Content Modifier stores the returned access token in an exchange property. The receiver adapter then references that property via dynamic configuration, satisfying the single-attempt requirement without scripting.

Exam trap

The trap here is assuming that a Content Enricher or Message Mapping step can perform an outbound HTTP call to fetch credentials, when only adapter-driven steps such as Request Reply can invoke a remote endpoint.

47
MCQmedium

An integration developer is using a Groovy script step in an integration flow to modify the message body. The script needs to read a header named 'CustomerID' and set a new header named 'CustomerType' based on its value. Which code snippet correctly accomplishes this in SAP Cloud Integration?

A.def customerId = message.getBody(String.class); message.setHeader("CustomerType", customerId == "VIP" ? "Premium" : "Standard");
B.def customerId = message.getProperty("CustomerID"); message.setProperty("CustomerType", customerId == "VIP" ? "Premium" : "Standard");
C.def customerId = message.getHeaders().get("CustomerID"); message.setProperty("CustomerType", customerId == "VIP" ? "Premium" : "Standard");
D.def customerId = message.getHeaders().get("CustomerID"); message.setHeader("CustomerType", customerId == "VIP" ? "Premium" : "Standard");
AnswerD

This snippet uses the message API to retrieve the CustomerID header and then sets a new CustomerType header based on a conditional expression. It correctly accesses the headers and modifies the message headers, which is the intended way to manipulate headers in a Groovy script step.

Why this answer

In a Groovy script step, message headers are accessed via message.getHeaders() and set via message.setHeader(). The correct snippet reads the CustomerID header and sets the CustomerType header using a conditional expression. Using properties or the message body would not meet the requirement of reading a header and setting a header.

Exam trap

The trap here is mixing up headers and properties in the message API, as both have similar getter and setter methods but serve different purposes in the integration flow.

48
MCQmedium

You are developing an integration flow in SAP Cloud Integration that processes incoming orders. The flow must execute a Message Mapping step only for messages whose payload contains a custom header named 'Priority' with the value 'High'. Which step should you place before the Message Mapping to conditionally route the message?

A.Router step with a non-XML condition using the header expression ${header.Priority} = 'High'.
B.Content Modifier step that sets the header 'Priority' to 'High' before the mapping.
C.Groovy Script step that reads the header and throws an exception if it is not 'High'.
D.Message Mapping step with a condition defined in the mapping editor.
AnswerA

The Router step evaluates conditions on the message context, including headers. Using a non-XML expression like ${header.Priority} = 'High' correctly checks the header value and routes the message to the branch containing the Message Mapping. This is the standard way to implement conditional processing based on header values in SAP Cloud Integration.

Why this answer

To conditionally execute a step based on a header, a Router step with a non-XML condition is used. The expression ${header.Priority} = 'High' evaluates the header value and directs the message to the appropriate branch. Other steps like Content Modifier or Script cannot conditionally bypass a subsequent step without failing the flow.

The Router is the correct integration pattern for this scenario.

Exam trap

The trap here is assuming that a Content Modifier or Script can conditionally skip a step, when actually only a Router step provides conditional branching.

49
Multi-Selectmedium

An integration developer is troubleshooting an integration flow that intermittently fails when writing to an SAP S/4HANA system with the OData V2 receiver adapter. Monitoring shows the payload is valid and credentials are correct, but some messages fail with a timeout under peak load. Which TWO configuration changes should the developer apply to improve resilience? (Choose two.)

Select 2 answers
A.Switch the receiver adapter to the SOAP protocol to reduce overhead
B.Increase the connection and response timeout values in the OData receiver adapter
C.Move the OData call into a Local Integration Process to isolate it
D.Configure the adapter's retry settings to retry idempotent read operations on transient errors
E.Disable the CSRF token handling in the adapter to save a round trip
AnswersB, D

Timeouts under peak load typically mean the backend takes longer to respond than the adapter is willing to wait. Raising the connection and response timeout values gives the S/4HANA system more time to complete slow requests, directly reducing the intermittent timeout failures without changing the payload or credentials.

Why this answer

Intermittent timeouts under peak load point to the adapter giving up before a busy backend responds, and to transient network or backend hiccups. Raising the connection and response timeouts lets slow-but-successful calls complete, while retrying idempotent reads on transient errors absorbs momentary failures without risking duplicate writes.

Exam trap

The trap here is treating a protocol or structural change as a resilience fix, when the actual levers are timeout values and retry behavior scoped to safe operations.

50
MCQmedium

An integration flow uses a multicast step with two branches. The first branch writes to an SFTP server and the second branch sends an alert email. The developer observes that when the SFTP write fails, the email is never sent. Which multicast configuration change ensures the email branch still executes when the SFTP branch fails?

A.Enable 'Stop on Exception' on the multicast and add an Exception Subprocess to the flow.
B.Disable 'Stop on Exception' on the multicast so remaining branches continue after a branch fails.
C.Wrap the SFTP branch in a Local Integration Process and set its quality of service to Exactly Once.
D.Change the multicast to sequential processing and set the SFTP branch as the first route.
AnswerB

When 'Stop on Exception' is disabled, the multicast step treats each branch independently: if one branch raises an exception, the runtime logs it but continues executing the remaining branches. Disabling this option therefore allows the email branch to run even when the SFTP write fails, which is exactly the required behavior.

Why this answer

The multicast step's 'Stop on Exception' option controls whether a failing branch aborts the remaining branches. Disabling it makes the runtime process each branch independently, logging the failure of the SFTP branch while still executing the email branch. This isolation is what guarantees the alert is sent despite the SFTP error.

Exam trap

The trap here is assuming branch execution order or exception subprocesses control sibling behavior, when the multicast's 'Stop on Exception' flag is the actual switch.

51
MCQeasy

An integration developer needs to create a reusable script that parses a JSON payload and extracts a specific field. The script will be used in multiple integration flows. Where should the script be stored in SAP Integration Suite?

A.In the 'Value Mapping' artifact, alongside mapping definitions.
B.In the 'Script Collection' artifact, which can be referenced by multiple integration flows.
C.In the 'Scripts' folder within the integration package that contains the flows.
D.In the 'Resources' section of the tenant's Monitor dashboard.
AnswerB

A Script Collection is a dedicated artifact in SAP Integration Suite that stores reusable scripts. It can be referenced from any integration flow within the same tenant, regardless of the package. This promotes reuse and centralizes script maintenance. It is the correct place for scripts intended for multiple flows.

Why this answer

In SAP Integration Suite, a Script Collection is a reusable artifact that can store multiple scripts and be referenced by any integration flow in the tenant. This allows developers to centralize script logic, avoid duplication, and maintain a single source of truth. Storing scripts in a package-local folder or other artifacts does not provide cross-package reusability.

Exam trap

The trap here is assuming that scripts stored in an integration package's Scripts folder are automatically reusable across all packages, when only a Script Collection provides that central reuse.

52
MCQmedium

You are developing an integration flow in SAP Cloud Integration that sends messages to an external SOAP service. The service requires a custom SOAP header element named CorrelationId whose value must come from an exchange property called correlationID. You have already added a Content Modifier step and created the exchange property. Which step should you add next to insert the SOAP header into the outbound message?

A.Add an XML Modifier step and use an XPath expression to insert the header element.
B.Add a SOAP Header step and configure it to set the header name and value from the exchange property.
C.Add a Groovy Script step and manually construct the SOAP envelope with the header.
D.Add a Message Mapping step and map the exchange property to a header field in the target structure.
AnswerB

The SOAP Header step is specifically designed to add or modify SOAP headers in the message. You can specify the header name and use an expression to set the value from an exchange property. This directly satisfies the requirement without altering the payload body and keeps the SOAP envelope intact.

Why this answer

The SOAP Header step in SAP Cloud Integration is purpose-built to add SOAP headers to an outbound message. It allows you to define header names and values, including dynamic values from exchange properties. This keeps the message body unchanged and ensures the SOAP envelope remains valid.

Other steps either do not target SOAP headers or require unnecessary complexity.

Exam trap

The trap here is assuming that any XML manipulation step can set SOAP headers, when only the SOAP Header step is designed for that specific purpose.

53
Multi-Selectmedium

An integration developer is configuring an HTTPS sender adapter in SAP Cloud Integration to receive messages from an external partner. The partner will authenticate using client certificate authentication. The developer must ensure the partner's certificate is trusted and that the integration flow can be called securely. Which two actions must the developer perform? (Choose two.)

Select 2 answers
A.Create an OAuth2 Client Credentials security material and reference it in the sender adapter's authentication settings.
B.Enable CSRF protection on the sender adapter so that the partner's certificate is checked on every request.
C.Add the partner's root or intermediate CA certificate to the SAP Cloud Integration Keystore under the appropriate certificate alias so the incoming client certificate can be validated.
D.Configure the HTTPS sender adapter to use Role-Based Access Control and assign the partner's certificate to a user with the required permissions.
E.Download the SAP Cloud Integration tenant's server certificate and provide it to the partner so the partner can trust the server during the TLS handshake.
AnswersC, E

For client certificate authentication, SAP Cloud Integration must validate the partner's certificate against a trusted CA. Adding the partner's root or intermediate CA certificate to the Keystore allows the runtime to build and verify the chain presented during the TLS handshake. Without this trust anchor, the sender adapter rejects the connection even if the client certificate itself is valid.

Why this answer

Client certificate authentication requires mutual TLS trust. The tenant must trust the partner's certificate chain by adding the issuing CA to the Keystore, and the partner must trust the tenant's server certificate by receiving it or its CA. Together these actions enable the TLS handshake to succeed and the sender adapter to accept the partner's messages.

Exam trap

The trap here is focusing only on the server trusting the client and forgetting that in mutual TLS the client must also trust the server, so both trust directions must be configured.

54
MCQeasy

An integration developer needs the integration flow to continue processing when a receiver returns an HTTP 404, because a missing resource is a valid business outcome. The developer wants the flow to inspect the status code and route the message accordingly instead of failing. Which exception handling configuration should the developer apply to the receiver call?

A.Set the receiver adapter's Retry configuration to retry on all HTTP error codes
B.Set the Exchange Property to store the response and enable the 'Throw exception on failure' option
C.Configure the receiver call as an Exception Subprocess with a condition on the error code
D.Disable the 'Throw exception on failure' option so the status code is written to the message and can be evaluated by a Router
AnswerD

With the throw-on-failure option disabled, the adapter does not raise an exception for HTTP error codes. The response, including the status code, is placed on the message, allowing a subsequent Router or condition to evaluate CamelHttpResponseCode and route the missing-resource case along the intended business path.

Why this answer

To treat an HTTP error status as data rather than a fault, the receiver call must be configured not to raise an exception on failure. The status code then becomes available on the message, and a Router can branch on it, letting the missing-resource case follow the business-valid path while other errors are handled separately.

Exam trap

The trap here is assuming any non-2xx response always aborts the flow, when the adapter's throw-on-failure setting controls whether the status is surfaced as data.

55
MCQeasy

What is the primary function of the 'Content Modifier' component in an integration flow?

A.To connect to external ERP systems.
B.To transform XML to JSON.
C.To manipulate message headers, properties, and body content.
D.To monitor integration flow performance.
AnswerC

The Content Modifier is designed to add, update, or remove message headers, properties, and body segments. This allows developers to inject dynamic values, clean up data, or structure the message precisely as required by the receiver, making it the most frequently used component in any integration scenario.

Why this answer

The Content Modifier is the most versatile component in SAP Integration Suite, allowing developers to create, modify, or delete message headers, properties, and body content. It is essential for mapping data between different formats and enriching messages with external information. Understanding this component is fundamental because it serves as the 'glue' that enables disparate systems with incompatible data structures to communicate effectively.

Exam trap

Candidates often confuse the Content Modifier with a Data Store or Message Mapping step, incorrectly thinking it executes complex structural message transformations or persistent database storage operations.

56
MCQeasy

An integration developer is creating an integration flow in SAP Cloud Integration that must be triggered by an external system sending an HTTP POST request with a JSON payload. The developer needs to define the endpoint and ensure the payload is available to subsequent steps. Which sender adapter should be used?

A.HTTP receiver adapter
B.SOAP sender adapter
C.OData V2 sender adapter
D.HTTPS sender adapter
AnswerD

The HTTPS sender adapter exposes an HTTP endpoint on the tenant that external systems can call with POST requests. It receives the JSON payload and makes it available as the message body to subsequent steps, which is exactly the requirement for an externally triggered JSON integration flow.

Why this answer

To let an external system trigger an integration flow with an HTTP POST carrying JSON, the flow must start with an HTTPS sender adapter. This adapter creates a callable endpoint and delivers the incoming payload as the message body, making it available to all subsequent steps for processing.

Exam trap

The trap here is confusing the HTTP receiver adapter, which sends outbound calls, with the HTTPS sender adapter, which receives inbound requests.

57
MCQhard

An integration developer has an integration flow that processes an order and then must call a legacy SOAP service. The SOAP service requires a WS-Security UsernameToken with a password digest, and the credential must never be stored in the integration flow's configuration. Which approach meets these requirements in SAP Cloud Integration?

A.Store the username and password in a Content Modifier header and enable the SOAP adapter's credential propagation
B.Deploy the credentials as a Secure Store entry and read them with a Groovy script that builds the WS-Security header manually
C.Configure the SOAP receiver adapter with the WS-Security UsernameToken option and reference a Security Material artifact of type User Credentials
D.Create a Keystore artifact containing the password and select it in the SOAP adapter's private key alias field
AnswerC

The SOAP receiver adapter supports WS-Security UsernameToken, including password digest, and can retrieve the username and password from a deployed User Credentials artifact. This keeps the secret out of the integration flow configuration and satisfies the digest requirement, so no credential is hard-coded anywhere in the flow.

Why this answer

WS-Security UsernameToken with password digest is a first-class option on the SOAP receiver adapter in SAP Cloud Integration. Pairing that option with a deployed User Credentials artifact keeps the secret in the tenant's secure store rather than in the flow configuration, and the adapter computes the digest, nonce, and timestamp automatically for each outbound request.

Exam trap

The trap here is reaching for a script or header to inject credentials when the SOAP receiver adapter already handles WS-Security UsernameToken natively with a secure artifact.

58
MCQmedium

An integration developer is configuring a Message Mapping step in an integration flow. The target structure must include a subtotal element that sums the Price values of all Item nodes from the source, and the mapping also contains a user-defined function that performs this summation. After deployment, the receiver reports that the subtotal is always 0. The developer confirms the source payload contains multiple Item nodes with valid numeric Price values. What is the most likely cause?

A.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.
B.The user-defined function must be written as a Groovy script in the Script step instead of a message mapping function, because mapping functions cannot aggregate values.
C.The mapping runtime does not support user-defined functions that perform arithmetic on numeric values, so the subtotal element is left empty.
D.The Price element in the source is a string, so the mapping engine treats it as text and cannot sum it, resulting in 0.
AnswerA

In SAP Cloud Integration message mapping, a user-defined function that accumulates values across multiple occurrences of the same source node must be declared as a queue function. Without queue processing, the function is invoked per context, resetting the accumulator for each Item node, so the returned sum is 0 or only the last value, depending on implementation.

Why this answer

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.

Exam trap

The trap here is assuming that any user-defined function automatically aggregates across all occurrences of a source node, when it actually runs per context unless explicitly queued.

59
MCQmedium

An integration developer is building an integration flow in SAP Cloud Integration that must process very large XML payloads. The flow splits the message using an Iterating Splitter, but the developer notices that the entire message is being loaded into memory before splitting, causing OutOfMemory errors. Which splitter type should be used to process the message in a streaming fashion?

A.Iterating Splitter
B.General Splitter
C.PKCS7/CMS Splitter
D.Streaming Splitter
AnswerD

The Streaming Splitter processes the incoming message as a stream, reading and splitting it incrementally without loading the entire payload into memory. This is exactly what is needed for very large XML messages to avoid OutOfMemory errors. It uses a StAX parser to emit split messages as they are read, making it the correct choice for high-volume, memory-constrained scenarios.

Why this answer

The Streaming Splitter is designed to handle large messages by parsing the input as a stream rather than building a complete DOM in memory. This prevents the OutOfMemory errors caused by the Iterating Splitter, which loads the entire message. For very large XML payloads, the streaming approach is the appropriate solution.

Exam trap

The trap here is assuming that any splitter type will automatically stream the payload, when in fact only the Streaming Splitter uses a streaming parser to avoid loading the entire message into memory.

60
MCQmedium

When using the 'Splitter' component, which processing mode ensures that the messages are processed in a specific order and waits for each sub-message to finish before continuing?

A.Parallel Processing enabled.
B.Sequential Processing.
C.Aggregator mode.
D.Broadcast mode.
AnswerB

Sequential processing processes each sub-message one at a time, ensuring that the next message is only triggered after the previous one completes. This is the correct choice when the order of arrival is vital for maintaining the integrity of dependent business processes in the downstream target application.

Why this answer

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.

Exam trap

Candidates often assume that the Splitter processes messages in order by default, failing to realize that Parallel Processing is often enabled, which causes non-deterministic ordering and potential downstream race conditions.

61
MCQmedium

An integration developer is building a Cloud Integration flow that connects to an external REST API requiring OAuth 2.0 client credentials authentication. The developer needs to ensure that the access token is cached efficiently across multiple concurrent message processing threads without repeatedly invoking the token endpoint. Which configuration step fulfills this requirement?

A.Store the client secret as a secure parameter in the Partner Directory and write a custom Groovy script using the Apache Oltu library to manually fetch and cache tokens in the global variable space.
B.Configure a Content Modifier step at the very beginning of the integration flow to call the token endpoint using a POST method, then store the resulting bearer token inside a message header for subsequent adapter calls.
C.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.
D.Deploy a separate timer-triggered integration flow that fetches the OAuth token every minute, writes it to a Data Store entry, and configure the main integration flow to read this Data Store entry prior to calling the target API.
AnswerC

Storing the OAuth2 Client Credentials artifact in the tenant keystore lets the HTTP Receiver adapter reuse a single cached token across concurrent threads, so the token endpoint is not invoked per message. This directly satisfies the requirement to cache efficiently without repeated token calls.

Why this answer

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.

Exam trap

Candidates often choose to implement custom Groovy scripts to manage token retrieval and caching, mistakenly believing that native adapter capabilities are insufficient for complex OAuth 2.0 token lifecycle management in high-concurrency scenarios.

62
MCQeasy

An integration developer needs to create an integration flow that reads a file from an SFTP server and writes it to an SAP S/4HANA system using the OData adapter. The file contains a CSV payload that must be converted to XML before mapping. Which step should be used to convert the CSV to XML?

A.Message Mapping
B.CSV to XML Converter
C.XML to CSV Converter
D.Groovy Script
AnswerB

The CSV to XML Converter step is designed to transform CSV-formatted data into XML. It allows you to specify the delimiter, field names, and other parameters. This is the standard and most efficient way to convert CSV to XML in SAP Cloud Integration, and it prepares the payload for subsequent mapping steps.

Why this answer

The CSV to XML Converter step is purpose-built to transform CSV data into XML format. It handles parsing, delimiter detection, and field mapping, producing a well-formed XML document. This step is essential before any XML-based mapping or routing can occur.

Other options either perform the reverse conversion or are not specialized for this task.

Exam trap

The trap here is selecting a general-purpose step like Message Mapping or Groovy when a dedicated converter exists that directly addresses the requirement.

63
MCQeasy

An integration developer needs to expose a Cloud Integration flow as an OData service that can be consumed by an SAP Fiori app. The flow must support query operations with filters. Which sender adapter should be used?

A.HTTP sender adapter
B.SOAP sender adapter
C.OData sender adapter
D.IDoc sender adapter
AnswerC

The OData sender adapter allows the integration flow to be exposed as an OData service, supporting standard OData query options such as $filter, $select, and $expand. This is the native protocol for SAP Fiori apps, making it the correct choice for enabling query operations with filters from a Fiori UI.

Why this answer

The OData sender adapter is specifically designed to expose integration flows as OData services. It supports OData query options like $filter, $select, and $expand, which are essential for Fiori apps to perform filtered queries. Other adapters like SOAP, HTTP, or IDoc do not provide native OData support and would require additional transformation or custom logic to handle OData queries.

Exam trap

The trap here is confusing a generic HTTP endpoint with an OData service, assuming any HTTP-based adapter can serve Fiori apps.

64
MCQhard

You are troubleshooting an integration flow that uses a Groovy script to modify the message body. The script is throwing a 'java.lang.NullPointerException' when accessing a header that was set by a previous Content Modifier step. The header is named 'CustomerID'. What is the most likely cause?

A.The Groovy script is executed in a different message exchange than the one where the header was set, such as after a split or in a separate branch.
B.The Groovy script is trying to access the header using the wrong API method, such as getHeader instead of getProperty.
C.The Content Modifier step is configured to set the header only in the 'Expression' mode, and the expression evaluates to null.
D.The header name 'CustomerID' is case-sensitive and the Content Modifier set it as 'customerid'.
AnswerA

In SAP Cloud Integration, headers are scoped to the message exchange. If the script runs in a different exchange (e.g., after a split or in a parallel branch), the header set in the original exchange is not available, leading to a null value and NullPointerException when accessed. This is a common pitfall.

Why this answer

The most likely cause is that the Groovy script is executing in a different message exchange context than where the header was set. Headers are not propagated across splits or parallel branches automatically. When the script tries to access the header, it gets null, and if it then calls a method on that null, a NullPointerException occurs.

Checking the flow's structure for splits or branches is essential.

Exam trap

The trap here is overlooking the message exchange scope of headers, assuming they are globally available throughout the entire integration flow.

65
MCQmedium

You are troubleshooting an integration flow that uses a Request-Reply step to call an external REST API. The API sometimes returns a 401 Unauthorized error. You have verified that the credentials are correct. Which configuration should you check in the Request-Reply step to ensure that the authentication header is being sent correctly?

A.The 'Timeout' value is set too low, causing the request to fail before authentication.
B.The 'Authentication' method is set to 'None' instead of 'Basic' or 'OAuth 2.0'.
C.The 'Proxy Type' is set to 'Internet' instead of 'On-Premise'.
D.The 'CSRF Protected' checkbox is enabled.
AnswerB

If the Request-Reply step's authentication method is set to 'None', no Authorization header is sent. The external API then returns 401 Unauthorized. Even if credentials are configured elsewhere, they are not used unless the authentication method is explicitly set to the correct type, such as Basic or OAuth 2.0. This is a common misconfiguration.

Why this answer

A 401 Unauthorized error indicates that the request lacked valid authentication credentials. In the Request-Reply step, the authentication method must be set to the appropriate type (e.g., Basic, OAuth 2.0) and the credential alias must be specified. If set to 'None', no Authorization header is sent.

Other settings like timeout or proxy type would produce different errors.

Exam trap

The trap here is focusing on network or timeout settings when the issue is simply that authentication is not configured to send credentials.

66
MCQmedium

An integration developer must expose an integration flow as an HTTPS endpoint that a partner will call. The partner requires mutual TLS authentication, and only certificates issued by the partner's internal CA should be accepted. The developer has uploaded the partner's root CA certificate into the tenant keystore. Which additional configuration on the HTTPS sender adapter is required to enforce mutual TLS with that specific CA?

A.Set the Authorization option to 'None' and rely on the partner's IP allowlist configured in the Cloud Integration tenant firewall settings.
B.Set the Authorization option to 'Role-Based' and add the partner's certificate to the tenant keystore under a new alias used only by this flow.
C.Set the Authorization option to 'User Role' and assign the partner's technical user to the ESBMessaging.send role.
D.Set the Authorization option to 'Client Certificate' and select the partner's root CA certificate as the trusted issuer in the sender adapter's certificate configuration.
AnswerD

Choosing Client Certificate authorization makes the sender adapter request a client certificate during the TLS handshake and validate it against the configured trusted issuer. Selecting the partner's root CA as the trusted issuer restricts acceptance to certificates chaining to that CA, which is exactly the mutual TLS requirement described. This enforces both authentication and the CA restriction in one configuration.

Why this answer

Mutual TLS on an HTTPS sender adapter is enabled by selecting Client Certificate authorization, which causes the runtime to request a client certificate during the TLS handshake. The trusted issuer list must include the partner's root CA so only certificates chaining to it are accepted. Role-based or None authorization does not validate client certificates, and merely storing the CA in the keystore without referencing it as a trusted issuer leaves the endpoint unauthenticated.

Exam trap

The trap here is confusing keystore storage with trust configuration, when the CA must also be selected as the trusted issuer in the sender adapter's Client Certificate authorization settings.

67
MCQhard

An integration developer is troubleshooting an integration flow that uses a Content Modifier step to set a header named OrderType based on a value read from the payload. A subsequent Router step using XPath on the header always routes to the default branch. The developer confirmed the payload contains the expected value. What is the most likely cause?

A.The Content Modifier step must be configured with 'Overwrite' enabled for headers to be visible to downstream steps.
B.The Router step evaluates XPath against the payload, not against headers, so referencing a header in the XPath expression always fails.
C.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.
D.The Router step requires the header name to be prefixed with 'SAP_' to be visible to the routing expression.
AnswerC

In SAP Cloud Integration, headers and exchange properties are distinct storage locations. If the Content Modifier wrote the value into a property but the Router expression references a header with the same name, the header will be empty and the default branch executes. Aligning the storage location fixes the routing.

Why this answer

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.

Exam trap

The trap here is treating headers and properties as interchangeable, when they are distinct storage scopes that a Router expression must reference explicitly.

68
MCQmedium

An integration developer is configuring an integration flow in SAP Cloud Integration that must route messages to different receiver systems based on the value of a header named CountryCode. The value can be DE, US, or FR. The developer wants to minimize the number of steps and ensure the routing logic is evaluated at runtime. Which step should be used to achieve this?

A.Router step with a non-XML condition
B.Content Modifier step that sets a property for each country
C.Groovy Script step that sets a header for each country
D.XSLT Mapping step with conditional templates
AnswerA

The Router step evaluates conditions at runtime and can route messages to multiple branches based on header values. Using a non-XML condition, the developer can reference the CountryCode header directly, reducing the need for additional mapping steps and ensuring dynamic routing without hardcoding.

Why this answer

The Router step is designed to evaluate conditions at runtime and direct messages to different branches. By using a non-XML condition, the developer can directly reference the CountryCode header, avoiding extra steps and ensuring dynamic routing. This approach is efficient and aligns with standard integration flow design.

Exam trap

The trap here is confusing message transformation or header manipulation steps with routing steps, assuming that setting a property or header automatically routes the message.

69
MCQmedium

An integration developer is building an integration flow in SAP Cloud Integration that must process messages in a strict sequence. Multiple messages arrive at the same time from an HTTPS sender, and the developer needs the flow to execute only one message at a time, in the exact order they were received. Which configuration should be applied?

A.Configure the sender adapter to use 'Best Effort' quality of service and enable message ordering.
B.Set the runtime configuration of the integration flow to 'Sequential Processing' and set the maximum number of concurrent executions to 1.
C.Enable the 'Exclusive' option in the JMS queue configuration of the sender adapter.
D.Add a 'Splitter' step with sequential processing enabled at the start of the integration flow.
AnswerB

In SAP Cloud Integration, the integration flow runtime configuration allows you to set the message processing mode. Selecting 'Sequential Processing' with a maximum concurrency of 1 ensures that the flow processes exactly one message at a time and in the order received. This is the correct mechanism to enforce serialized, ordered execution of an integration flow.

Why this answer

To enforce that an integration flow processes messages one at a time and in the order received, the runtime configuration must be set to sequential processing with a maximum concurrency of 1. This is a property of the integration flow itself, not of the sender adapter or any step within the flow. The other options address delivery guarantees, message splitting, or queue behavior, none of which control the flow's runtime concurrency.

Exam trap

The trap here is assuming that sender adapter settings or queue options can control the execution order of an integration flow, when in fact only the integration flow's runtime configuration governs concurrency and sequencing.

70
MCQmedium

An integration developer is configuring a Message Mapping in SAP Cloud Integration. The target structure requires an element `CustomerID` that must combine the source fields `Region` and `Number` into a single string. The mapping must be reusable in several integration flows. Which approach should the developer use?

A.Create a User-Defined Function in the mapping with parameters for Region and Number, and call it from the target element.
B.Use a Groovy script step after the mapping to concatenate Region and Number in the target payload.
C.Define a Value Mapping artifact that maps each Region and Number combination to a CustomerID.
D.Add a Content Modifier step before the mapping to write the concatenated value into the message header, then map the header to CustomerID.
AnswerA

A User-Defined Function encapsulates the concatenation logic and can be stored in the mapping artifact, then reused wherever the mapping is referenced. It keeps the transformation logic inside the mapping, avoids external dependencies, and supports parameters so Region and Number are passed dynamically. This is the standard way to implement custom reusable logic in SAP Cloud Integration Message Mapping.

Why this answer

The requirement is a custom, reusable payload transformation inside a Message Mapping. A User-Defined Function is the native mapping construct for custom logic with parameters and can be saved with the mapping artifact, making it reusable across integration flows. Other approaches either place logic outside the mapping or use artifacts not designed for dynamic concatenation.

Exam trap

The trap here is assuming any custom logic must be implemented in a Groovy script step, when SAP Cloud Integration Message Mapping natively supports reusable User-Defined Functions.

71
MCQhard

An integration developer is configuring a Message Mapping in SAP Cloud Integration to transform a source XML payload into a target XML structure. The source contains a repeating node called 'Items' with multiple 'Item' elements, and the target requires a flat list of 'Product' elements under a 'Products' root. The developer needs to ensure that each 'Item' is mapped to a separate 'Product' element. Which mapping technique should be used?

A.Use a user-defined function that concatenates all 'Item' values into a single 'Product' element.
B.Use a standard mapping with a one-to-many function to split the 'Items' node into multiple 'Product' elements.
C.Use a one-to-one mapping with a context change to iterate over the 'Item' nodes and map each to a 'Product' element.
D.Use a value mapping to map each 'Item' to a 'Product' element based on a lookup table.
AnswerC

A context change in the Message Mapping allows the mapping to process each occurrence of the 'Item' node individually, creating a separate 'Product' element for each. This is the standard approach for converting repeating structures into a flat list in SAP Cloud Integration.

Why this answer

To transform a repeating source node into a flat list of target elements, a context change is required in the Message Mapping. This allows the mapping logic to be applied to each occurrence of the repeating node, generating one target element per source occurrence. Other techniques like concatenation or value mapping do not achieve the required structural transformation.

Exam trap

The trap here is confusing context change with one-to-many functions or value mappings, which are used for different purposes and do not handle iteration over repeating nodes.

72
MCQmedium

An integration developer is configuring a Message Mapping step in SAP Cloud Integration. The source structure contains a repeating node <Items> that can appear up to 500 times, and the target structure expects exactly one <ItemCount> element containing the total number of occurrences. Which mapping function should be used to populate the <ItemCount> target field?

A.Use the standard sum function on the <Items> node and assign the aggregated result to the <ItemCount> target element.
B.Use the standard exists function on the <Items> node and assign the Boolean result to the <ItemCount> target element.
C.Use the standard count function on the <Items> node and assign the result to the <ItemCount> target element.
D.Use the standard index function on the <Items> node and assign the last index value to the <ItemCount> target element.
AnswerC

The standard count function returns the number of occurrences of a source node and can be mapped directly to a target element. It is the intended way to obtain the total number of repeating nodes in a Message Mapping, so the target <ItemCount> element receives the exact count of <Items> occurrences.

Why this answer

The standard count function is specifically designed to return the number of occurrences of a source node in a Message Mapping. Mapping it to the <ItemCount> target element produces the total number of repeating <Items> nodes, which is exactly what the target structure requires. Other standard functions such as exists, index, or sum serve different purposes and would not yield the correct total count.

Exam trap

The trap here is confusing functions that operate on node presence or position, such as exists or index, with the count function that returns the actual number of repeating occurrences.

73
MCQeasy

You are developing an integration flow in SAP Cloud Integration that needs to read a file from an SFTP server and then write the processed data to another SFTP server. Which two adapter types must you configure in the integration flow to achieve this?

A.SFTP sender adapter and OData receiver adapter.
B.SFTP sender adapter and Mail receiver adapter.
C.SFTP sender adapter and SFTP receiver adapter.
D.HTTPS sender adapter and SFTP receiver adapter.
AnswerC

To read from an SFTP server, you use an SFTP sender adapter, which polls the server for files. To write to another SFTP server, you use an SFTP receiver adapter, which sends the processed data. This combination allows the integration flow to fetch files from one SFTP location and deliver them to another, fulfilling the requirement.

Why this answer

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.

Exam trap

The trap here is mixing up sender and receiver adapters for different protocols, such as using an HTTPS sender when SFTP is needed, or choosing a Mail receiver instead of SFTP for file transfer.

74
MCQeasy

An integration developer needs to reuse a set of field mappings across several integration flows. The mappings convert country codes to ISO alpha-3 values and are maintained by a central team. Which SAP Integration Suite artifact type should be created to store and version these reusable mappings?

A.A Message Mapping artifact containing the source and target structures.
B.An Integration Flow artifact configured as a reusable sub-process.
C.A Value Mapping artifact that stores source and target agency/identifier pairs.
D.A Script Collection artifact that contains reusable Groovy scripts.
AnswerC

A Value Mapping artifact is precisely the shared repository for code-list conversions such as country codes to ISO alpha-3 values. It stores agency, identifier, and value pairs and can be referenced from multiple integration flows via a Value Mapping step. Central maintenance and transport ensure consistent reuse across flows and tenants.

Why this answer

The Value Mapping artifact is the Integration Suite construct for maintaining reusable code-list conversions, such as country code to ISO alpha-3. It stores agency, identifier, and value pairs that integration flows reference through a Value Mapping step, allowing a central team to update values once and have every consuming flow pick up the change.

Exam trap

The trap here is confusing reusable mapping logic with reusable mapping data; a Message Mapping holds transformation logic, whereas a Value Mapping holds the lookup values.

75
MCQeasy

An integration developer needs to store a reusable credential for an external system in SAP Integration Suite. The credential must be accessible from multiple integration flows and must not be exposed in the integration flow configuration. Which artifact should be used?

A.Partner Directory
B.Security Material (User Credentials)
C.Content Modifier
D.Message Mapping
AnswerB

Security Material of type User Credentials is designed to store username-password pairs securely in the tenant's keystore. It can be referenced by name in multiple integration flows, and the actual credentials are never exposed in the flow configuration. This meets the requirement for reusability and security, making it the correct choice.

Why this answer

Security Material provides a centralized, secure store for credentials that can be referenced by name across multiple integration flows. It ensures credentials are encrypted and not exposed in design or runtime. Other artifacts serve different purposes: Partner Directory for partner data, Message Mapping for transformations, and Content Modifier for message manipulation.

None offer the required security and reusability.

Exam trap

The trap here is confusing the Partner Directory with a secure credential store; while it can hold data, it is not designed for encrypted credentials.

Page 1 of 3

Page 2

All pages

Practice C_CPI by domain

Target a specific domain to shore up weak areas.

See all domains with question counts →