C_CPI Integration Suite Development Practice Question
An integration developer is configuring a Request Reply step in an integration flow to call an external SOAP service. The service requires WS-Security UsernameToken authentication. The developer has configured the SOAP receiver adapter with the appropriate security settings. However, the service returns a fault indicating authentication failure. What is the most likely reason?
⚠ Common exam trap
The trap here is assuming WS-Security is unsupported or that credentials storage is the issue, rather than the specific password type expected by the service policy.
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
✓
The WS-Security policy requires the password to be sent as plain text, but the adapter is configured to send it as a digest.
WS-Security UsernameToken can be sent with plain text or digest password. If the service expects one type and the adapter sends the other, authentication fails. The developer should verify the service's WS-Security policy and configure the SOAP receiver adapter accordingly, ensuring the password type matches.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The service requires mutual TLS authentication, and WS-Security UsernameToken is not sufficient.
Why it's wrong here
While some services require mutual TLS, the scenario states the service requires WS-Security UsernameToken. The fault indicates authentication failure, which points to a UsernameToken configuration issue rather than a missing TLS layer. Mutual TLS would be an additional requirement, not a replacement.
- ✗
The SOAP receiver adapter does not support WS-Security; a separate WS-Security step must be added before the Request Reply.
Why it's wrong here
SAP Cloud Integration SOAP receiver adapter does support WS-Security configurations, including UsernameToken and X.509. Adding a separate step is not required. The issue is likely a mismatch in the security settings, not a lack of support.
- ✓
The WS-Security policy requires the password to be sent as plain text, but the adapter is configured to send it as a digest.
Why this is correct
WS-Security UsernameToken supports both plain text and digest password types. If the service expects plain text and the adapter sends digest, authentication fails. The developer must align the adapter's security settings with the service's policy. This is a common misconfiguration when integrating with external SOAP services.
- ✗
The username and password must be stored in a User Credentials artifact and referenced via a Secure Store alias.
Why it's wrong here
Using a Secure Store alias is a best practice for credentials, but it is not the cause of authentication failure if the credentials are correct. The fault suggests the password type or token format is wrong. Referencing a Secure Store alias does not automatically fix a mismatch in WS-Security policy.
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.