C_CPI Integration Suite Development Practice Question
An integration developer is creating an integration flow in SAP Cloud Integration that must expose an HTTPS endpoint for a partner to send JSON payloads. The developer wants to ensure that only authorized partners can access the endpoint and that the payload is validated against a JSON schema. Which combination of steps should be used?
⚠ Common exam trap
Watch out — candidates often confuse the XML Validator with the JSON Validator, as both are validation steps but apply to different payload formats.
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
✓
Use an HTTPS sender adapter with Client Certificate authentication, followed by a JSON Validator step.
To securely expose an HTTPS endpoint for JSON payloads, the HTTPS sender adapter with Client Certificate authentication provides strong mutual authentication. The JSON Validator step then validates the payload against a JSON schema, ensuring structural correctness. This combination directly addresses both the security and validation needs without unnecessary transformations.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use an IDoc sender adapter with Basic Authentication, followed by a JSON to XML converter and then an XML Validator.
Why it's wrong here
The IDoc sender adapter is used for IDoc messages, not for exposing an HTTPS endpoint for JSON. Basic Authentication is less secure than client certificates for partner access. Additionally, converting JSON to XML before validation adds unnecessary complexity. This combination does not align with the stated requirements.
- ✗
Use an HTTPS sender adapter with Role-Based Authentication, followed by a Content Modifier to check the JSON structure.
Why it's wrong here
Role-Based Authentication is not a standard authentication method for the HTTPS sender adapter; it typically uses Basic, Client Certificate, or OAuth. A Content Modifier cannot validate JSON against a schema; it only modifies headers or properties. This approach would not enforce schema validation and could allow invalid payloads.
- ✓
Use an HTTPS sender adapter with Client Certificate authentication, followed by a JSON Validator step.
Why this is correct
The HTTPS sender adapter supports Client Certificate authentication, which authenticates the partner via mutual TLS. The JSON Validator step validates the incoming payload against a provided JSON schema, ensuring data integrity. This combination meets both security and validation requirements without additional components.
- ✗
Use an HTTPS sender adapter with OAuth 2.0 authentication, followed by an XML Validator step.
Why it's wrong here
While OAuth 2.0 can secure the endpoint, the XML Validator step is designed for XML schemas, not JSON. Using it on JSON payloads would fail or produce errors. The requirement specifies JSON payloads, so an XML Validator is inappropriate. This option mixes authentication and validation incorrectly.
About these practice questions
One of 218 original C_CPI practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.