Debugging and exception handling

1. Answer: d

   You must enable Failed Message Routing on the Receive Port where processing fails and you must add a filter on ErrorReport.ReceivePortName to the SendFailureNotification Port. The BTS.ReceivePortName property is available but will not be promoted in a failed message and cannot be used for routing.

2. Answer: c

   RecoverableInterchangeProcessing is a property on the XMLDisassembler component. When configured to True, it allows successfully processed messages from a batch to pass through while suspending only the incorrect ones. By default the property is False, which means that one incorrectly formatted message fails the entire batch. Ordered Delivery does not help with this nor does processing instructions.

3. Answer: b

   You need to set Enable Unit Testing to True. References to Microsoft.BizTalk.TestTools and Microsoft.XLANGs.BaseTypes are needed, but you do not need to add them manually. Also, when setting Enable Unit Testing to True, the Schema will get the TestableSchemaBase as its base class, which surfaces the ValidateInstance method on the Schema class. You cannot cast a Schema that does not inherit from the TestableSchemaBase class to that class and use the ValidateInstance method.

4. Answer: d

   You need to use a scope with an exception block to be able to catch the exception. Once caught, the Orchestration will terminate without suspending. The Throw Exception shape will rethrow the exception and cause the Orchestration to become suspended. The Report to Analyst option is connected to the Orchestration Designer for Business Analysts (ODBA) and has nothing to do with exception handling.

5. Answer: a

   In order to get rid of suspended messages on a Send Port that fails processing, you must enable Failed Message Routing and create a subscription that matches any of the ErrorReport properties, for example SendPortName. Subscribing to BTS.AckType and BTS.AckSendPortName will get you the NACK message (the exception), but you will not avoid the suspended message. Also, Delivery Notification does not help you avoid suspended messages either.

6. Answer: b

   You can unit test Schemas, Maps and Pipelines. You cannot easily unit test the Pipeline components by themselves, only inside a Pipeline, since they require the context of a Pipeline. Orchestrations must be deployed to be run and tested.