1. Answer: c

When signing a message, the trading partner will use his/her own private certificate. When the receiver (us) needs to verify the validity of the signature, a public key instance of the certificate must be used and stored in local machine/other people.

2. Answer: b, c

In this case, routing for failed messages need to be set up on the Receive Port (there will be no Send Port activity when a message fails on the receive side). When failed message routing is enabled, all normal Context properties such as BTS.ReceivePortName are unpromoted, and only Context properties in the ErrorReport namespace can be used for routing.

3. Answer: b

Receive Locations should still be enabled and the BizTalk service(s) should still be running, so that other subscribers will still get their messages. Setting a Send Port state to Unenlisted state will cause the Send Port to stop subscribing to messages, and will therefore never receive the messages received in BizTalk while the state was Unenlisted. Setting the port to a stopped state will allow the port to receive all messages intended for the port and not send them, until the port is started again.

4. Answer: c

If a message is published to the MessageBox without a message type Context Property, no disassembler has been executed in the Receive Port, and out of the box only the PassThruReceive pipeline has that lack of disassemblers. Therefore, we must assume that it has been used, and as we are receiving XML messages, using the XMLReceive pipeline should solve the problem.

5. Answer: c

POP3 is the only out of the box adapter that has the capabilities of receiving e-mails from an exchange server. Also, the body part index should be 0, because the actual body part is required.