A BizTalk Server 2010 messaging-only solution is used to process XML messages.
The pipelines used in the receive location and the send port contain the XML validator pipeline component.
Routing for failed messages is enabled on both the receive port and the send port.
When validation fails on the receive side, messages must be routed to Send Port A.
When validation fails on the send side, messages must be routed to Send Port B.
You need to create subscriptions for Send Port A and Send Port B.
What should you do?

• A. Set the filter for Send Port A to Error.SendPortName Exists. Set the filter for Send Port B to Error. ReceivePortName Exists.
• B. Set the filter for Send Port A to Error.ErrorType == ReceivePort. Set the filter for Send Port B to Error. ErrorType == SendPort.
• C. Set the filter for Send Port A to Error.ReceivePortName Exists. Set the filter for Send Port B to Error. SendPortName Exists.
• D. Set the filter for Send Port A to BTS.ReceivePortName Exists. Set the filter for Send Port B to BTS. SPName Exists.

You change the host-level settings of a BizTalk Server 2010 group named Group1 to optimize the group for a low-latency scenario. You install and configure another BizTalk Server 2010 group, named Group2. Both BizTalk groups use identical hardware. You need to ensure that the same low-latency optimizations are applied to Group2 as to Group1. What should you do?

• A. From the Administration console, export the host-level settings for Group1. Import the settings on Group2.
• B. From the Administration console, export the default application as MSI file from Group1. Import the application on Group2.
• C. From the Administration console, export all applications as Microsoft Windows Installer (MSI) files from Group1. Import the applications on Group2.
• D. From Microsoft SQL Server Management Studio, create a backup of the BizTalk management database of Group1. Restore this backup on Group2.

You are developing a BizTalk Server 2010 orchestration. In the Business Rule Composer, you create and save a policy named BonusPolicy that calculates an employees bonus based on year-to-date sales. You add a Call Rules shape to the orchestration. In the BizTalk Orchestration Designer, BonusPolicy is not listed in the menu of available policies to call. You need to make the policy available in the Orchestration Designer. What should you do?

• A. In the Business Rules Composer, publish BonusPolicy.
• B. Use the Rule Engine Deployment Wizard to export BonusPolicy.
• C. In the Business Rules Composer, create a vocabulary with a definition that references the XML schema used to evaluate BonusPolicy. Publish the vocabulary.
• D. In the Business Rules Composer, use the Rule Store menu and load policies from the BizTalkRuleEngineDb database.

A BizTalk Server 2010 solution uses an orchestration that performs several actions. The orchestration uses Expression shapes and Message Assignment shapes. The orchestration has no Scope shapes and the Transaction Type property is set to None. Occasionally, an XLANG exception is thrown in the orchestration. The exception is not handled and the orchestration goes into a suspended state. You need to catch the exception and handle the error. Which two actions should you perform? (Each correct answer presents part of the solution. Choose two.)

• A. Add a Scope shape to the orchestration. Place all Expression and Message Assignment shapes within this scope.
• B. Add an exception handler. Set the Exception Object Type property to System.SystemException.
• C. Set the Transaction Type property of the orchestration to Long Running. Set the Compensation property of the orchestration to Default.
• D. Add an exception handler. Set the Exception Object Type property to Microsoft.XLANGs.BaseTypes. XLANGsException.

A BizTalk Server 2010 solution uses an orchestration to call an external Microsoft .NET assembly. The class on the assembly is not serializable. The Expression shape used to call the .NET assembly is contained within a scope that has its Transaction Type property set to Atomic. The call to the .NET assembly occasionally results in an exception being thrown. You need to handle the exception when it is thrown. Create a new scope with the Transaction Type property set to Long Running. What should you do next?

• A. Add a compensation block to the atomic scope. Drag and drop the atomic scope inside the new scope.
• B. Add an exception handler to the new scope. Drag and drop the atomic scope above the new scope.
• C. Add an exception handler to the new scope. Drag and drop the atomic scope below the new scope.
• D. Add an exception handler to the new scope. Drag and drop the atomic scope inside the new scope.