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.

• ✗

  Add a Content Modifier to insert the UsernameToken header manually into the SOAP envelope

  Why it's wrong here

  Manually inserting a WS-Security header via Content Modifier bypasses the adapter's built-in security handling and is error-prone, especially regarding timestamp and nonce generation. The SOAP adapter's WS-Security configuration handles these elements correctly. Manual insertion also risks exposing credentials in logs and does not integrate with the User Credentials artifact.

• ✓

  Configure a WS-Security Username Token in the SOAP receiver adapter with a User Credentials artifact

  Why this is correct

  The SOAP receiver adapter supports WS-Security UsernameToken configuration, where the username and password are sourced from a deployed User Credentials artifact. This satisfies the service's authentication requirement without hardcoding secrets. It is the standard mechanism for UsernameToken in Cloud Integration and directly addresses the scenario.

• ✗

  Enable OAuth 2.0 client credentials in the SOAP adapter's authentication settings

  Why it's wrong here

  OAuth 2.0 client credentials is a different authentication mechanism than WS-Security UsernameToken. The external service requires UsernameToken, so configuring OAuth would not satisfy its authentication expectations. Additionally, the SOAP adapter's WS-Security settings are separate from OAuth configuration, making this option both incorrect and unrelated to the requirement.

• ✓

  Deploy the service's root CA certificate in the tenant keystore and reference it in the SOAP adapter's trust configuration

  Why this is correct

  To validate the external service's certificate, the issuing CA must be present in the tenant keystore so the TLS handshake can be verified. Deploying the root CA and referencing the keystore in the adapter's trust settings enables certificate validation. This is required for secure outbound HTTPS calls to a service with a non-public CA.

• ✗

  Configure the SOAP adapter to use Proxy Type 'On-Premise' with a Cloud Connector location ID

  Why it's wrong here

  Proxy Type 'On-Premise' is used when the target service resides behind a Cloud Connector on the customer network. The scenario describes an external SOAP service reachable over the internet, so on-premise proxy settings are unnecessary and would misroute the call. This option does not address authentication or certificate validation.