C_CPI Integration Suite Development Practice Question
A developer needs to call an SAP S/4HANA OData V2 service that requires principal propagation from an on-premise SAP NetWeaver Gateway. The Cloud Integration tenant is connected through Cloud Connector. Users authenticate to Cloud Integration with their SAP IAS identity, and the backend expects the SAP user context. Which combination of configuration elements is required to make principal propagation work end to end?
⚠ Common exam trap
The trap here is believing that any authentication method that reaches the backend will propagate the user, when only the Principal Propagation method with Cloud Connector System Logon trust does so.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure the OData receiver with authentication method 'Principal Propagation' and enable the 'System Logon' in Cloud Connector with the X.509 certificate trust between Cloud Connector and the backend.
Principal propagation forwards the logged-in user's identity to the on-premise backend by having Cloud Connector issue a short-lived certificate for that user, which the backend trusts. The receiver adapter must be set to Principal Propagation, and Cloud Connector must be configured for System Logon with the correct trust configuration. Neither side alone is sufficient, and alternatives like Basic or Client Certificate authenticate the application rather than the user.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configure the OData receiver with authentication method 'Basic Authentication' and store the SAP backend user credentials in a User Credentials artifact in the tenant.
Why it's wrong here
Basic Authentication with a stored User Credentials artifact authenticates every request as the same technical or named user, so the actual logged-in IAS identity is never forwarded. This is a valid pattern for technical connectivity but not for principal propagation, because the backend cannot distinguish which end user triggered the request. It also creates a shared credential that undermines the per-user authorization model.
- ✗
Configure the OData receiver with authentication method 'Client Certificate' and import the tenant's keystore certificate into the backend's trusted CA list.
Why it's wrong here
Client Certificate authentication proves the identity of the Cloud Integration tenant, not of the individual end user. The backend would see the tenant's certificate subject, so all requests collapse to a single technical identity. Principal propagation specifically requires per-user certificate generation by the Cloud Connector, which this configuration does not provide, and thus fails the user-context requirement.
- ✗
Configure the OData receiver with authentication method 'OAuth 2.0 Client Credentials' and map the IAS user to a backend service user in the Cloud Connector principal mapping table.
Why it's wrong here
OAuth 2.0 client credentials authenticates the calling application, not the end user, so the backend would see a technical client rather than the propagated user. Cloud Connector does not maintain an IAS-to-backend-user principal mapping table for this purpose; principal propagation uses certificate-based user context, not OAuth client identity. This approach would defeat the audit and authorization requirements of principal propagation.
- ✓
Configure the OData receiver with authentication method 'Principal Propagation' and enable the 'System Logon' in Cloud Connector with the X.509 certificate trust between Cloud Connector and the backend.
Why this is correct
Principal propagation relies on the Cloud Connector establishing a short-lived X.509 certificate on behalf of the logged-in user, which the backend trusts. Selecting Principal Propagation on the receiver adapter and configuring System Logon trust in Cloud Connector is the standard path. Without both sides, the backend receives an anonymous or technical-user context instead of the propagated user identity.
About these practice questions
This C_CPI question is part of Courseiva's 218-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official SAP exam blueprint
This C_CPI practice question is part of Courseiva's free SAP certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the C_CPI exam.