You are developing a BizTalk Server 2010 orchestration that consumes a web service located at http://localhost/ProcessData.asmx. The orchestration contains a non-transactional scope with an exception handler that handles any SOAP exceptions returned from the web service. The orchestration then completes successfully. After the orchestration completes with exceptions, you notice that the original messages posted to the web service are suspended in the BizTalk Administration console. You need to ensure that the messages are not suspended but are saved in an archive file on a shared server.
What should you do?
A.
In the Administration console, modify the SOAP send port and enable routing for failed messages.
Create a FILE send port with filters ErrorReport.ErrorType==FailedMessage and ErrorReport.OutboundTransportLocation==http://localhost/ProcessData.asmx.
B.
In Orchestration Designer, set Delivery Notification to Transmitted on the request/response port that sends the SOAP message. Create an exception handler with exception type DeliveryFailureException. In the handler, send a copy of the original message to a new send port that will transmit the message as a file.
C.
In the Administration console, change the send pipeline to PassThruTransmit and enable Ordered delivery in the transport options.
D.
In Orchestration Designer, modify the SOAP exception handler to send a copy of the original message to a new send port that will transmit the message as a file.