C_CPI Integration Suite Development Practice Question

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 'Authentication' tab with 'Basic' authentication and provide username and password.

  Why it's wrong here

  Basic authentication uses HTTP headers, not WS-Security SOAP headers. The web service explicitly requires WS-Security with a username token, which is a different mechanism. Using Basic authentication would not meet the security requirement and would likely result in an authentication failure.

• ✗

  Set the 'Message Exchange Pattern' to 'Request-Reply' and add a username token in the message body.

  Why it's wrong here

  The message exchange pattern determines synchronous versus asynchronous communication, not security. Adding a username token in the message body does not conform to WS-Security standards; WS-Security tokens belong in the SOAP header. This approach would not satisfy the web service's authentication requirement.

• ✗

  Use the 'OAuth 2.0' authentication option and configure a client credentials grant.

  Why it's wrong here

  OAuth 2.0 is a different authentication protocol and is not the same as WS-Security username token. The web service specifically requires WS-Security, so OAuth 2.0 would not be accepted. Configuring OAuth 2.0 would be incorrect and would not provide the required username token.

• ✓

  Enable the 'Use WS-Security' option and select 'Username Token' as the security type.

  Why this is correct

  The SOAP adapter in SAP Cloud Integration provides a 'Use WS-Security' option where you can select 'Username Token' to include a username token in the SOAP header. This directly satisfies the web service's requirement for WS-Security with a username token, ensuring authentication is properly handled.