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.

• ✓

  Import the partner's public certificate for signature verification, import your private key for decryption, and enable both signature verification and decryption in the adapter.

  Why this is correct

  The AS2 sender adapter requires the partner's public certificate to verify their digital signature, and your own private key to decrypt the message payload. Enabling both signature verification and decryption in the adapter configuration ensures the message is validated and decrypted correctly. This is the standard setup for secure AS2 communication where the partner signs and encrypts outgoing messages.

• ✗

  Import your own private key for signature verification, import your own public certificate for decryption, and enable both signature verification and decryption in the adapter.

  Why it's wrong here

  Signature verification cannot use a private key; it requires the sender's public certificate. Your own private key is not the correct key for verifying the partner's signature. For decryption, your public certificate cannot decrypt a message encrypted with your public key; only your private key can. This configuration would result in both signature verification and decryption failures, causing the message to be rejected.

• ✗

  Import your own public certificate for signature verification, import the partner's private key for decryption, and enable both signature verification and decryption in the adapter.

  Why it's wrong here

  Signature verification uses the sender's public certificate, not your own public certificate. The partner signs with their private key, so you need their public key to verify. Similarly, decryption requires your private key, not the partner's private key, because the message was encrypted with your public key. Using the wrong certificates will cause signature verification to fail and decryption to produce unreadable data.

• ✗

  Import the partner's public certificate for signature verification, import the partner's public certificate for decryption, and enable both signature verification and decryption in the adapter.

  Why it's wrong here

  While the partner's public certificate is correct for signature verification, it cannot be used for decryption. Decryption requires your private key, which corresponds to the public key the partner used to encrypt the message. Using the partner's public certificate for decryption will fail because it does not contain the private key needed to decrypt the message. The adapter will reject the message due to decryption errors.