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.

• ✗

  Store the username and password in a Content Modifier header and enable the SOAP adapter's credential propagation

  Why it's wrong here

  Content Modifier headers are plain message headers visible in trace logs and message monitoring, so the secret would be exposed and effectively stored in the flow configuration. Credential propagation also forwards the inbound sender's credentials rather than injecting a dedicated outbound credential, so it would not produce the required UsernameToken.

• ✗

  Deploy the credentials as a Secure Store entry and read them with a Groovy script that builds the WS-Security header manually

  Why it's wrong here

  Reading Secure Store entries via a script is possible, but manually constructing a WS-Security UsernameToken with a correct password digest, nonce, and timestamp is error-prone and unnecessary. The SOAP receiver adapter already provides a supported UsernameToken configuration, so this adds custom code without benefit and risks an incorrect digest.

• ✓

  Configure the SOAP receiver adapter with the WS-Security UsernameToken option and reference a Security Material artifact of type User Credentials

  Why this is correct

  The SOAP receiver adapter supports WS-Security UsernameToken, including password digest, and can retrieve the username and password from a deployed User Credentials artifact. This keeps the secret out of the integration flow configuration and satisfies the digest requirement, so no credential is hard-coded anywhere in the flow.

• ✗

  Create a Keystore artifact containing the password and select it in the SOAP adapter's private key alias field

  Why it's wrong here

  Keystore artifacts hold X.509 key pairs and certificates for signing and TLS, not username and password pairs. The private key alias field is used for WS-Security signing or mutual TLS authentication, so selecting it would not generate a UsernameToken and would fail against a service expecting a password digest.