C_CPI Integration Suite Development Practice Question
You are configuring a SOAP receiver adapter in SAP Cloud Integration to call an external web service that requires WS-Security UsernameToken with a password digest. The external service also expects the timestamp to be included, and the digest must use SHA-256. Which configuration steps must you perform in the receiver adapter?
⚠ Common exam trap
The trap here is assuming that any WS-Security token type can be used interchangeably, when the external service's policy strictly demands UsernameToken with SHA-256 and a timestamp.
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, select 'Username Token' as the security token, set the password digest algorithm to SHA-256, and enable 'Include Timestamp'.
The SOAP receiver adapter's WS-Security settings must match the external service's policy. Selecting Username Token with SHA-256 digest and enabling the timestamp creates the correct WS-Security header. Other token types such as X.509 or SAML would not satisfy the UsernameToken requirement, and SHA-1 would fail the digest algorithm constraint.
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, select 'SAML Token' as the security token, and configure the SAML issuer and subject.
Why it's wrong here
SAML Token is used for SAML-based WS-Security assertions, not for UsernameToken with password digest. The external service requires a username token, so a SAML assertion would not satisfy the authentication requirement. SAML configuration involves issuer and subject settings that are irrelevant to this scenario.
- ✗
Enable WS-Security, select 'X.509 Token' as the security token, and configure the keystore alias for the private key.
Why it's wrong here
X.509 Token is used for certificate-based WS-Security, not for UsernameToken with password digest. The external service specifically requires a username and password digest, so an X.509 token would be rejected. Keystore configuration is for signing or encryption, not for the username token scenario described.
- ✗
Enable WS-Security, select 'Username Token' as the security token, and set the password digest algorithm to SHA-1, then add a Content Modifier to insert the Timestamp manually.
Why it's wrong here
The external service requires SHA-256, not SHA-1. Using SHA-1 would produce an incorrect digest and cause authentication failure. Manually inserting a Timestamp via Content Modifier is unnecessary because the adapter has a built-in option to include the timestamp, and manual insertion risks format mismatches.
- ✓
Enable WS-Security, select 'Username Token' as the security token, set the password digest algorithm to SHA-256, and enable 'Include Timestamp'.
Why this is correct
The SOAP receiver adapter's WS-Security configuration allows you to select Username Token, choose the digest algorithm (SHA-256), and include a timestamp. These settings generate the correct WS-Security header with a password digest computed using SHA-256 and a Timestamp element, exactly matching the external service's requirements.
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.