C_CPI Integration Suite Development Practice Question
You are configuring a SOAP receiver adapter in SAP Cloud Integration to call a third-party web service. The web service requires WS-Security with a UsernameToken for authentication. Which adapter configuration is necessary?
⚠ Common exam trap
Many exam-takers confuse HTTP-level authentication (Basic, OAuth) with SOAP message-level security (WS-Security), which are distinct and serve different purposes.
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
✓
Enable 'WS-Security' and configure the 'Username Token' with the appropriate credentials.
The SOAP receiver adapter must be configured to use WS-Security with a UsernameToken to meet the web service's authentication requirement. This involves enabling WS-Security in the adapter and providing the username and password, either directly or via a security artifact. Other authentication methods like Basic or OAuth operate at different layers and do not satisfy the WS-Security requirement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Enable 'WS-Security' and configure the 'Username Token' with the appropriate credentials.
Why this is correct
The SOAP receiver adapter in SAP Cloud Integration supports WS-Security. By enabling WS-Security and selecting the Username Token option, you can provide the username and password. The adapter will then add the WS-Security header to the SOAP request. This is the correct configuration to meet the web service's authentication requirement.
- ✗
Configure the 'Credential' name in the adapter and reference a security artifact.
Why it's wrong here
While referencing a security artifact (like a User Credentials artifact) is good practice for storing credentials, it alone does not enable WS-Security. You must still enable WS-Security and select Username Token in the adapter settings. Simply configuring a credential name without enabling WS-Security will not add the required header. This option is incomplete.
- ✗
Use OAuth 2.0 client credentials and configure the token endpoint.
Why it's wrong here
OAuth 2.0 is a different authentication mechanism and is not compatible with WS-Security UsernameToken. The web service requires WS-Security, so using OAuth would not work. The SOAP adapter may support OAuth for HTTP authentication, but it does not replace WS-Security for message-level authentication. Therefore, this option does not meet the scenario's requirement.
- ✗
Set the 'Authentication' method to 'Basic' and enter the username and password.
Why it's wrong here
Basic authentication uses the HTTP Authorization header, not WS-Security. The third-party web service specifically requires WS-Security with a UsernameToken, so Basic authentication would not satisfy the requirement. The SOAP adapter's Basic authentication option is for HTTP-level authentication, not for SOAP message-level security. Thus, this option is incorrect.
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.