Free Practice Questions for SAP C_CPI_2506 Exam

In SAP Cloud Integration, dynamic configuration values (headers, properties, body elements) are accessed using Expression Language (EL) notation:

${header.} → Accesses a message header value.

${property.} → Accesses a message property.

${body} → Accesses the payload.

Therefore, when you want to set an Entry ID in a Data Store Write operation using a header value, the correct syntax is ${header.receiver}.

For robust security in SAP integration landscapes:

A security architecture must cover:

Authentication → Verifying the identity of users/systems (OAuth 2.0, SAML, certificates).

Authorization → Role-based access control.

Encryption → TLS/SSL for data in transit, strong encryption for data at rest.

This ensures end-to-end security without sacrificing performance or scalability.

Other options:

Skilled teams and security patches are important but are operational measures, not the foundation of integration security.

Centralizing system administration is organizational, not architectural.

Thus, the key is a well-defined security architecture.

In SAP API Management, supported API description languages include:

RAML (RESTful API Modeling Language)

OpenAPI Specification (OAS, formerly Swagger)

Both are industry-standard languages for modeling REST APIs.

Other options:

A. HTML → A markup language for UI, not an API modeling language.

D. CXML (Commerce XML) → A B2B procurement standard, not for API modeling.

In a Data Store Write operation:

If multiple messages are written with the same Entry ID, enabling Overwrite Existing Message ensures that the previous entry is replaced, avoiding duplicate records.

Other options:

Encrypted Stored Message → Secures data, not related to duplicates.

Include Message Headers → Controls storage of headers, not duplication.

Retention Threshold for Alerting → Configures alerts, not duplication.

Thus, the parameter required to avoid duplicates is Overwrite Existing Message.

In SAP Cloud Integration, integration flows are manipulated using a web-based graphical editor:

Allows drag-and-drop of adapters, mappings, scripts, and process steps.

Provides visual orchestration of message flows.

Command-line and raw code editors are not supported for iFlow design (though XML behind the iFlow exists, it is not directly edited by developers).

Thus, the editor is the Graphical editor.

The URL shown is an OData service endpoint exposed from the SAP ES5 Gateway demo system:

https://sapes5.sapdevcenter.com/sap/opu/odata/iwbep/GWSAMPLE_BASIC/ProductSet( 'HT-1000')/ToSalesOrderLineltems

OData services in SAP Gateway return XML responses by default when called in a browser, unless otherwise specified by request headers (like JSON format).

The structure follows AtomPub/Atom XML representation, showing entity details and navigation properties.

Therefore, the file type displayed in the browser is XML, not HTML, Java, or PHP.

In SAP Integration Suite, Event Mesh (EMIS), queue creation and management requires specific role collections assigned to the user in SAP BTP:

EventMeshAdmin → Provides full administration rights (create, delete, configure queues, topics, subscriptions).

EventMeshDeveloper → Allows development tasks, including working with queues and topic subscriptions.

Other options are not correct:

Message client administrators group membership → Not a BTP role collection concept.

Administrator privileges on Event Mesh → Too generic; the system enforces access through role collections.

Sufficient authorization within emis-s4hana system → S/4HANA authorizations do not govern Event Mesh capabilities.

Thus, the minimum permission required is assignment of the Event Mesh role collections in BTP.

For a synchronous call to a remote HTTP API in an integration flow:

The OData adapter (or HTTP adapter) is used to perform synchronous request-reply communication with REST-based services.

AMQP → Messaging protocol, not synchronous.

SFTP → File-based transfer, asynchronous.

Mail → For SMTP/IMAP, not synchronous API calls.

Thus, the correct adapter for a synchronous remote API call is OData (or HTTP adapter, depending on configuration).